]> git.ipfire.org Git - thirdparty/vim.git/commit
runtime(java): Recognise the {@snippet} documentation tag (#14271)
authorAliaksei Budavei <32549825+zzzyxwvut@users.noreply.github.com>
Fri, 22 Mar 2024 18:32:48 +0000 (21:32 +0300)
committerGitHub <noreply@github.com>
Fri, 22 Mar 2024 18:32:48 +0000 (19:32 +0100)
commit3e72bf10a0a2fc34f01ff9663ed3324c2a140228
tree55879b08c2aaad3937ab6b363823d7db904f4d74
parentf976e2c956eb8f1643bc110bd4e3fbb8021a754d
runtime(java): Recognise the {@snippet} documentation tag (#14271)

Remember that ‘code fragments are typically Java source
code, but they may also be fragments of properties files,
source code in other languages, or plain text.’  Therefore,
with these changes, markup tags are highlighted in the Java
source files (as external snippets) and in the {@snippet}
tags.

Also:

- Improve matching of the multi-line {@code} documentation
  tag with any contained balanced braces.
- Recognise the {@literal} documentation tag.
- Highlight stray blanks in comments.

Related to an enhancement proposal for PCRE-like callouts
discussed at https://github.com/vim/vim/issues/11217.

References:
https://openjdk.org/jeps/413
https://docs.oracle.com/en/java/javase/21/docs/specs/javadoc/doc-comment-spec.html

Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
runtime/syntax/java.vim
runtime/syntax/testdir/dumps/java_comments_00.dump [new file with mode: 0644]
runtime/syntax/testdir/dumps/java_comments_01.dump [new file with mode: 0644]
runtime/syntax/testdir/dumps/java_comments_99.dump [new file with mode: 0644]
runtime/syntax/testdir/input/java_comments.java [new file with mode: 0644]