diff options
author | Bram Moolenaar <Bram@vim.org> | 2023-02-20 20:44:55 +0000 |
---|---|---|
committer | Bram Moolenaar <Bram@vim.org> | 2023-02-20 20:44:55 +0000 |
commit | 938ae280c79b8cdb0fca60336ec4c090ecd8bb5a (patch) | |
tree | c9418dcff4d627d7c86aa740a47082f02ad555f6 /runtime/doc/syntax.txt | |
parent | 6b066c6d8f57aa05f1ab29ab4d098bc4bfabb1bb (diff) |
Update runtime files.
Diffstat (limited to 'runtime/doc/syntax.txt')
-rw-r--r-- | runtime/doc/syntax.txt | 32 |
1 files changed, 23 insertions, 9 deletions
diff --git a/runtime/doc/syntax.txt b/runtime/doc/syntax.txt index 27c65daccf..eed82f1e84 100644 --- a/runtime/doc/syntax.txt +++ b/runtime/doc/syntax.txt @@ -1,4 +1,4 @@ -*syntax.txt* For Vim version 9.0. Last change: 2022 Dec 26 +*syntax.txt* For Vim version 9.0. Last change: 2023 Feb 20 VIM REFERENCE MANUAL by Bram Moolenaar @@ -1307,18 +1307,32 @@ When not set 4 is used. DOSBATCH *dosbatch.vim* *ft-dosbatch-syntax* -There is one option with highlighting DOS batch files. This covers new -extensions to the Command Interpreter introduced with Windows 2000 and -is controlled by the variable dosbatch_cmdextversion. For Windows NT -this should have the value 1, and for Windows 2000 it should be 2. +Select the set of Windows Command interpreter extensions that should be +supported with the variable dosbatch_cmdextversion. For versions of Windows +NT (before Windows 2000) this should have the value of 1. For Windows 2000 +and later it should be 2. Select the version you want with the following line: > :let dosbatch_cmdextversion = 1 If this variable is not defined it defaults to a value of 2 to support -Windows 2000. +Windows 2000 and later. -A second option covers whether *.btm files should be detected as type +The original MS-DOS supports an idiom of using a double colon (::) as an +alternative way to enter a comment line. This idiom can be used with the +current Windows Command Interpreter, but it can lead to problems when used +inside ( ... ) command blocks. You can find a discussion about this on +Stack Overflow - + +https://stackoverflow.com/questions/12407800/which-comment-style-should-i-use-in-batch-files + +To allow the use of the :: idiom for comments in the Windows Command +Interpreter or working with MS-DOS bat files, set the +dosbatch_colons_comment variable to anything: > + + :let dosbatch_colons_comment = 1 + +There is an option that covers whether *.btm files should be detected as type "dosbatch" (MS-DOS batch files) or type "btm" (4DOS batch files). The latter is used by default. You may select the former with the following line: > @@ -3836,7 +3850,7 @@ SYNTAX ISKEYWORD SETTING *:syn-iskeyword* clear: Syntax specific iskeyword setting is disabled and the buffer-local 'iskeyword' setting is used. - {option} Set the syntax 'iskeyword' option to a new value. + {option} Set the syntax 'iskeyword' option to a new value. Example: > :syntax iskeyword @,48-57,192-255,$,_ @@ -5283,7 +5297,7 @@ guisp={color-name} *highlight-guisp* (guisp) color to use in the GUI. "guisp" is used for undercurl and strikethrough. There are a few special names: - NONE no color (transparent) + NONE no color (transparent) *E1361* bg use normal background color background use normal background color fg use normal foreground color |