From 30a8ad675d183c15c47b42e37199e98e2f924d69 Mon Sep 17 00:00:00 2001 From: Aliaksei Budavei <0x000c70@gmail.com> Date: Wed, 31 Jul 2024 22:16:08 +0200 Subject: [PATCH] runtime(java): Document "g:java_space_errors" and "g:java_comment_strings" closes: #15399 Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com> Signed-off-by: Christian Brabandt --- runtime/doc/syntax.txt | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/runtime/doc/syntax.txt b/runtime/doc/syntax.txt index 8af731fb16..8cefb0e65c 100644 --- a/runtime/doc/syntax.txt +++ b/runtime/doc/syntax.txt @@ -1,4 +1,4 @@ -*syntax.txt* For Vim version 9.1. Last change: 2024 Jul 30 +*syntax.txt* For Vim version 9.1. Last change: 2024 Jul 31 VIM REFERENCE MANUAL by Bram Moolenaar @@ -2132,6 +2132,16 @@ actually appear in Javadoc comments. The variables to use are > :let g:java_vb = 1 Note that these three variables are maintained in the HTML syntax file. +Numbers and strings can be recognized in non-Javadoc comments with > + :let g:java_comment_strings = 1 + +Trailing whitespace characters or a run of space characters before a tab +character can be marked as an error with > + :let g:java_space_errors = 1 +but either kind of an error can be suppressed by also defining one of > + :let g:java_no_trail_space_error = 1 + :let g:java_no_tab_space_error = 1 + In order to highlight nested parens with different colors, define colors for `javaParen`, `javaParen1`, and `javaParen2`. For example, > :hi link javaParen Comment