Mercurial > vim

comparison runtime/syntax/lss.vim @ 32974:d46f974fd69e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
runtime: Fix typos in various files Commit: https://github.com/vim/vim/commit/3fc7a7e44abda6505ccd39a6d067db6e5173cbf6 Author: Viktor Sz?pe <viktor@szepe.net> Date: Wed Aug 23 21:20:00 2023 +0200 runtime: Fix typos in various files closes: https://github.com/vim/vim/issues/12836 Signed-off-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Viktor Sz?pe <viktor@szepe.net>
author Christian Brabandt <cb@256bit.org>
date Thu, 24 Aug 2023 07:33:27 +0200
parents 43efa4f5a8ea
children
comparison
equal deleted inserted replaced
32973:3c2cb52444e9 32974:d46f974fd69e
7 if exists("b:current_syntax") 7 if exists("b:current_syntax")
8 finish 8 finish
9 endif 9 endif
10 10
11 " This setup is probably atypical for a syntax highlighting file, because 11 " This setup is probably atypical for a syntax highlighting file, because
12 " most of it is not really intended to be overrideable. Instead, the 12 " most of it is not really intended to be overridable. Instead, the
13 " highlighting is supposed to correspond to the highlighting specified by 13 " highlighting is supposed to correspond to the highlighting specified by
14 " the .lss file entries themselves; ie. the "bold" keyword should be bold, 14 " the .lss file entries themselves; ie. the "bold" keyword should be bold,
15 " the "red" keyword should be red, and so forth. The exceptions to this 15 " the "red" keyword should be red, and so forth. The exceptions to this
16 " are comments, of course, and the initial keyword identifying the affected 16 " are comments, of course, and the initial keyword identifying the affected
17 " element, which will inherit the usual Identifier highlighting. 17 " element, which will inherit the usual Identifier highlighting.