Mercurial > vim
annotate runtime/doc/syntax.txt @ 4687:79797c8534b5
Added tag v7-3-1090 for changeset 8db697ae406a
| author | Bram Moolenaar <bram@vim.org> |
|---|---|
| date | Sat, 01 Jun 2013 23:02:55 +0200 |
| parents | 2eb30f341e8d |
| children | f824cb97eb92 |
| rev | line source |
|---|---|
|
4681
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4437
diff
changeset
|
1 *syntax.txt* For Vim version 7.3. Last change: 2013 May 31 |
| 7 | 2 |
| 3 | |
| 4 VIM REFERENCE MANUAL by Bram Moolenaar | |
| 5 | |
| 6 | |
| 7 Syntax highlighting *syntax* *syntax-highlighting* *coloring* | |
| 8 | |
| 9 Syntax highlighting enables Vim to show parts of the text in another font or | |
| 10 color. Those parts can be specific keywords or text matching a pattern. Vim | |
| 11 doesn't parse the whole file (to keep it fast), so the highlighting has its | |
| 12 limitations. Lexical highlighting might be a better name, but since everybody | |
| 13 calls it syntax highlighting we'll stick with that. | |
| 14 | |
| 15 Vim supports syntax highlighting on all terminals. But since most ordinary | |
| 16 terminals have very limited highlighting possibilities, it works best in the | |
| 17 GUI version, gvim. | |
| 18 | |
| 19 In the User Manual: | |
| 20 |usr_06.txt| introduces syntax highlighting. | |
| 21 |usr_44.txt| introduces writing a syntax file. | |
| 22 | |
| 23 1. Quick start |:syn-qstart| | |
| 24 2. Syntax files |:syn-files| | |
| 25 3. Syntax loading procedure |syntax-loading| | |
| 26 4. Syntax file remarks |:syn-file-remarks| | |
| 27 5. Defining a syntax |:syn-define| | |
| 28 6. :syntax arguments |:syn-arguments| | |
| 29 7. Syntax patterns |:syn-pattern| | |
| 30 8. Syntax clusters |:syn-cluster| | |
| 31 9. Including syntax files |:syn-include| | |
| 32 10. Synchronizing |:syn-sync| | |
| 33 11. Listing syntax items |:syntax| | |
| 34 12. Highlight command |:highlight| | |
| 35 13. Linking groups |:highlight-link| | |
| 36 14. Cleaning up |:syn-clear| | |
| 37 15. Highlighting tags |tag-highlight| | |
|
2250
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
38 16. Window-local syntax |:ownsyntax| |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
39 17. Color xterms |xterm-color| |
| 7 | 40 |
| 41 {Vi does not have any of these commands} | |
| 42 | |
| 43 Syntax highlighting is not available when the |+syntax| feature has been | |
| 44 disabled at compile time. | |
| 45 | |
| 46 ============================================================================== | |
| 47 1. Quick start *:syn-qstart* | |
| 48 | |
| 49 *:syn-enable* *:syntax-enable* | |
| 50 This command switches on syntax highlighting: > | |
| 51 | |
| 52 :syntax enable | |
| 53 | |
| 54 What this command actually does is to execute the command > | |
| 55 :source $VIMRUNTIME/syntax/syntax.vim | |
| 56 | |
| 57 If the VIM environment variable is not set, Vim will try to find | |
| 58 the path in another way (see |$VIMRUNTIME|). Usually this works just | |
| 59 fine. If it doesn't, try setting the VIM environment variable to the | |
| 60 directory where the Vim stuff is located. For example, if your syntax files | |
| 61 are in the "/usr/vim/vim50/syntax" directory, set $VIMRUNTIME to | |
| 62 "/usr/vim/vim50". You must do this in the shell, before starting Vim. | |
| 63 | |
| 64 *:syn-on* *:syntax-on* | |
| 65 The ":syntax enable" command will keep your current color settings. This | |
| 66 allows using ":highlight" commands to set your preferred colors before or | |
| 67 after using this command. If you want Vim to overrule your settings with the | |
| 68 defaults, use: > | |
| 69 :syntax on | |
| 70 < | |
| 71 *:hi-normal* *:highlight-normal* | |
| 72 If you are running in the GUI, you can get white text on a black background | |
| 73 with: > | |
| 74 :highlight Normal guibg=Black guifg=White | |
| 75 For a color terminal see |:hi-normal-cterm|. | |
| 76 For setting up your own colors syntax highlighting see |syncolor|. | |
| 77 | |
| 78 NOTE: The syntax files on MS-DOS and Windows have lines that end in <CR><NL>. | |
| 79 The files for Unix end in <NL>. This means you should use the right type of | |
| 80 file for your system. Although on MS-DOS and Windows the right format is | |
| 81 automatically selected if the 'fileformats' option is not empty. | |
| 82 | |
| 83 NOTE: When using reverse video ("gvim -fg white -bg black"), the default value | |
| 84 of 'background' will not be set until the GUI window is opened, which is after | |
| 819 | 85 reading the |gvimrc|. This will cause the wrong default highlighting to be |
| 7 | 86 used. To set the default value of 'background' before switching on |
| 819 | 87 highlighting, include the ":gui" command in the |gvimrc|: > |
| 7 | 88 |
| 89 :gui " open window and set default for 'background' | |
| 90 :syntax on " start highlighting, use 'background' to set colors | |
| 91 | |
| 819 | 92 NOTE: Using ":gui" in the |gvimrc| means that "gvim -f" won't start in the |
| 7 | 93 foreground! Use ":gui -f" then. |
| 94 | |
| 2520 | 95 *g:syntax_on* |
| 96 You can toggle the syntax on/off with this command: > | |
| 97 :if exists("g:syntax_on") | syntax off | else | syntax enable | endif | |
| 7 | 98 |
| 99 To put this into a mapping, you can use: > | |
| 2520 | 100 :map <F7> :if exists("g:syntax_on") <Bar> |
| 7 | 101 \ syntax off <Bar> |
| 102 \ else <Bar> | |
| 103 \ syntax enable <Bar> | |
| 104 \ endif <CR> | |
| 105 [using the |<>| notation, type this literally] | |
| 106 | |
| 1624 | 107 Details: |
| 7 | 108 The ":syntax" commands are implemented by sourcing a file. To see exactly how |
| 109 this works, look in the file: | |
| 110 command file ~ | |
| 111 :syntax enable $VIMRUNTIME/syntax/syntax.vim | |
| 112 :syntax on $VIMRUNTIME/syntax/syntax.vim | |
| 113 :syntax manual $VIMRUNTIME/syntax/manual.vim | |
| 114 :syntax off $VIMRUNTIME/syntax/nosyntax.vim | |
| 115 Also see |syntax-loading|. | |
| 116 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
117 NOTE: If displaying long lines is slow and switching off syntax highlighting |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
118 makes it fast, consider setting the 'synmaxcol' option to a lower value. |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
119 |
| 7 | 120 ============================================================================== |
| 121 2. Syntax files *:syn-files* | |
| 122 | |
| 123 The syntax and highlighting commands for one language are normally stored in | |
| 124 a syntax file. The name convention is: "{name}.vim". Where {name} is the | |
| 125 name of the language, or an abbreviation (to fit the name in 8.3 characters, | |
| 126 a requirement in case the file is used on a DOS filesystem). | |
| 127 Examples: | |
| 128 c.vim perl.vim java.vim html.vim | |
| 129 cpp.vim sh.vim csh.vim | |
| 130 | |
| 131 The syntax file can contain any Ex commands, just like a vimrc file. But | |
| 132 the idea is that only commands for a specific language are included. When a | |
| 133 language is a superset of another language, it may include the other one, | |
| 134 for example, the cpp.vim file could include the c.vim file: > | |
| 135 :so $VIMRUNTIME/syntax/c.vim | |
| 136 | |
| 137 The .vim files are normally loaded with an autocommand. For example: > | |
| 138 :au Syntax c runtime! syntax/c.vim | |
| 139 :au Syntax cpp runtime! syntax/cpp.vim | |
| 140 These commands are normally in the file $VIMRUNTIME/syntax/synload.vim. | |
| 141 | |
| 142 | |
| 143 MAKING YOUR OWN SYNTAX FILES *mysyntaxfile* | |
| 144 | |
| 145 When you create your own syntax files, and you want to have Vim use these | |
| 146 automatically with ":syntax enable", do this: | |
| 147 | |
| 148 1. Create your user runtime directory. You would normally use the first item | |
| 149 of the 'runtimepath' option. Example for Unix: > | |
| 150 mkdir ~/.vim | |
| 151 | |
| 152 2. Create a directory in there called "syntax". For Unix: > | |
| 153 mkdir ~/.vim/syntax | |
| 154 | |
| 155 3. Write the Vim syntax file. Or download one from the internet. Then write | |
| 156 it in your syntax directory. For example, for the "mine" syntax: > | |
| 157 :w ~/.vim/syntax/mine.vim | |
| 158 | |
| 159 Now you can start using your syntax file manually: > | |
| 160 :set syntax=mine | |
| 161 You don't have to exit Vim to use this. | |
| 162 | |
| 163 If you also want Vim to detect the type of file, see |new-filetype|. | |
| 164 | |
| 165 If you are setting up a system with many users and you don't want each user | |
| 166 to add the same syntax file, you can use another directory from 'runtimepath'. | |
| 167 | |
| 168 | |
| 169 ADDING TO AN EXISTING SYNTAX FILE *mysyntaxfile-add* | |
| 170 | |
| 171 If you are mostly satisfied with an existing syntax file, but would like to | |
| 172 add a few items or change the highlighting, follow these steps: | |
| 173 | |
| 174 1. Create your user directory from 'runtimepath', see above. | |
| 175 | |
| 176 2. Create a directory in there called "after/syntax". For Unix: > | |
| 177 mkdir ~/.vim/after | |
| 178 mkdir ~/.vim/after/syntax | |
| 179 | |
| 180 3. Write a Vim script that contains the commands you want to use. For | |
| 181 example, to change the colors for the C syntax: > | |
| 182 highlight cComment ctermfg=Green guifg=Green | |
| 183 | |
| 184 4. Write that file in the "after/syntax" directory. Use the name of the | |
| 185 syntax, with ".vim" added. For our C syntax: > | |
| 186 :w ~/.vim/after/syntax/c.vim | |
| 187 | |
| 188 That's it. The next time you edit a C file the Comment color will be | |
| 189 different. You don't even have to restart Vim. | |
| 190 | |
| 169 | 191 If you have multiple files, you can use the filetype as the directory name. |
| 192 All the "*.vim" files in this directory will be used, for example: | |
| 193 ~/.vim/after/syntax/c/one.vim | |
| 194 ~/.vim/after/syntax/c/two.vim | |
| 195 | |
| 7 | 196 |
| 197 REPLACING AN EXISTING SYNTAX FILE *mysyntaxfile-replace* | |
| 198 | |
| 199 If you don't like a distributed syntax file, or you have downloaded a new | |
| 200 version, follow the same steps as for |mysyntaxfile| above. Just make sure | |
| 201 that you write the syntax file in a directory that is early in 'runtimepath'. | |
| 3445 | 202 Vim will only load the first syntax file found, assuming that it sets |
| 203 b:current_syntax. | |
| 7 | 204 |
| 205 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
206 NAMING CONVENTIONS *group-name* *{group-name}* *E669* *W18* |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
207 |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
208 A syntax group name is to be used for syntax items that match the same kind of |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
209 thing. These are then linked to a highlight group that specifies the color. |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
210 A syntax group name doesn't specify any color or attributes itself. |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
211 |
| 7 | 212 The name for a highlight or syntax group must consist of ASCII letters, digits |
| 213 and the underscore. As a regexp: "[a-zA-Z0-9_]*" | |
| 214 | |
| 215 To be able to allow each user to pick his favorite set of colors, there must | |
| 216 be preferred names for highlight groups that are common for many languages. | |
| 217 These are the suggested group names (if syntax highlighting works properly | |
| 218 you can see the actual color, except for "Ignore"): | |
| 219 | |
| 220 *Comment any comment | |
| 221 | |
| 222 *Constant any constant | |
| 223 String a string constant: "this is a string" | |
| 224 Character a character constant: 'c', '\n' | |
| 225 Number a number constant: 234, 0xff | |
| 226 Boolean a boolean constant: TRUE, false | |
| 227 Float a floating point constant: 2.3e10 | |
| 228 | |
| 229 *Identifier any variable name | |
| 230 Function function name (also: methods for classes) | |
| 231 | |
| 232 *Statement any statement | |
| 233 Conditional if, then, else, endif, switch, etc. | |
| 234 Repeat for, do, while, etc. | |
| 235 Label case, default, etc. | |
| 236 Operator "sizeof", "+", "*", etc. | |
| 237 Keyword any other keyword | |
| 238 Exception try, catch, throw | |
| 239 | |
| 240 *PreProc generic Preprocessor | |
| 241 Include preprocessor #include | |
| 242 Define preprocessor #define | |
| 243 Macro same as Define | |
| 244 PreCondit preprocessor #if, #else, #endif, etc. | |
| 245 | |
| 246 *Type int, long, char, etc. | |
| 247 StorageClass static, register, volatile, etc. | |
| 248 Structure struct, union, enum, etc. | |
| 249 Typedef A typedef | |
| 250 | |
| 251 *Special any special symbol | |
| 252 SpecialChar special character in a constant | |
| 253 Tag you can use CTRL-] on this | |
| 254 Delimiter character that needs attention | |
| 255 SpecialComment special things inside a comment | |
| 256 Debug debugging statements | |
| 257 | |
| 258 *Underlined text that stands out, HTML links | |
| 259 | |
|
2386
fb8cce4174f0
Better text for 'concealcursor' in :options window.
Bram Moolenaar <bram@vim.org>
parents:
2378
diff
changeset
|
260 *Ignore left blank, hidden |hl-Ignore| |
| 7 | 261 |
| 262 *Error any erroneous construct | |
| 263 | |
| 264 *Todo anything that needs extra attention; mostly the | |
| 265 keywords TODO FIXME and XXX | |
| 266 | |
| 267 The names marked with * are the preferred groups; the others are minor groups. | |
| 268 For the preferred groups, the "syntax.vim" file contains default highlighting. | |
| 269 The minor groups are linked to the preferred groups, so they get the same | |
| 270 highlighting. You can override these defaults by using ":highlight" commands | |
| 271 after sourcing the "syntax.vim" file. | |
| 272 | |
| 273 Note that highlight group names are not case sensitive. "String" and "string" | |
| 274 can be used for the same group. | |
| 275 | |
| 276 The following names are reserved and cannot be used as a group name: | |
| 277 NONE ALL ALLBUT contains contained | |
| 278 | |
|
2386
fb8cce4174f0
Better text for 'concealcursor' in :options window.
Bram Moolenaar <bram@vim.org>
parents:
2378
diff
changeset
|
279 *hl-Ignore* |
|
fb8cce4174f0
Better text for 'concealcursor' in :options window.
Bram Moolenaar <bram@vim.org>
parents:
2378
diff
changeset
|
280 When using the Ignore group, you may also consider using the conceal |
|
fb8cce4174f0
Better text for 'concealcursor' in :options window.
Bram Moolenaar <bram@vim.org>
parents:
2378
diff
changeset
|
281 mechanism. See |conceal|. |
|
fb8cce4174f0
Better text for 'concealcursor' in :options window.
Bram Moolenaar <bram@vim.org>
parents:
2378
diff
changeset
|
282 |
| 7 | 283 ============================================================================== |
| 284 3. Syntax loading procedure *syntax-loading* | |
| 285 | |
| 286 This explains the details that happen when the command ":syntax enable" is | |
| 287 issued. When Vim initializes itself, it finds out where the runtime files are | |
| 288 located. This is used here as the variable |$VIMRUNTIME|. | |
| 289 | |
| 290 ":syntax enable" and ":syntax on" do the following: | |
| 291 | |
| 292 Source $VIMRUNTIME/syntax/syntax.vim | |
| 293 | | |
| 294 +- Clear out any old syntax by sourcing $VIMRUNTIME/syntax/nosyntax.vim | |
| 295 | | |
| 296 +- Source first syntax/synload.vim in 'runtimepath' | |
| 297 | | | |
| 298 | +- Setup the colors for syntax highlighting. If a color scheme is | |
| 299 | | defined it is loaded again with ":colors {name}". Otherwise | |
| 300 | | ":runtime! syntax/syncolor.vim" is used. ":syntax on" overrules | |
| 301 | | existing colors, ":syntax enable" only sets groups that weren't | |
| 302 | | set yet. | |
| 303 | | | |
| 304 | +- Set up syntax autocmds to load the appropriate syntax file when | |
| 305 | | the 'syntax' option is set. *synload-1* | |
| 306 | | | |
| 307 | +- Source the user's optional file, from the |mysyntaxfile| variable. | |
| 308 | This is for backwards compatibility with Vim 5.x only. *synload-2* | |
| 309 | | |
| 310 +- Do ":filetype on", which does ":runtime! filetype.vim". It loads any | |
| 311 | filetype.vim files found. It should always Source | |
| 312 | $VIMRUNTIME/filetype.vim, which does the following. | |
| 313 | | | |
| 314 | +- Install autocmds based on suffix to set the 'filetype' option | |
| 315 | | This is where the connection between file name and file type is | |
| 316 | | made for known file types. *synload-3* | |
| 317 | | | |
| 318 | +- Source the user's optional file, from the *myfiletypefile* | |
| 319 | | variable. This is for backwards compatibility with Vim 5.x only. | |
| 320 | | *synload-4* | |
| 321 | | | |
| 322 | +- Install one autocommand which sources scripts.vim when no file | |
| 323 | | type was detected yet. *synload-5* | |
| 324 | | | |
| 325 | +- Source $VIMRUNTIME/menu.vim, to setup the Syntax menu. |menu.vim| | |
| 326 | | |
| 327 +- Install a FileType autocommand to set the 'syntax' option when a file | |
| 328 | type has been detected. *synload-6* | |
| 329 | | |
| 330 +- Execute syntax autocommands to start syntax highlighting for each | |
| 331 already loaded buffer. | |
| 332 | |
| 333 | |
| 334 Upon loading a file, Vim finds the relevant syntax file as follows: | |
| 335 | |
| 336 Loading the file triggers the BufReadPost autocommands. | |
| 337 | | |
| 338 +- If there is a match with one of the autocommands from |synload-3| | |
| 339 | (known file types) or |synload-4| (user's file types), the 'filetype' | |
| 340 | option is set to the file type. | |
| 341 | | |
| 342 +- The autocommand at |synload-5| is triggered. If the file type was not | |
| 343 | found yet, then scripts.vim is searched for in 'runtimepath'. This | |
| 344 | should always load $VIMRUNTIME/scripts.vim, which does the following. | |
| 345 | | | |
| 346 | +- Source the user's optional file, from the *myscriptsfile* | |
| 347 | | variable. This is for backwards compatibility with Vim 5.x only. | |
| 348 | | | |
| 349 | +- If the file type is still unknown, check the contents of the file, | |
| 350 | again with checks like "getline(1) =~ pattern" as to whether the | |
| 351 | file type can be recognized, and set 'filetype'. | |
| 352 | | |
| 353 +- When the file type was determined and 'filetype' was set, this | |
| 354 | triggers the FileType autocommand |synload-6| above. It sets | |
| 355 | 'syntax' to the determined file type. | |
| 356 | | |
| 357 +- When the 'syntax' option was set above, this triggers an autocommand | |
| 358 | from |synload-1| (and |synload-2|). This find the main syntax file in | |
| 359 | 'runtimepath', with this command: | |
| 360 | runtime! syntax/<name>.vim | |
| 361 | | |
| 362 +- Any other user installed FileType or Syntax autocommands are | |
| 363 triggered. This can be used to change the highlighting for a specific | |
| 364 syntax. | |
| 365 | |
| 366 ============================================================================== | |
| 367 4. Syntax file remarks *:syn-file-remarks* | |
| 368 | |
| 369 *b:current_syntax-variable* | |
| 370 Vim stores the name of the syntax that has been loaded in the | |
| 371 "b:current_syntax" variable. You can use this if you want to load other | |
| 372 settings, depending on which syntax is active. Example: > | |
| 373 :au BufReadPost * if b:current_syntax == "csh" | |
| 374 :au BufReadPost * do-some-things | |
| 375 :au BufReadPost * endif | |
| 376 | |
| 377 | |
| 378 2HTML *2html.vim* *convert-to-HTML* | |
| 379 | |
| 380 This is not a syntax file itself, but a script that converts the current | |
| 381 window into HTML. Vim opens a new window in which it builds the HTML file. | |
| 382 | |
| 3713 | 383 After you save the resulting file, you can view it with any browser. The |
|
4681
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4437
diff
changeset
|
384 colors should be exactly the same as you see them in Vim. You can jump to |
|
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4437
diff
changeset
|
385 specific lines by adding (for example) #L123 or #123 to the end of the URL in |
|
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4437
diff
changeset
|
386 your browser's address bar (#123 only with javascript support). And with |
|
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4437
diff
changeset
|
387 |g:html_dynamic_folds| enabled, you can show or hide the text that is folded |
|
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4437
diff
changeset
|
388 in Vim. |
| 3713 | 389 |
| 7 | 390 You are not supposed to set the 'filetype' or 'syntax' option to "2html"! |
| 391 Source the script to convert the current file: > | |
| 392 | |
| 393 :runtime! syntax/2html.vim | |
| 394 < | |
| 3713 | 395 Many variables affect the output of 2html.vim; see below. Any of the on/off |
| 396 options listed below can be enabled or disabled by setting them explicitly to | |
| 397 the desired value, or restored to their default by removing the variable using | |
| 398 |:unlet|. | |
| 7 | 399 |
| 400 Remarks: | |
|
2496
a29075150aee
Improve handling of user settings in :TOhtml. Default to generating CSS.
Bram Moolenaar <bram@vim.org>
parents:
2494
diff
changeset
|
401 - Some truly ancient browsers may not show the background colors. |
| 7 | 402 - From most browsers you can also print the file (in color)! |
| 3713 | 403 - The latest TOhtml may actually work with older versions of Vim, but some |
| 2642 | 404 features such as conceal support will not function, and the colors may be |
| 405 incorrect for an old Vim without GUI support compiled in. | |
| 7 | 406 |
| 407 Here is an example how to run the script over all .c and .h files from a | |
| 408 Unix shell: > | |
| 409 for f in *.[ch]; do gvim -f +"syn on" +"run! syntax/2html.vim" +"wq" +"q" $f; done | |
| 410 < | |
| 3713 | 411 *g:html_start_line* *g:html_end_line* |
| 412 To restrict the conversion to a range of lines, use a range with the |:TOhtml| | |
| 413 command below, or set "g:html_start_line" and "g:html_end_line" to the first | |
| 414 and last line to be converted. Example, using the last set Visual area: > | |
| 415 | |
| 416 :let g:html_start_line = line("'<") | |
| 417 :let g:html_end_line = line("'>") | |
| 418 :runtime! syntax/2html.vim | |
| 419 < | |
| 420 *:TOhtml* | |
| 421 :[range]TOhtml The ":TOhtml" command is defined in a standard plugin. | |
| 422 This command will source |2html.vim| for you. When a | |
| 423 range is given, set |g:html_start_line| and | |
| 424 |g:html_end_line| to the start and end of the range, | |
| 425 respectively. Default range is the entire buffer. | |
| 426 | |
| 427 If the current window is part of a |diff|, unless | |
| 428 |g:html_diff_one_file| is set, :TOhtml will convert | |
| 429 all windows which are part of the diff in the current | |
| 430 tab and place them side-by-side in a <table> element | |
|
4681
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4437
diff
changeset
|
431 in the generated HTML. When this happens you can jump |
|
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4437
diff
changeset
|
432 to lines in specific windows with (for example) #W1L42 |
|
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4437
diff
changeset
|
433 for line 42 in the first diffed window, or #W3L87 for |
|
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4437
diff
changeset
|
434 line 87 in the third. Omitting the window ID will |
|
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4437
diff
changeset
|
435 default to the first window if javascript is enabled. |
| 3713 | 436 |
| 437 Examples: > | |
| 438 | |
| 439 :10,40TOhtml " convert lines 10-40 to html | |
| 440 :'<,'>TOhtml " convert current/last visual selection | |
| 441 :TOhtml " convert entire buffer | |
| 442 < | |
| 443 *g:html_diff_one_file* | |
| 444 Default: 0. | |
| 445 When 0, all windows involved in a |diff| in the current tab page are converted | |
| 446 to HTML and placed side-by-side in a <table> element. | |
| 447 When 1, only the current buffer is converted. | |
| 448 Example: > | |
| 449 | |
| 450 let g:html_diff_one_file = 1 | |
| 451 < | |
| 452 *g:html_whole_filler* | |
| 453 Default: 0. | |
| 454 When 0, if |g:html_diff_one_file| is 1, a sequence of more than 3 filler lines | |
| 455 is displayed as three lines with the middle line mentioning the total number | |
| 456 of inserted lines. | |
| 457 When 1, always display all inserted lines as if |g:html_diff_one_file| were | |
| 458 not set. | |
| 459 > | |
| 460 :let g:html_whole_filler = 1 | |
| 461 < | |
| 462 *TOhtml-performance* *g:html_no_progress* | |
| 463 Default: 0. | |
| 464 When 0, display a progress bar in the statusline for each major step in the | |
| 465 2html.vim conversion process. | |
| 466 When 1, do not display the progress bar. This offers a minor speed improvement | |
| 467 but you won't have any idea how much longer the conversion might take; for big | |
| 468 files it can take a long time! | |
| 469 Example: > | |
| 470 | |
| 471 let g:html_no_progress = 1 | |
| 472 < | |
| 473 You can obtain better performance improvements by also instructing Vim to not | |
| 474 run interactively, so that too much time is not taken to redraw as the script | |
| 475 moves through the buffer, switches windows, and the like: > | |
| 476 | |
| 477 vim -E -s -c "let g:html_no_progress=1" -c "syntax on" -c "set ft=c" -c "runtime syntax/2html.vim" -cwqa myfile.c | |
| 478 < | |
| 479 Note that the -s flag prevents loading your .vimrc and any plugins, so you | |
| 480 need to explicitly source/enable anything that will affect the HTML | |
| 481 conversion. See |-E| and |-s-ex| for details. It is probably best to create a | |
| 482 script to replace all the -c commands and use it with the -u flag instead of | |
| 483 specifying each command separately. | |
| 484 | |
| 485 *g:html_number_lines* | |
| 486 Default: current 'number' setting. | |
| 487 When 0, buffer text is displayed in the generated HTML without line numbering. | |
| 488 When 1, a column of line numbers is added to the generated HTML with the same | |
| 489 highlighting as the line number column in Vim (|hl-LineNr|). | |
| 490 Force line numbers even if 'number' is not set: > | |
| 491 :let g:html_number_lines = 1 | |
| 492 Force to omit the line numbers: > | |
| 493 :let g:html_number_lines = 0 | |
| 494 Go back to the default to use 'number' by deleting the variable: > | |
| 495 :unlet g:html_number_lines | |
| 496 < | |
| 497 *g:html_use_css* | |
| 498 Default: 1. | |
| 499 When 1, generate valid HTML 4.01 markup with CSS1 styling, supported in all | |
| 500 modern browsers and most old browsers. | |
| 501 When 0, generate <font> tags and similar outdated markup. This is not | |
| 502 recommended but it may work better in really old browsers, email clients, | |
| 503 forum posts, and similar situations where basic CSS support is unavailable. | |
| 504 Example: > | |
| 505 :let g:html_use_css = 0 | |
| 506 < | |
| 507 *g:html_ignore_conceal* | |
| 508 Default: 0. | |
| 509 When 0, concealed text is removed from the HTML and replaced with a character | |
| 510 from |:syn-cchar| or 'listchars' as appropriate, depending on the current | |
| 511 value of 'conceallevel'. | |
| 512 When 1, include all text from the buffer in the generated HTML, even if it is | |
| 513 |conceal|ed. | |
| 514 | |
| 515 Either of the following commands will ensure that all text in the buffer is | |
| 516 included in the generated HTML (unless it is folded): > | |
| 517 :let g:html_ignore_conceal = 1 | |
| 518 :setl conceallevel=0 | |
| 519 < | |
| 520 *g:html_ignore_folding* | |
| 521 Default: 0. | |
| 522 When 0, text in a closed fold is replaced by the text shown for the fold in | |
| 523 Vim (|fold-foldtext|). See |g:html_dynamic_folds| if you also want to allow | |
| 524 the user to expand the fold as in Vim to see the text inside. | |
| 525 When 1, include all text from the buffer in the generated HTML; whether the | |
| 526 text is in a fold has no impact at all. |g:html_dynamic_folds| has no effect. | |
| 527 | |
| 528 Either of these commands will ensure that all text in the buffer is included | |
| 529 in the generated HTML (unless it is concealed): > | |
| 530 zR | |
| 531 :let g:html_ignore_folding = 1 | |
| 532 < | |
| 533 *g:html_dynamic_folds* | |
| 534 Default: 0. | |
| 535 When 0, text in a closed fold is not included at all in the generated HTML. | |
| 536 When 1, generate javascript to open a fold and show the text within, just like | |
| 537 in Vim. | |
| 538 | |
| 539 Setting this variable to 1 causes 2html.vim to always use CSS for styling, | |
| 540 regardless of what |g:html_use_css| is set to. | |
| 541 | |
| 542 This variable is ignored when |g:html_ignore_folding| is set. | |
| 543 > | |
| 544 :let g:html_dynamic_folds = 1 | |
| 545 < | |
| 546 *g:html_no_foldcolumn* | |
| 547 Default: 0. | |
| 548 When 0, if |g:html_dynamic_folds| is 1, generate a column of text similar to | |
| 549 Vim's foldcolumn (|fold-foldcolumn|) the user can click on to toggle folds | |
| 550 open or closed. The minimum width of the generated text column is the current | |
| 551 'foldcolumn' setting. | |
| 552 When 1, do not generate this column; instead, hovering the mouse cursor over | |
| 553 folded text will open the fold as if |g:html_hover_unfold| were set. | |
| 554 > | |
| 555 :let g:html_no_foldcolumn = 1 | |
| 556 < | |
| 557 *TOhtml-uncopyable-text* *g:html_prevent_copy* | |
| 558 Default: empty string. | |
| 559 This option prevents certain regions of the generated HTML from being copied, | |
| 560 when you select all text in document rendered in a browser and copy it. Useful | |
| 561 for allowing users to copy-paste only the source text even if a fold column or | |
| 562 line numbers are shown in the generated content. Specify regions to be | |
| 563 affected in this way as follows: | |
| 564 f: fold column | |
| 565 n: line numbers (also within fold text) | |
| 566 t: fold text | |
| 567 d: diff filler | |
| 568 | |
| 569 Example, to make the fold column and line numbers uncopyable: > | |
| 570 :let g:html_prevent_copy = "fn" | |
| 571 < | |
| 572 This feature is currently implemented by inserting read-only <input> elements | |
| 573 into the markup to contain the uncopyable areas. This does not work well in | |
| 574 all cases. When pasting to some applications which understand HTML, the | |
| 575 <input> elements also get pasted. But plain-text paste destinations should | |
| 576 always work. | |
| 577 | |
| 578 *g:html_no_invalid* | |
| 579 Default: 0. | |
| 580 When 0, if |g:html_prevent_copy| is non-empty, an invalid attribute is | |
| 581 intentionally inserted into the <input> element for the uncopyable areas. This | |
| 582 increases the number of applications you can paste to without also pasting the | |
| 583 <input> elements. Specifically, Microsoft Word will not paste the <input> | |
| 584 elements if they contain this invalid attribute. | |
| 585 When 1, no invalid markup is ever intentionally inserted, and the generated | |
| 586 page should validate. However, be careful pasting into Microsoft Word when | |
| 587 |g:html_prevent_copy| is non-empty; it can be hard to get rid of the <input> | |
| 588 elements which get pasted. | |
| 589 | |
| 590 *g:html_hover_unfold* | |
| 591 Default: 0. | |
| 592 When 0, the only way to open a fold generated by 2html.vim with | |
| 593 |g:html_dynamic_folds| set, is to click on the generated fold column. | |
| 594 When 1, use CSS 2.0 to allow the user to open a fold by moving the mouse | |
| 595 cursor over the displayed fold text. This is useful to allow users with | |
| 596 disabled javascript to view the folded text. | |
| 597 | |
| 598 Note that old browsers (notably Internet Explorer 6) will not support this | |
| 599 feature. Browser-specific markup for IE6 is included to fall back to the | |
| 600 normal CSS1 styling so that the folds show up correctly for this browser, but | |
| 601 they will not be openable without a foldcolumn. | |
| 602 > | |
| 603 :let g:html_hover_unfold = 1 | |
| 604 < | |
| 605 *TOhtml-wrap-text* *g:html_pre_wrap* | |
| 606 Default: current 'wrap' setting. | |
| 607 When 0, if |g:html_no_pre| is 0 or unset, the text in the generated HTML does | |
| 608 not wrap at the edge of the browser window. | |
| 609 When 1, if |g:html_use_css| is 1, the CSS 2.0 "white-space:pre-wrap" value is | |
| 610 used, causing the text to wrap at whitespace at the edge of the browser | |
| 611 window. | |
| 612 Explicitly enable text wrapping: > | |
| 613 :let g:html_pre_wrap = 1 | |
| 614 Explicitly disable wrapping: > | |
| 615 :let g:html_pre_wrap = 0 | |
| 616 Go back to default, determine wrapping from 'wrap' setting: > | |
| 617 :unlet g:html_pre_wrap | |
| 618 < | |
| 619 *g:html_no_pre* | |
| 620 Default: 0. | |
| 621 When 0, buffer text in the generated HTML is surrounded by <pre>...</pre> | |
| 622 tags. Series of whitespace is shown as in Vim without special markup, and tab | |
| 623 characters can be included literally (see |g:html_expand_tabs|). | |
| 624 When 1 (not recommended), the <pre> tags are omitted, and a plain <div> is | |
| 625 used instead. Whitespace is replaced by a series of character | |
| 626 references, and <br> is used to end each line. This is another way to allow | |
| 627 text in the generated HTML is wrap (see |g:html_pre_wrap|) which also works in | |
| 628 old browsers, but may cause noticeable differences between Vim's display and | |
| 629 the rendered page generated by 2html.vim. | |
| 630 > | |
| 631 :let g:html_no_pre = 1 | |
| 632 < | |
| 633 *g:html_expand_tabs* | |
| 634 Default: 1 if 'tabstop' is 8, 'expandtab' is 0, and no fold column or line | |
| 635 numbers occur in the generated HTML; | |
| 636 0 otherwise. | |
| 637 When 0, <Tab> characters in the buffer text are replaced with an appropriate | |
| 638 number of space characters, or references if |g:html_no_pre| is 1. | |
| 639 When 1, if |g:html_no_pre| is 0 or unset, <Tab> characters in the buffer text | |
| 640 are included as-is in the generated HTML. This is useful for when you want to | |
| 641 allow copy and paste from a browser without losing the actual whitespace in | |
| 642 the source document. Note that this can easily break text alignment and | |
| 643 indentation in the HTML, unless set by default. | |
| 644 | |
| 645 Force |2html.vim| to keep <Tab> characters: > | |
| 646 :let g:html_expand_tabs = 0 | |
| 647 < | |
| 648 Force tabs to be expanded: > | |
| 649 :let g:html_expand_tabs = 1 | |
| 650 < | |
| 651 *TOhtml-encoding-detect* *TOhtml-encoding* | |
| 652 It is highly recommended to set your desired encoding with | |
| 653 |g:html_use_encoding| for any content which will be placed on a web server. | |
| 654 | |
| 655 If you do not specify an encoding, |2html.vim| uses the preferred IANA name | |
| 656 for the current value of 'fileencoding' if set, or 'encoding' if not. | |
| 657 'encoding' is always used for certain 'buftype' values. 'fileencoding' will be | |
| 658 set to match the chosen document encoding. | |
| 659 | |
| 660 Automatic detection works for the encodings mentioned specifically by name in | |
| 661 |encoding-names|, but TOhtml will only automatically use those encodings with | |
| 662 wide browser support. However, you can override this to support specific | |
| 663 encodings that may not be automatically detected by default (see options | |
| 664 below). See http://www.iana.org/assignments/character-sets for the IANA names. | |
| 665 | |
| 666 Note, by default all Unicode encodings are converted to UTF-8 with no BOM in | |
| 667 the generated HTML, as recommended by W3C: | |
| 668 | |
| 669 http://www.w3.org/International/questions/qa-choosing-encodings | |
| 670 http://www.w3.org/International/questions/qa-byte-order-mark | |
| 671 | |
| 672 *g:html_use_encoding* | |
| 673 Default: none, uses IANA name for current 'fileencoding' as above. | |
| 674 To overrule all automatic charset detection, set g:html_use_encoding to the | |
| 675 name of the charset to be used. It is recommended to set this variable to | |
| 676 something widely supported, like UTF-8, for anything you will be hosting on a | |
| 677 webserver: > | |
| 678 :let g:html_use_encoding = "UTF-8" | |
| 679 You can also use this option to omit the line that specifies the charset | |
| 680 entirely, by setting g:html_use_encoding to an empty string (NOT recommended): > | |
| 681 :let g:html_use_encoding = "" | |
| 682 To go back to the automatic mechanism, delete the |g:html_use_encoding| | |
| 683 variable: > | |
| 684 :unlet g:html_use_encoding | |
| 685 < | |
| 686 *g:html_encoding_override* | |
| 687 Default: none, autoload/tohtml.vim contains default conversions for encodings | |
| 688 mentioned by name at |encoding-names|. | |
| 689 This option allows |2html.vim| to detect the correct 'fileencoding' when you | |
| 690 specify an encoding with |g:html_use_encoding| which is not in the default | |
| 691 list of conversions. | |
| 692 | |
| 693 This is a dictionary of charset-encoding pairs that will replace existing | |
| 694 pairs automatically detected by TOhtml, or supplement with new pairs. | |
| 695 | |
| 696 Detect the HTML charset "windows-1252" as the encoding "8bit-cp1252": > | |
| 697 :let g:html_encoding_override = {'windows-1252': '8bit-cp1252'} | |
| 698 < | |
| 699 *g:html_charset_override* | |
| 700 Default: none, autoload/tohtml.vim contains default conversions for encodings | |
| 701 mentioned by name at |encoding-names| and which have wide | |
| 702 browser support. | |
| 703 This option allows |2html.vim| to detect the HTML charset for any | |
| 704 'fileencoding' or 'encoding' which is not detected automatically. You can also | |
| 705 use it to override specific existing encoding-charset pairs. For example, | |
| 706 TOhtml will by default use UTF-8 for all Unicode/UCS encodings. To use UTF-16 | |
| 707 and UTF-32 instead, use: > | |
| 708 :let g:html_charset_override = {'ucs-4': 'UTF-32', 'utf-16': 'UTF-16'} | |
| 709 | |
| 710 Note that documents encoded in either UTF-32 or UTF-16 have known | |
| 711 compatibility problems with some major browsers. | |
| 712 | |
| 713 *convert-to-XML* *convert-to-XHTML* *g:html_use_xhtml* | |
| 714 Default: 0. | |
| 715 When 0, generate standard HTML 4.01 (strict when possible). | |
| 716 When 1, generate XHTML 1.0 instead (XML compliant HTML). | |
| 717 > | |
| 718 :let g:html_use_xhtml = 1 | |
| 719 < | |
| 7 | 720 |
| 501 | 721 ABEL *abel.vim* *ft-abel-syntax* |
| 7 | 722 |
| 723 ABEL highlighting provides some user-defined options. To enable them, assign | |
| 724 any value to the respective variable. Example: > | |
| 725 :let abel_obsolete_ok=1 | |
| 726 To disable them use ":unlet". Example: > | |
| 727 :unlet abel_obsolete_ok | |
| 728 | |
| 729 Variable Highlight ~ | |
| 730 abel_obsolete_ok obsolete keywords are statements, not errors | |
| 731 abel_cpp_comments_illegal do not interpret '//' as inline comment leader | |
| 732 | |
| 733 | |
| 1125 | 734 ADA |
| 735 | |
| 736 See |ft-ada-syntax| | |
| 7 | 737 |
| 738 | |
| 501 | 739 ANT *ant.vim* *ft-ant-syntax* |
| 7 | 740 |
| 741 The ant syntax file provides syntax highlighting for javascript and python | |
| 237 | 742 by default. Syntax highlighting for other script languages can be installed |
| 7 | 743 by the function AntSyntaxScript(), which takes the tag name as first argument |
| 237 | 744 and the script syntax file name as second argument. Example: > |
| 7 | 745 |
| 746 :call AntSyntaxScript('perl', 'perl.vim') | |
| 747 | |
| 748 will install syntax perl highlighting for the following ant code > | |
| 749 | |
| 750 <script language = 'perl'><![CDATA[ | |
| 751 # everything inside is highlighted as perl | |
| 752 ]]></script> | |
| 753 | |
| 754 See |mysyntaxfile-add| for installing script languages permanently. | |
| 755 | |
| 756 | |
| 501 | 757 APACHE *apache.vim* *ft-apache-syntax* |
| 7 | 758 |
| 759 The apache syntax file provides syntax highlighting depending on Apache HTTP | |
| 760 server version, by default for 1.3.x. Set "apache_version" to Apache version | |
| 761 (as a string) to get highlighting for another version. Example: > | |
| 762 | |
| 763 :let apache_version = "2.0" | |
| 764 < | |
| 765 | |
| 766 *asm.vim* *asmh8300.vim* *nasm.vim* *masm.vim* *asm68k* | |
| 501 | 767 ASSEMBLY *ft-asm-syntax* *ft-asmh8300-syntax* *ft-nasm-syntax* |
| 768 *ft-masm-syntax* *ft-asm68k-syntax* *fasm.vim* | |
| 7 | 769 |
| 770 Files matching "*.i" could be Progress or Assembly. If the automatic detection | |
| 771 doesn't work for you, or you don't edit Progress at all, use this in your | |
| 772 startup vimrc: > | |
| 773 :let filetype_i = "asm" | |
| 774 Replace "asm" with the type of assembly you use. | |
| 775 | |
| 776 There are many types of assembly languages that all use the same file name | |
| 777 extensions. Therefore you will have to select the type yourself, or add a | |
| 778 line in the assembly file that Vim will recognize. Currently these syntax | |
| 779 files are included: | |
| 780 asm GNU assembly (the default) | |
| 781 asm68k Motorola 680x0 assembly | |
| 782 asmh8300 Hitachi H-8300 version of GNU assembly | |
| 783 ia64 Intel Itanium 64 | |
| 784 fasm Flat assembly (http://flatassembler.net) | |
| 785 masm Microsoft assembly (probably works for any 80x86) | |
| 786 nasm Netwide assembly | |
| 787 tasm Turbo Assembly (with opcodes 80x86 up to Pentium, and | |
| 788 MMX) | |
| 789 pic PIC assembly (currently for PIC16F84) | |
| 790 | |
| 791 The most flexible is to add a line in your assembly file containing: > | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
792 asmsyntax=nasm |
| 7 | 793 Replace "nasm" with the name of the real assembly syntax. This line must be |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
794 one of the first five lines in the file. No non-white text must be |
| 3682 | 795 immediately before or after this text. Note that specifying asmsyntax=foo is |
| 796 equivalent to setting ft=foo in a |modeline|, and that in case of a conflict | |
| 797 between the two settings the one from the modeline will take precedence (in | |
| 798 particular, if you have ft=asm in the modeline, you will get the GNU syntax | |
| 799 highlighting regardless of what is specified as asmsyntax). | |
| 7 | 800 |
| 801 The syntax type can always be overruled for a specific buffer by setting the | |
| 802 b:asmsyntax variable: > | |
| 1624 | 803 :let b:asmsyntax = "nasm" |
| 7 | 804 |
| 805 If b:asmsyntax is not set, either automatically or by hand, then the value of | |
| 806 the global variable asmsyntax is used. This can be seen as a default assembly | |
| 807 language: > | |
| 1624 | 808 :let asmsyntax = "nasm" |
| 7 | 809 |
| 810 As a last resort, if nothing is defined, the "asm" syntax is used. | |
| 811 | |
| 812 | |
| 813 Netwide assembler (nasm.vim) optional highlighting ~ | |
| 814 | |
| 815 To enable a feature: > | |
| 816 :let {variable}=1|set syntax=nasm | |
| 817 To disable a feature: > | |
| 818 :unlet {variable} |set syntax=nasm | |
| 819 | |
| 820 Variable Highlight ~ | |
| 821 nasm_loose_syntax unofficial parser allowed syntax not as Error | |
| 822 (parser dependent; not recommended) | |
| 823 nasm_ctx_outside_macro contexts outside macro not as Error | |
| 824 nasm_no_warn potentially risky syntax not as ToDo | |
| 825 | |
| 826 | |
| 501 | 827 ASPPERL and ASPVBS *ft-aspperl-syntax* *ft-aspvbs-syntax* |
| 7 | 828 |
| 829 *.asp and *.asa files could be either Perl or Visual Basic script. Since it's | |
| 830 hard to detect this you can set two global variables to tell Vim what you are | |
| 831 using. For Perl script use: > | |
| 832 :let g:filetype_asa = "aspperl" | |
| 833 :let g:filetype_asp = "aspperl" | |
| 834 For Visual Basic use: > | |
| 835 :let g:filetype_asa = "aspvbs" | |
| 836 :let g:filetype_asp = "aspvbs" | |
| 837 | |
| 838 | |
| 856 | 839 BAAN *baan.vim* *baan-syntax* |
| 844 | 840 |
| 841 The baan.vim gives syntax support for BaanC of release BaanIV upto SSA ERP LN | |
| 842 for both 3 GL and 4 GL programming. Large number of standard defines/constants | |
| 843 are supported. | |
| 844 | |
| 845 Some special violation of coding standards will be signalled when one specify | |
| 846 in ones |.vimrc|: > | |
| 847 let baan_code_stds=1 | |
| 848 | |
| 849 *baan-folding* | |
| 850 | |
| 851 Syntax folding can be enabled at various levels through the variables | |
| 852 mentioned below (Set those in your |.vimrc|). The more complex folding on | |
| 853 source blocks and SQL can be CPU intensive. | |
| 854 | |
| 855 To allow any folding and enable folding at function level use: > | |
| 856 let baan_fold=1 | |
| 857 Folding can be enabled at source block level as if, while, for ,... The | |
| 858 indentation preceding the begin/end keywords has to match (spaces are not | |
| 859 considered equal to a tab). > | |
| 860 let baan_fold_block=1 | |
| 861 Folding can be enabled for embedded SQL blocks as SELECT, SELECTDO, | |
| 856 | 862 SELECTEMPTY, ... The indentation preceding the begin/end keywords has to |
| 844 | 863 match (spaces are not considered equal to a tab). > |
| 864 let baan_fold_sql=1 | |
| 856 | 865 Note: Block folding can result in many small folds. It is suggested to |:set| |
| 844 | 866 the options 'foldminlines' and 'foldnestmax' in |.vimrc| or use |:setlocal| in |
| 867 .../after/syntax/baan.vim (see |after-directory|). Eg: > | |
| 868 set foldminlines=5 | |
| 869 set foldnestmax=6 | |
| 870 | |
| 871 | |
| 501 | 872 BASIC *basic.vim* *vb.vim* *ft-basic-syntax* *ft-vb-syntax* |
| 7 | 873 |
| 874 Both Visual Basic and "normal" basic use the extension ".bas". To detect | |
| 875 which one should be used, Vim checks for the string "VB_Name" in the first | |
| 876 five lines of the file. If it is not found, filetype will be "basic", | |
| 877 otherwise "vb". Files with the ".frm" extension will always be seen as Visual | |
| 878 Basic. | |
| 879 | |
| 880 | |
| 501 | 881 C *c.vim* *ft-c-syntax* |
| 7 | 882 |
| 883 A few things in C highlighting are optional. To enable them assign any value | |
| 884 to the respective variable. Example: > | |
| 1624 | 885 :let c_comment_strings = 1 |
| 7 | 886 To disable them use ":unlet". Example: > |
| 887 :unlet c_comment_strings | |
| 888 | |
| 889 Variable Highlight ~ | |
| 890 c_gnu GNU gcc specific items | |
| 891 c_comment_strings strings and numbers inside a comment | |
| 892 c_space_errors trailing white space and spaces before a <Tab> | |
| 893 c_no_trail_space_error ... but no trailing spaces | |
| 894 c_no_tab_space_error ... but no spaces before a <Tab> | |
| 895 c_no_bracket_error don't highlight {}; inside [] as errors | |
| 140 | 896 c_no_curly_error don't highlight {}; inside [] and () as errors; |
| 897 except { and } in first column | |
| 1624 | 898 c_curly_error highlight a missing }; this forces syncing from the |
| 899 start of the file, can be slow | |
| 7 | 900 c_no_ansi don't do standard ANSI types and constants |
| 901 c_ansi_typedefs ... but do standard ANSI types | |
| 902 c_ansi_constants ... but do standard ANSI constants | |
| 903 c_no_utf don't highlight \u and \U in strings | |
| 3445 | 904 c_syntax_for_h for *.h files use C syntax instead of C++ and use objc |
| 905 syntax instead of objcpp | |
| 7 | 906 c_no_if0 don't highlight "#if 0" blocks as comments |
| 907 c_no_cformat don't highlight %-formats in strings | |
| 908 c_no_c99 don't highlight C99 standard items | |
| 3256 | 909 c_no_c11 don't highlight C11 standard items |
| 7 | 910 |
| 36 | 911 When 'foldmethod' is set to "syntax" then /* */ comments and { } blocks will |
| 912 become a fold. If you don't want comments to become a fold use: > | |
| 913 :let c_no_comment_fold = 1 | |
| 842 | 914 "#if 0" blocks are also folded, unless: > |
| 915 :let c_no_if0_fold = 1 | |
| 36 | 916 |
| 7 | 917 If you notice highlighting errors while scrolling backwards, which are fixed |
| 918 when redrawing with CTRL-L, try setting the "c_minlines" internal variable | |
| 919 to a larger number: > | |
| 920 :let c_minlines = 100 | |
| 921 This will make the syntax synchronization start 100 lines before the first | |
| 922 displayed line. The default value is 50 (15 when c_no_if0 is set). The | |
| 923 disadvantage of using a larger number is that redrawing can become slow. | |
| 924 | |
| 925 When using the "#if 0" / "#endif" comment highlighting, notice that this only | |
| 926 works when the "#if 0" is within "c_minlines" from the top of the window. If | |
| 927 you have a long "#if 0" construct it will not be highlighted correctly. | |
| 928 | |
| 929 To match extra items in comments, use the cCommentGroup cluster. | |
| 930 Example: > | |
| 931 :au Syntax c call MyCadd() | |
| 932 :function MyCadd() | |
| 933 : syn keyword cMyItem contained Ni | |
| 934 : syn cluster cCommentGroup add=cMyItem | |
| 935 : hi link cMyItem Title | |
| 936 :endfun | |
| 937 | |
| 938 ANSI constants will be highlighted with the "cConstant" group. This includes | |
| 939 "NULL", "SIG_IGN" and others. But not "TRUE", for example, because this is | |
| 940 not in the ANSI standard. If you find this confusing, remove the cConstant | |
| 941 highlighting: > | |
| 942 :hi link cConstant NONE | |
| 943 | |
| 944 If you see '{' and '}' highlighted as an error where they are OK, reset the | |
| 945 highlighting for cErrInParen and cErrInBracket. | |
| 946 | |
| 947 If you want to use folding in your C files, you can add these lines in a file | |
|
2207
b17bbfa96fa0
Add the settabvar() and gettabvar() functions.
Bram Moolenaar <bram@vim.org>
parents:
2178
diff
changeset
|
948 in the "after" directory in 'runtimepath'. For Unix this would be |
| 7 | 949 ~/.vim/after/syntax/c.vim. > |
| 950 syn sync fromstart | |
| 951 set foldmethod=syntax | |
| 952 | |
| 501 | 953 CH *ch.vim* *ft-ch-syntax* |
| 22 | 954 |
| 955 C/C++ interpreter. Ch has similar syntax highlighting to C and builds upon | |
| 956 the C syntax file. See |c.vim| for all the settings that are available for C. | |
| 957 | |
| 958 By setting a variable you can tell Vim to use Ch syntax for *.h files, instead | |
| 959 of C or C++: > | |
| 960 :let ch_syntax_for_h = 1 | |
| 961 | |
| 7 | 962 |
| 501 | 963 CHILL *chill.vim* *ft-chill-syntax* |
| 7 | 964 |
| 965 Chill syntax highlighting is similar to C. See |c.vim| for all the settings | |
| 966 that are available. Additionally there is: | |
| 967 | |
| 968 chill_space_errors like c_space_errors | |
| 969 chill_comment_string like c_comment_strings | |
| 970 chill_minlines like c_minlines | |
| 971 | |
| 972 | |
| 501 | 973 CHANGELOG *changelog.vim* *ft-changelog-syntax* |
| 7 | 974 |
| 975 ChangeLog supports highlighting spaces at the start of a line. | |
| 976 If you do not like this, add following line to your .vimrc: > | |
| 977 let g:changelog_spacing_errors = 0 | |
| 978 This works the next time you edit a changelog file. You can also use | |
| 979 "b:changelog_spacing_errors" to set this per buffer (before loading the syntax | |
| 980 file). | |
| 981 | |
| 982 You can change the highlighting used, e.g., to flag the spaces as an error: > | |
| 983 :hi link ChangelogError Error | |
| 984 Or to avoid the highlighting: > | |
| 985 :hi link ChangelogError NONE | |
| 986 This works immediately. | |
| 987 | |
| 988 | |
| 501 | 989 COBOL *cobol.vim* *ft-cobol-syntax* |
| 7 | 990 |
| 991 COBOL highlighting has different needs for legacy code than it does for fresh | |
| 992 development. This is due to differences in what is being done (maintenance | |
| 993 versus development) and other factors. To enable legacy code highlighting, | |
| 994 add this line to your .vimrc: > | |
| 995 :let cobol_legacy_code = 1 | |
| 996 To disable it again, use this: > | |
| 997 :unlet cobol_legacy_code | |
| 998 | |
| 999 | |
| 501 | 1000 COLD FUSION *coldfusion.vim* *ft-coldfusion-syntax* |
| 7 | 1001 |
| 237 | 1002 The ColdFusion has its own version of HTML comments. To turn on ColdFusion |
| 7 | 1003 comment highlighting, add the following line to your startup file: > |
| 1004 | |
| 1005 :let html_wrong_comments = 1 | |
| 1006 | |
| 1007 The ColdFusion syntax file is based on the HTML syntax file. | |
| 1008 | |
| 1009 | |
| 4186 | 1010 CPP *cpp.vim* *ft-cpp-syntax* |
| 1011 | |
| 1012 Most of things are same as |ft-c-syntax|. | |
| 1013 | |
| 1014 Variable Highlight ~ | |
| 1015 cpp_no_c11 don't highlight C++11 standard items | |
| 1016 | |
| 1017 | |
| 501 | 1018 CSH *csh.vim* *ft-csh-syntax* |
| 7 | 1019 |
| 1020 This covers the shell named "csh". Note that on some systems tcsh is actually | |
| 1021 used. | |
| 1022 | |
| 1023 Detecting whether a file is csh or tcsh is notoriously hard. Some systems | |
| 1024 symlink /bin/csh to /bin/tcsh, making it almost impossible to distinguish | |
| 1025 between csh and tcsh. In case VIM guesses wrong you can set the | |
| 2965 | 1026 "filetype_csh" variable. For using csh: *g:filetype_csh* |
| 1027 > | |
| 1028 :let g:filetype_csh = "csh" | |
| 7 | 1029 |
| 1030 For using tcsh: > | |
| 1031 | |
| 2965 | 1032 :let g:filetype_csh = "tcsh" |
| 7 | 1033 |
| 1034 Any script with a tcsh extension or a standard tcsh filename (.tcshrc, | |
| 1035 tcsh.tcshrc, tcsh.login) will have filetype tcsh. All other tcsh/csh scripts | |
| 237 | 1036 will be classified as tcsh, UNLESS the "filetype_csh" variable exists. If the |
| 7 | 1037 "filetype_csh" variable exists, the filetype will be set to the value of the |
| 1038 variable. | |
| 1039 | |
| 1040 | |
| 501 | 1041 CYNLIB *cynlib.vim* *ft-cynlib-syntax* |
| 7 | 1042 |
| 1043 Cynlib files are C++ files that use the Cynlib class library to enable | |
| 237 | 1044 hardware modelling and simulation using C++. Typically Cynlib files have a .cc |
| 7 | 1045 or a .cpp extension, which makes it very difficult to distinguish them from a |
| 237 | 1046 normal C++ file. Thus, to enable Cynlib highlighting for .cc files, add this |
| 7 | 1047 line to your .vimrc file: > |
| 1048 | |
| 1049 :let cynlib_cyntax_for_cc=1 | |
| 1050 | |
| 1051 Similarly for cpp files (this extension is only usually used in Windows) > | |
| 1052 | |
| 1053 :let cynlib_cyntax_for_cpp=1 | |
| 1054 | |
| 1055 To disable these again, use this: > | |
| 1056 | |
| 1057 :unlet cynlib_cyntax_for_cc | |
| 1058 :unlet cynlib_cyntax_for_cpp | |
| 1059 < | |
| 1060 | |
| 501 | 1061 CWEB *cweb.vim* *ft-cweb-syntax* |
| 7 | 1062 |
| 1063 Files matching "*.w" could be Progress or cweb. If the automatic detection | |
| 1064 doesn't work for you, or you don't edit Progress at all, use this in your | |
| 1065 startup vimrc: > | |
| 1066 :let filetype_w = "cweb" | |
| 1067 | |
| 1068 | |
| 501 | 1069 DESKTOP *desktop.vim* *ft-desktop-syntax* |
| 7 | 1070 |
| 1071 Primary goal of this syntax file is to highlight .desktop and .directory files | |
|
2236
dc2e5ec0500d
Added the undofile() function. Updated runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
1072 according to freedesktop.org standard: |
|
dc2e5ec0500d
Added the undofile() function. Updated runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
1073 http://standards.freedesktop.org/desktop-entry-spec/latest/ |
| 7 | 1074 But actually almost none implements this standard fully. Thus it will |
| 237 | 1075 highlight all Unix ini files. But you can force strict highlighting according |
| 7 | 1076 to standard by placing this in your vimrc file: > |
| 1077 :let enforce_freedesktop_standard = 1 | |
| 1078 | |
| 1079 | |
| 501 | 1080 DIRCOLORS *dircolors.vim* *ft-dircolors-syntax* |
| 7 | 1081 |
| 1082 The dircolors utility highlighting definition has one option. It exists to | |
| 1083 provide compatibility with the Slackware GNU/Linux distributions version of | |
| 1084 the command. It adds a few keywords that are generally ignored by most | |
| 1085 versions. On Slackware systems, however, the utility accepts the keywords and | |
| 1086 uses them for processing. To enable the Slackware keywords add the following | |
| 1087 line to your startup file: > | |
| 1088 let dircolors_is_slackware = 1 | |
| 1089 | |
| 1090 | |
| 501 | 1091 DOCBOOK *docbk.vim* *ft-docbk-syntax* *docbook* |
| 2662 | 1092 DOCBOOK XML *docbkxml.vim* *ft-docbkxml-syntax* |
| 1093 DOCBOOK SGML *docbksgml.vim* *ft-docbksgml-syntax* | |
| 7 | 1094 |
| 1095 There are two types of DocBook files: SGML and XML. To specify what type you | |
| 1096 are using the "b:docbk_type" variable should be set. Vim does this for you | |
| 1097 automatically if it can recognize the type. When Vim can't guess it the type | |
| 1098 defaults to XML. | |
| 1099 You can set the type manually: > | |
| 1100 :let docbk_type = "sgml" | |
| 1101 or: > | |
| 1102 :let docbk_type = "xml" | |
| 1103 You need to do this before loading the syntax file, which is complicated. | |
| 1104 Simpler is setting the filetype to "docbkxml" or "docbksgml": > | |
| 1105 :set filetype=docbksgml | |
| 1106 or: > | |
| 1107 :set filetype=docbkxml | |
| 1108 | |
| 3967 | 1109 You can specify the DocBook version: > |
| 1110 :let docbk_ver = 3 | |
| 1111 When not set 4 is used. | |
| 1112 | |
| 7 | 1113 |
| 501 | 1114 DOSBATCH *dosbatch.vim* *ft-dosbatch-syntax* |
| 7 | 1115 |
| 1116 There is one option with highlighting DOS batch files. This covers new | |
| 1117 extensions to the Command Interpreter introduced with Windows 2000 and | |
| 1118 is controlled by the variable dosbatch_cmdextversion. For Windows NT | |
| 1119 this should have the value 1, and for Windows 2000 it should be 2. | |
| 1120 Select the version you want with the following line: > | |
| 1121 | |
| 15 | 1122 :let dosbatch_cmdextversion = 1 |
| 7 | 1123 |
| 1124 If this variable is not defined it defaults to a value of 2 to support | |
| 1125 Windows 2000. | |
| 1126 | |
| 15 | 1127 A second option covers whether *.btm files should be detected as type |
| 237 | 1128 "dosbatch" (MS-DOS batch files) or type "btm" (4DOS batch files). The latter |
| 1129 is used by default. You may select the former with the following line: > | |
| 15 | 1130 |
| 1131 :let g:dosbatch_syntax_for_btm = 1 | |
| 1132 | |
| 1133 If this variable is undefined or zero, btm syntax is selected. | |
| 1134 | |
| 1135 | |
| 832 | 1136 DOXYGEN *doxygen.vim* *doxygen-syntax* |
| 1137 | |
| 1138 Doxygen generates code documentation using a special documentation format | |
| 1698 | 1139 (similar to Javadoc). This syntax script adds doxygen highlighting to c, cpp, |
| 1140 idl and php files, and should also work with java. | |
| 832 | 1141 |
| 1224 | 1142 There are a few of ways to turn on doxygen formatting. It can be done |
| 1143 explicitly or in a modeline by appending '.doxygen' to the syntax of the file. | |
| 1144 Example: > | |
| 832 | 1145 :set syntax=c.doxygen |
| 1146 or > | |
| 1147 // vim:syntax=c.doxygen | |
| 1148 | |
| 3356 | 1149 It can also be done automatically for C, C++, C#, IDL and PHP files by setting |
| 1150 the global or buffer-local variable load_doxygen_syntax. This is done by | |
| 1151 adding the following to your .vimrc. > | |
| 832 | 1152 :let g:load_doxygen_syntax=1 |
| 1153 | |
|
2207
b17bbfa96fa0
Add the settabvar() and gettabvar() functions.
Bram Moolenaar <bram@vim.org>
parents:
2178
diff
changeset
|
1154 There are a couple of variables that have an effect on syntax highlighting, and |
| 832 | 1155 are to do with non-standard highlighting options. |
| 1156 | |
| 1157 Variable Default Effect ~ | |
| 1158 g:doxygen_enhanced_color | |
| 1159 g:doxygen_enhanced_colour 0 Use non-standard highlighting for | |
| 1160 doxygen comments. | |
| 1161 | |
| 1162 doxygen_my_rendering 0 Disable rendering of HTML bold, italic | |
| 1163 and html_my_rendering underline. | |
| 1164 | |
| 1165 doxygen_javadoc_autobrief 1 Set to 0 to disable javadoc autobrief | |
| 1166 colour highlighting. | |
| 1167 | |
| 1168 doxygen_end_punctuation '[.]' Set to regexp match for the ending | |
| 856 | 1169 punctuation of brief |
| 832 | 1170 |
| 1171 There are also some hilight groups worth mentioning as they can be useful in | |
| 1172 configuration. | |
| 1173 | |
| 1174 Highlight Effect ~ | |
| 1175 doxygenErrorComment The colour of an end-comment when missing | |
| 1176 punctuation in a code, verbatim or dot section | |
| 1177 doxygenLinkError The colour of an end-comment when missing the | |
| 1178 \endlink from a \link section. | |
| 1179 | |
| 7 | 1180 |
| 501 | 1181 DTD *dtd.vim* *ft-dtd-syntax* |
| 7 | 1182 |
| 237 | 1183 The DTD syntax highlighting is case sensitive by default. To disable |
| 7 | 1184 case-sensitive highlighting, add the following line to your startup file: > |
| 1185 | |
| 1186 :let dtd_ignore_case=1 | |
| 1187 | |
| 237 | 1188 The DTD syntax file will highlight unknown tags as errors. If |
| 7 | 1189 this is annoying, it can be turned off by setting: > |
| 1190 | |
| 1191 :let dtd_no_tag_errors=1 | |
| 1192 | |
| 1193 before sourcing the dtd.vim syntax file. | |
| 1194 Parameter entity names are highlighted in the definition using the | |
| 1195 'Type' highlighting group and 'Comment' for punctuation and '%'. | |
| 1196 Parameter entity instances are highlighted using the 'Constant' | |
| 1197 highlighting group and the 'Type' highlighting group for the | |
| 237 | 1198 delimiters % and ;. This can be turned off by setting: > |
| 7 | 1199 |
| 1200 :let dtd_no_param_entities=1 | |
| 1201 | |
| 1202 The DTD syntax file is also included by xml.vim to highlight included dtd's. | |
| 1203 | |
| 1204 | |
| 501 | 1205 EIFFEL *eiffel.vim* *ft-eiffel-syntax* |
| 7 | 1206 |
| 1207 While Eiffel is not case-sensitive, its style guidelines are, and the | |
| 237 | 1208 syntax highlighting file encourages their use. This also allows to |
| 1209 highlight class names differently. If you want to disable case-sensitive | |
| 7 | 1210 highlighting, add the following line to your startup file: > |
| 1211 | |
| 1212 :let eiffel_ignore_case=1 | |
| 1213 | |
| 1214 Case still matters for class names and TODO marks in comments. | |
| 1215 | |
| 1216 Conversely, for even stricter checks, add one of the following lines: > | |
| 1217 | |
| 1218 :let eiffel_strict=1 | |
| 1219 :let eiffel_pedantic=1 | |
| 1220 | |
| 1221 Setting eiffel_strict will only catch improper capitalization for the | |
| 1222 five predefined words "Current", "Void", "Result", "Precursor", and | |
| 1223 "NONE", to warn against their accidental use as feature or class names. | |
| 1224 | |
| 1225 Setting eiffel_pedantic will enforce adherence to the Eiffel style | |
| 1226 guidelines fairly rigorously (like arbitrary mixes of upper- and | |
| 1227 lowercase letters as well as outdated ways to capitalize keywords). | |
| 1228 | |
| 1229 If you want to use the lower-case version of "Current", "Void", | |
| 1230 "Result", and "Precursor", you can use > | |
| 1231 | |
| 1232 :let eiffel_lower_case_predef=1 | |
| 1233 | |
| 1234 instead of completely turning case-sensitive highlighting off. | |
| 1235 | |
| 1236 Support for ISE's proposed new creation syntax that is already | |
| 1237 experimentally handled by some compilers can be enabled by: > | |
| 1238 | |
| 1239 :let eiffel_ise=1 | |
| 1240 | |
| 237 | 1241 Finally, some vendors support hexadecimal constants. To handle them, add > |
| 7 | 1242 |
| 1243 :let eiffel_hex_constants=1 | |
| 1244 | |
| 1245 to your startup file. | |
| 1246 | |
| 1247 | |
| 501 | 1248 ERLANG *erlang.vim* *ft-erlang-syntax* |
| 7 | 1249 |
| 4437 | 1250 Erlang is a functional programming language developed by Ericsson. Files with |
|
4681
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4437
diff
changeset
|
1251 the following extensions are recognized as Erlang files: erl, hrl, yaws. |
| 4437 | 1252 |
| 1253 The BIFs (built-in functions) are highlighted by default. To disable this, | |
| 1254 put the following line in your vimrc: > | |
| 1255 | |
| 1256 :let g:erlang_highlight_bifs = 0 | |
| 1257 | |
| 1258 To enable highlighting some special atoms, put this in your vimrc: > | |
| 1259 | |
| 1260 :let g:erlang_highlight_special_atoms = 1 | |
| 7 | 1261 |
| 1262 | |
| 857 | 1263 FLEXWIKI *flexwiki.vim* *ft-flexwiki-syntax* |
| 1264 | |
| 1265 FlexWiki is an ASP.NET-based wiki package available at http://www.flexwiki.com | |
| 2826 | 1266 NOTE: this site currently doesn't work, on Wikipedia is mentioned that |
| 1267 development stopped in 2009. | |
| 857 | 1268 |
| 1269 Syntax highlighting is available for the most common elements of FlexWiki | |
| 1270 syntax. The associated ftplugin script sets some buffer-local options to make | |
| 1271 editing FlexWiki pages more convenient. FlexWiki considers a newline as the | |
| 1272 start of a new paragraph, so the ftplugin sets 'tw'=0 (unlimited line length), | |
| 1273 'wrap' (wrap long lines instead of using horizontal scrolling), 'linebreak' | |
| 1274 (to wrap at a character in 'breakat' instead of at the last char on screen), | |
| 1275 and so on. It also includes some keymaps that are disabled by default. | |
| 1276 | |
| 1277 If you want to enable the keymaps that make "j" and "k" and the cursor keys | |
| 1278 move up and down by display lines, add this to your .vimrc: > | |
| 1279 :let flexwiki_maps = 1 | |
| 1280 | |
| 1281 | |
| 501 | 1282 FORM *form.vim* *ft-form-syntax* |
| 7 | 1283 |
| 1284 The coloring scheme for syntax elements in the FORM file uses the default | |
| 1285 modes Conditional, Number, Statement, Comment, PreProc, Type, and String, | |
| 1275 | 1286 following the language specifications in 'Symbolic Manipulation with FORM' by |
| 7 | 1287 J.A.M. Vermaseren, CAN, Netherlands, 1991. |
| 1288 | |
| 1289 If you want include your own changes to the default colors, you have to | |
| 1290 redefine the following syntax groups: | |
| 1291 | |
| 1292 - formConditional | |
| 1293 - formNumber | |
| 1294 - formStatement | |
| 1295 - formHeaderStatement | |
| 1296 - formComment | |
| 1297 - formPreProc | |
| 1298 - formDirective | |
| 1299 - formType | |
| 1300 - formString | |
| 1301 | |
| 1302 Note that the form.vim syntax file implements FORM preprocessor commands and | |
| 1303 directives per default in the same syntax group. | |
| 1304 | |
| 1305 A predefined enhanced color mode for FORM is available to distinguish between | |
| 237 | 1306 header statements and statements in the body of a FORM program. To activate |
| 7 | 1307 this mode define the following variable in your vimrc file > |
| 1308 | |
| 1309 :let form_enhanced_color=1 | |
| 1310 | |
| 1311 The enhanced mode also takes advantage of additional color features for a dark | |
| 237 | 1312 gvim display. Here, statements are colored LightYellow instead of Yellow, and |
| 7 | 1313 conditionals are LightBlue for better distinction. |
| 1314 | |
| 1315 | |
| 501 | 1316 FORTRAN *fortran.vim* *ft-fortran-syntax* |
| 7 | 1317 |
| 1318 Default highlighting and dialect ~ | |
| 3256 | 1319 Highlighting appropriate for Fortran 2008 is used by default. This choice |
| 1320 should be appropriate for most users most of the time because Fortran 2008 is | |
| 1321 almost a superset of previous versions (Fortran 2003, 95, 90, and 77). | |
| 7 | 1322 |
| 1323 Fortran source code form ~ | |
| 3281 | 1324 Fortran code can be in either fixed or free source form. Note that the |
| 7 | 1325 syntax highlighting will not be correct if the form is incorrectly set. |
| 1326 | |
| 1327 When you create a new fortran file, the syntax script assumes fixed source | |
| 237 | 1328 form. If you always use free source form, then > |
| 7 | 1329 :let fortran_free_source=1 |
| 237 | 1330 in your .vimrc prior to the :syntax on command. If you always use fixed source |
| 7 | 1331 form, then > |
| 1332 :let fortran_fixed_source=1 | |
| 1333 in your .vimrc prior to the :syntax on command. | |
| 1334 | |
| 1335 If the form of the source code depends upon the file extension, then it is | |
| 237 | 1336 most convenient to set fortran_free_source in a ftplugin file. For more |
| 1337 information on ftplugin files, see |ftplugin|. For example, if all your | |
| 7 | 1338 fortran files with an .f90 extension are written in free source form and the |
| 1339 rest in fixed source form, add the following code to your ftplugin file > | |
| 1340 let s:extfname = expand("%:e") | |
| 1341 if s:extfname ==? "f90" | |
| 1342 let fortran_free_source=1 | |
| 1343 unlet! fortran_fixed_source | |
| 1344 else | |
| 1345 let fortran_fixed_source=1 | |
| 1346 unlet! fortran_free_source | |
| 1347 endif | |
| 1348 Note that this will work only if the "filetype plugin indent on" command | |
| 1349 precedes the "syntax on" command in your .vimrc file. | |
| 1350 | |
| 1351 When you edit an existing fortran file, the syntax script will assume free | |
| 1352 source form if the fortran_free_source variable has been set, and assumes | |
| 237 | 1353 fixed source form if the fortran_fixed_source variable has been set. If |
| 7 | 1354 neither of these variables have been set, the syntax script attempts to |
| 1355 determine which source form has been used by examining the first five columns | |
| 819 | 1356 of the first 250 lines of your file. If no signs of free source form are |
| 237 | 1357 detected, then the file is assumed to be in fixed source form. The algorithm |
| 1358 should work in the vast majority of cases. In some cases, such as a file that | |
| 819 | 1359 begins with 250 or more full-line comments, the script may incorrectly decide |
| 237 | 1360 that the fortran code is in fixed form. If that happens, just add a |
| 7 | 1361 non-comment statement beginning anywhere in the first five columns of the |
| 1362 first twenty five lines, save (:w) and then reload (:e!) the file. | |
| 1363 | |
| 1364 Tabs in fortran files ~ | |
| 237 | 1365 Tabs are not recognized by the Fortran standards. Tabs are not a good idea in |
| 7 | 1366 fixed format fortran source code which requires fixed column boundaries. |
| 237 | 1367 Therefore, tabs are marked as errors. Nevertheless, some programmers like |
| 1368 using tabs. If your fortran files contain tabs, then you should set the | |
| 7 | 1369 variable fortran_have_tabs in your .vimrc with a command such as > |
| 1370 :let fortran_have_tabs=1 | |
| 237 | 1371 placed prior to the :syntax on command. Unfortunately, the use of tabs will |
| 7 | 1372 mean that the syntax file will not be able to detect incorrect margins. |
| 1373 | |
| 1374 Syntax folding of fortran files ~ | |
| 1375 If you wish to use foldmethod=syntax, then you must first set the variable | |
| 1376 fortran_fold with a command such as > | |
| 1377 :let fortran_fold=1 | |
| 1378 to instruct the syntax script to define fold regions for program units, that | |
| 1379 is main programs starting with a program statement, subroutines, function | |
| 237 | 1380 subprograms, block data subprograms, interface blocks, and modules. If you |
| 7 | 1381 also set the variable fortran_fold_conditionals with a command such as > |
| 1382 :let fortran_fold_conditionals=1 | |
| 1383 then fold regions will also be defined for do loops, if blocks, and select | |
| 237 | 1384 case constructs. If you also set the variable |
| 7 | 1385 fortran_fold_multilinecomments with a command such as > |
| 1386 :let fortran_fold_multilinecomments=1 | |
| 1387 then fold regions will also be defined for three or more consecutive comment | |
| 237 | 1388 lines. Note that defining fold regions can be slow for large files. |
| 7 | 1389 |
| 1390 If fortran_fold, and possibly fortran_fold_conditionals and/or | |
| 1391 fortran_fold_multilinecomments, have been set, then vim will fold your file if | |
| 237 | 1392 you set foldmethod=syntax. Comments or blank lines placed between two program |
| 7 | 1393 units are not folded because they are seen as not belonging to any program |
| 1394 unit. | |
| 1395 | |
| 1396 More precise fortran syntax ~ | |
| 1397 If you set the variable fortran_more_precise with a command such as > | |
| 1398 :let fortran_more_precise=1 | |
| 237 | 1399 then the syntax coloring will be more precise but slower. In particular, |
| 7 | 1400 statement labels used in do, goto and arithmetic if statements will be |
| 1401 recognized, as will construct names at the end of a do, if, select or forall | |
| 1402 construct. | |
| 1403 | |
| 1404 Non-default fortran dialects ~ | |
| 3281 | 1405 The syntax script supports two Fortran dialects: f08 and F. You will probably |
| 1406 find the default highlighting (f08) satisfactory. A few legacy constructs | |
| 1407 deleted or declared obsolescent in the 2008 standard are highlighted as todo | |
| 1408 items. | |
| 1409 | |
| 1410 If you use F, the advantage of setting the dialect appropriately is that | |
| 1411 other legacy features excluded from F will be highlighted as todo items and | |
| 1412 that free source form will be assumed. | |
| 1413 | |
| 1414 The dialect can be selected in various ways. If all your fortran files use | |
| 1415 the same dialect, set the global variable fortran_dialect in your .vimrc prior | |
| 1416 to your syntax on statement. The case-sensitive, permissible values of | |
| 1417 fortran_dialect are "f08" or "F". Invalid values of fortran_dialect are | |
| 1418 ignored. | |
| 1419 | |
| 1420 If the dialect depends upon the file extension, then it is most convenient to | |
| 1421 set a buffer-local variable in a ftplugin file. For more information on | |
| 1422 ftplugin files, see |ftplugin|. For example, if all your fortran files with | |
| 1423 an .f90 extension are written in the F subset, your ftplugin file should | |
| 1424 contain the code > | |
| 7 | 1425 let s:extfname = expand("%:e") |
| 1426 if s:extfname ==? "f90" | |
| 3281 | 1427 let b:fortran_dialect="F" |
| 7 | 1428 else |
| 3281 | 1429 unlet! b:fortran_dialect |
| 7 | 1430 endif |
| 1431 Note that this will work only if the "filetype plugin indent on" command | |
| 1432 precedes the "syntax on" command in your .vimrc file. | |
| 1433 | |
| 1434 Finer control is necessary if the file extension does not uniquely identify | |
| 3281 | 1435 the dialect. You can override the default dialect, on a file-by-file basis, |
| 1436 by including a comment with the directive "fortran_dialect=xx" (where xx=F or | |
| 1437 f08) in one of the first three lines in your file. For example, your older .f | |
| 1438 files may be legacy code but your newer ones may be F codes, and you would | |
| 1439 identify the latter by including in the first three lines of those files a | |
| 1440 Fortran comment of the form > | |
| 7 | 1441 ! fortran_dialect=F |
| 3281 | 1442 |
| 1443 For previous versions of the syntax, you may have set fortran_dialect to the | |
| 1444 now-obsolete values "f77", "f90", "f95", or "elf". Such settings will be | |
| 1445 silently handled as "f08". Users of "elf" may wish to experiment with "F" | |
| 1446 instead. | |
| 1447 | |
| 1448 The syntax/fortran.vim script contains embedded comments that tell you how to | |
| 1449 comment and/or uncomment some lines to (a) activate recognition of some | |
| 1450 non-standard, vendor-supplied intrinsics and (b) to prevent features deleted | |
| 1451 or declared obsolescent in the 2008 standard from being highlighted as todo | |
| 1452 items. | |
| 7 | 1453 |
| 1454 Limitations ~ | |
| 237 | 1455 Parenthesis checking does not catch too few closing parentheses. Hollerith |
| 1456 strings are not recognized. Some keywords may be highlighted incorrectly | |
| 7 | 1457 because Fortran90 has no reserved words. |
| 1458 | |
| 501 | 1459 For further information related to fortran, see |ft-fortran-indent| and |
| 1460 |ft-fortran-plugin|. | |
| 1461 | |
| 1462 | |
| 1463 FVWM CONFIGURATION FILES *fvwm.vim* *ft-fvwm-syntax* | |
| 7 | 1464 |
| 1465 In order for Vim to recognize Fvwm configuration files that do not match | |
| 1466 the patterns *fvwmrc* or *fvwm2rc* , you must put additional patterns | |
| 1467 appropriate to your system in your myfiletypes.vim file. For these | |
| 1468 patterns, you must set the variable "b:fvwm_version" to the major version | |
| 1469 number of Fvwm, and the 'filetype' option to fvwm. | |
| 1470 | |
| 1471 For example, to make Vim identify all files in /etc/X11/fvwm2/ | |
| 1472 as Fvwm2 configuration files, add the following: > | |
| 1473 | |
| 1474 :au! BufNewFile,BufRead /etc/X11/fvwm2/* let b:fvwm_version = 2 | | |
| 1475 \ set filetype=fvwm | |
| 1476 | |
| 1477 If you'd like Vim to highlight all valid color names, tell it where to | |
| 1478 find the color database (rgb.txt) on your system. Do this by setting | |
| 1479 "rgb_file" to its location. Assuming your color database is located | |
| 1480 in /usr/X11/lib/X11/, you should add the line > | |
| 1481 | |
| 1482 :let rgb_file = "/usr/X11/lib/X11/rgb.txt" | |
| 1483 | |
| 1484 to your .vimrc file. | |
| 1485 | |
| 1486 | |
| 501 | 1487 GSP *gsp.vim* *ft-gsp-syntax* |
| 7 | 1488 |
| 1489 The default coloring style for GSP pages is defined by |html.vim|, and | |
| 1490 the coloring for java code (within java tags or inline between backticks) | |
| 1491 is defined by |java.vim|. The following HTML groups defined in |html.vim| | |
| 1492 are redefined to incorporate and highlight inline java code: | |
| 1493 | |
| 1494 htmlString | |
| 1495 htmlValue | |
| 1496 htmlEndTag | |
| 1497 htmlTag | |
| 1498 htmlTagN | |
| 1499 | |
| 1500 Highlighting should look fine most of the places where you'd see inline | |
| 1501 java code, but in some special cases it may not. To add another HTML | |
| 1502 group where you will have inline java code where it does not highlight | |
| 1503 correctly, just copy the line you want from |html.vim| and add gspJava | |
| 1504 to the contains clause. | |
| 1505 | |
| 1506 The backticks for inline java are highlighted according to the htmlError | |
| 1507 group to make them easier to see. | |
| 1508 | |
| 1509 | |
| 501 | 1510 GROFF *groff.vim* *ft-groff-syntax* |
| 7 | 1511 |
| 1512 The groff syntax file is a wrapper for |nroff.vim|, see the notes | |
| 237 | 1513 under that heading for examples of use and configuration. The purpose |
| 7 | 1514 of this wrapper is to set up groff syntax extensions by setting the |
| 1515 filetype from a |modeline| or in a personal filetype definitions file | |
| 1516 (see |filetype.txt|). | |
| 1517 | |
| 1518 | |
| 501 | 1519 HASKELL *haskell.vim* *lhaskell.vim* *ft-haskell-syntax* |
| 7 | 1520 |
| 1521 The Haskell syntax files support plain Haskell code as well as literate | |
| 237 | 1522 Haskell code, the latter in both Bird style and TeX style. The Haskell |
| 7 | 1523 syntax highlighting will also highlight C preprocessor directives. |
| 1524 | |
| 1525 If you want to highlight delimiter characters (useful if you have a | |
| 1526 light-coloured background), add to your .vimrc: > | |
| 1527 :let hs_highlight_delimiters = 1 | |
| 1528 To treat True and False as keywords as opposed to ordinary identifiers, | |
| 1529 add: > | |
| 1530 :let hs_highlight_boolean = 1 | |
| 1531 To also treat the names of primitive types as keywords: > | |
| 1532 :let hs_highlight_types = 1 | |
| 1533 And to treat the names of even more relatively common types as keywords: > | |
| 1534 :let hs_highlight_more_types = 1 | |
| 1535 If you want to highlight the names of debugging functions, put in | |
| 1536 your .vimrc: > | |
| 1537 :let hs_highlight_debug = 1 | |
| 1538 | |
| 1539 The Haskell syntax highlighting also highlights C preprocessor | |
| 1540 directives, and flags lines that start with # but are not valid | |
| 237 | 1541 directives as erroneous. This interferes with Haskell's syntax for |
| 1542 operators, as they may start with #. If you want to highlight those | |
| 7 | 1543 as operators as opposed to errors, put in your .vimrc: > |
| 1544 :let hs_allow_hash_operator = 1 | |
| 1545 | |
| 1546 The syntax highlighting for literate Haskell code will try to | |
| 1547 automatically guess whether your literate Haskell code contains | |
| 1548 TeX markup or not, and correspondingly highlight TeX constructs | |
| 237 | 1549 or nothing at all. You can override this globally by putting |
| 7 | 1550 in your .vimrc > |
| 1551 :let lhs_markup = none | |
| 1552 for no highlighting at all, or > | |
| 1553 :let lhs_markup = tex | |
| 1554 to force the highlighting to always try to highlight TeX markup. | |
| 1555 For more flexibility, you may also use buffer local versions of | |
| 1556 this variable, so e.g. > | |
| 1557 :let b:lhs_markup = tex | |
| 237 | 1558 will force TeX highlighting for a particular buffer. It has to be |
| 7 | 1559 set before turning syntax highlighting on for the buffer or |
| 1560 loading a file. | |
| 1561 | |
| 1562 | |
| 501 | 1563 HTML *html.vim* *ft-html-syntax* |
| 7 | 1564 |
| 1565 The coloring scheme for tags in the HTML file works as follows. | |
| 1566 | |
| 1567 The <> of opening tags are colored differently than the </> of a closing tag. | |
| 1568 This is on purpose! For opening tags the 'Function' color is used, while for | |
| 1569 closing tags the 'Type' color is used (See syntax.vim to check how those are | |
| 1570 defined for you) | |
| 1571 | |
| 1572 Known tag names are colored the same way as statements in C. Unknown tag | |
| 1573 names are colored with the same color as the <> or </> respectively which | |
| 1574 makes it easy to spot errors | |
| 1575 | |
| 237 | 1576 Note that the same is true for argument (or attribute) names. Known attribute |
| 7 | 1577 names are colored differently than unknown ones. |
| 1578 | |
| 237 | 1579 Some HTML tags are used to change the rendering of text. The following tags |
| 7 | 1580 are recognized by the html.vim syntax coloring file and change the way normal |
| 1581 text is shown: <B> <I> <U> <EM> <STRONG> (<EM> is used as an alias for <I>, | |
| 1582 while <STRONG> as an alias for <B>), <H1> - <H6>, <HEAD>, <TITLE> and <A>, but | |
| 237 | 1583 only if used as a link (that is, it must include a href as in |
| 1224 | 1584 <A href="somefile.html">). |
| 7 | 1585 |
| 1586 If you want to change how such text is rendered, you must redefine the | |
| 1587 following syntax groups: | |
| 1588 | |
| 1589 - htmlBold | |
| 1590 - htmlBoldUnderline | |
| 1591 - htmlBoldUnderlineItalic | |
| 1592 - htmlUnderline | |
| 1593 - htmlUnderlineItalic | |
| 1594 - htmlItalic | |
| 1595 - htmlTitle for titles | |
| 1596 - htmlH1 - htmlH6 for headings | |
| 1597 | |
| 1598 To make this redefinition work you must redefine them all with the exception | |
| 1599 of the last two (htmlTitle and htmlH[1-6], which are optional) and define the | |
| 1600 following variable in your vimrc (this is due to the order in which the files | |
| 1601 are read during initialization) > | |
| 1602 :let html_my_rendering=1 | |
| 1603 | |
| 1604 If you'd like to see an example download mysyntax.vim at | |
| 1605 http://www.fleiner.com/vim/download.html | |
| 1606 | |
| 1607 You can also disable this rendering by adding the following line to your | |
| 1608 vimrc file: > | |
| 1609 :let html_no_rendering=1 | |
| 1610 | |
| 1611 HTML comments are rather special (see an HTML reference document for the | |
| 1612 details), and the syntax coloring scheme will highlight all errors. | |
| 1613 However, if you prefer to use the wrong style (starts with <!-- and | |
| 1614 ends with --!>) you can define > | |
| 1615 :let html_wrong_comments=1 | |
| 1616 | |
| 1617 JavaScript and Visual Basic embedded inside HTML documents are highlighted as | |
| 1618 'Special' with statements, comments, strings and so on colored as in standard | |
| 237 | 1619 programming languages. Note that only JavaScript and Visual Basic are currently |
| 7 | 1620 supported, no other scripting language has been added yet. |
| 1621 | |
| 1622 Embedded and inlined cascading style sheets (CSS) are highlighted too. | |
| 1623 | |
| 237 | 1624 There are several html preprocessor languages out there. html.vim has been |
| 1625 written such that it should be trivial to include it. To do so add the | |
| 7 | 1626 following two lines to the syntax coloring file for that language |
| 1627 (the example comes from the asp.vim file): | |
| 1628 | |
| 1629 runtime! syntax/html.vim | |
| 1630 syn cluster htmlPreproc add=asp | |
| 1631 | |
| 1632 Now you just need to make sure that you add all regions that contain | |
| 1633 the preprocessor language to the cluster htmlPreproc. | |
| 1634 | |
| 1635 | |
| 501 | 1636 HTML/OS (by Aestiva) *htmlos.vim* *ft-htmlos-syntax* |
| 7 | 1637 |
| 1638 The coloring scheme for HTML/OS works as follows: | |
| 1639 | |
| 1640 Functions and variable names are the same color by default, because VIM | |
| 1641 doesn't specify different colors for Functions and Identifiers. To change | |
| 1642 this (which is recommended if you want function names to be recognizable in a | |
| 1643 different color) you need to add the following line to either your ~/.vimrc: > | |
| 1644 :hi Function term=underline cterm=bold ctermfg=LightGray | |
| 1645 | |
| 1646 Of course, the ctermfg can be a different color if you choose. | |
| 1647 | |
| 1648 Another issues that HTML/OS runs into is that there is no special filetype to | |
| 1649 signify that it is a file with HTML/OS coding. You can change this by opening | |
| 1650 a file and turning on HTML/OS syntax by doing the following: > | |
| 1651 :set syntax=htmlos | |
| 1652 | |
| 1653 Lastly, it should be noted that the opening and closing characters to begin a | |
| 1654 block of HTML/OS code can either be << or [[ and >> or ]], respectively. | |
| 1655 | |
| 1656 | |
| 501 | 1657 IA64 *ia64.vim* *intel-itanium* *ft-ia64-syntax* |
| 7 | 1658 |
| 1659 Highlighting for the Intel Itanium 64 assembly language. See |asm.vim| for | |
| 1660 how to recognize this filetype. | |
| 1661 | |
| 1662 To have *.inc files be recognized as IA64, add this to your .vimrc file: > | |
| 1663 :let g:filetype_inc = "ia64" | |
| 1664 | |
| 1665 | |
| 501 | 1666 INFORM *inform.vim* *ft-inform-syntax* |
| 7 | 1667 |
| 1668 Inform highlighting includes symbols provided by the Inform Library, as | |
| 1669 most programs make extensive use of it. If do not wish Library symbols | |
| 1670 to be highlighted add this to your vim startup: > | |
| 1671 :let inform_highlight_simple=1 | |
| 1672 | |
| 1673 By default it is assumed that Inform programs are Z-machine targeted, | |
| 1674 and highlights Z-machine assembly language symbols appropriately. If | |
| 1675 you intend your program to be targeted to a Glulx/Glk environment you | |
| 1676 need to add this to your startup sequence: > | |
| 1677 :let inform_highlight_glulx=1 | |
| 1678 | |
| 1679 This will highlight Glulx opcodes instead, and also adds glk() to the | |
| 1680 set of highlighted system functions. | |
| 1681 | |
| 1682 The Inform compiler will flag certain obsolete keywords as errors when | |
| 1683 it encounters them. These keywords are normally highlighted as errors | |
| 1684 by Vim. To prevent such error highlighting, you must add this to your | |
| 1685 startup sequence: > | |
| 1686 :let inform_suppress_obsolete=1 | |
| 1687 | |
| 1688 By default, the language features highlighted conform to Compiler | |
| 1689 version 6.30 and Library version 6.11. If you are using an older | |
| 1690 Inform development environment, you may with to add this to your | |
| 1691 startup sequence: > | |
| 1692 :let inform_highlight_old=1 | |
| 1693 | |
| 829 | 1694 IDL *idl.vim* *idl-syntax* |
| 1695 | |
| 1696 IDL (Interface Definition Language) files are used to define RPC calls. In | |
| 1697 Microsoft land, this is also used for defining COM interfaces and calls. | |
| 1698 | |
| 1699 IDL's structure is simple enough to permit a full grammar based approach to | |
| 1700 rather than using a few heuristics. The result is large and somewhat | |
| 1224 | 1701 repetitive but seems to work. |
| 829 | 1702 |
| 1703 There are some Microsoft extensions to idl files that are here. Some of them | |
| 1704 are disabled by defining idl_no_ms_extensions. | |
| 1705 | |
| 1706 The more complex of the extensions are disabled by defining idl_no_extensions. | |
| 1707 | |
| 1708 Variable Effect ~ | |
| 1709 | |
| 1710 idl_no_ms_extensions Disable some of the Microsoft specific | |
| 1711 extensions | |
| 1712 idl_no_extensions Disable complex extensions | |
| 1713 idlsyntax_showerror Show IDL errors (can be rather intrusive, but | |
| 1714 quite helpful) | |
| 1715 idlsyntax_showerror_soft Use softer colours by default for errors | |
| 1716 | |
| 7 | 1717 |
| 501 | 1718 JAVA *java.vim* *ft-java-syntax* |
| 7 | 1719 |
| 1720 The java.vim syntax highlighting file offers several options: | |
| 1721 | |
| 1722 In Java 1.0.2 it was never possible to have braces inside parens, so this was | |
| 1723 flagged as an error. Since Java 1.1 this is possible (with anonymous | |
| 237 | 1724 classes), and therefore is no longer marked as an error. If you prefer the old |
| 7 | 1725 way, put the following line into your vim startup file: > |
| 1726 :let java_mark_braces_in_parens_as_errors=1 | |
| 1727 | |
| 1728 All identifiers in java.lang.* are always visible in all classes. To | |
| 1729 highlight them use: > | |
| 1730 :let java_highlight_java_lang_ids=1 | |
| 1731 | |
| 237 | 1732 You can also highlight identifiers of most standard Java packages if you |
| 7 | 1733 download the javaid.vim script at http://www.fleiner.com/vim/download.html. |
| 1734 If you prefer to only highlight identifiers of a certain package, say java.io | |
| 1735 use the following: > | |
| 1736 :let java_highlight_java_io=1 | |
| 1737 Check the javaid.vim file for a list of all the packages that are supported. | |
| 1738 | |
| 1739 Function names are not highlighted, as the way to find functions depends on | |
| 237 | 1740 how you write Java code. The syntax file knows two possible ways to highlight |
| 7 | 1741 functions: |
| 1742 | |
| 1743 If you write function declarations that are always indented by either | |
| 1744 a tab, 8 spaces or 2 spaces you may want to set > | |
| 1745 :let java_highlight_functions="indent" | |
| 1746 However, if you follow the Java guidelines about how functions and classes are | |
| 1747 supposed to be named (with respect to upper and lowercase), use > | |
| 1748 :let java_highlight_functions="style" | |
| 1749 If both options do not work for you, but you would still want function | |
| 1750 declarations to be highlighted create your own definitions by changing the | |
| 1751 definitions in java.vim or by creating your own java.vim which includes the | |
| 1752 original one and then adds the code to highlight functions. | |
| 1753 | |
| 237 | 1754 In Java 1.1 the functions System.out.println() and System.err.println() should |
| 8 | 1755 only be used for debugging. Therefore it is possible to highlight debugging |
| 237 | 1756 statements differently. To do this you must add the following definition in |
| 7 | 1757 your startup file: > |
| 1758 :let java_highlight_debug=1 | |
| 1759 The result will be that those statements are highlighted as 'Special' | |
| 237 | 1760 characters. If you prefer to have them highlighted differently you must define |
| 7 | 1761 new highlightings for the following groups.: |
| 1762 Debug, DebugSpecial, DebugString, DebugBoolean, DebugType | |
| 1763 which are used for the statement itself, special characters used in debug | |
| 237 | 1764 strings, strings, boolean constants and types (this, super) respectively. I |
| 7 | 1765 have opted to chose another background for those statements. |
| 1766 | |
| 237 | 1767 Javadoc is a program that takes special comments out of Java program files and |
| 1768 creates HTML pages. The standard configuration will highlight this HTML code | |
| 1769 similarly to HTML files (see |html.vim|). You can even add Javascript | |
| 1770 and CSS inside this code (see below). There are four differences however: | |
| 7 | 1771 1. The title (all characters up to the first '.' which is followed by |
| 1772 some white space or up to the first '@') is colored differently (to change | |
| 1773 the color change the group CommentTitle). | |
| 1774 2. The text is colored as 'Comment'. | |
| 1775 3. HTML comments are colored as 'Special' | |
| 237 | 1776 4. The special Javadoc tags (@see, @param, ...) are highlighted as specials |
| 7 | 1777 and the argument (for @see, @param, @exception) as Function. |
| 1778 To turn this feature off add the following line to your startup file: > | |
| 1779 :let java_ignore_javadoc=1 | |
| 1780 | |
| 237 | 1781 If you use the special Javadoc comment highlighting described above you |
| 1782 can also turn on special highlighting for Javascript, visual basic | |
| 1783 scripts and embedded CSS (stylesheets). This makes only sense if you | |
| 1784 actually have Javadoc comments that include either Javascript or embedded | |
| 1785 CSS. The options to use are > | |
| 7 | 1786 :let java_javascript=1 |
| 1787 :let java_css=1 | |
| 1788 :let java_vb=1 | |
| 1789 | |
| 1790 In order to highlight nested parens with different colors define colors | |
| 1791 for javaParen, javaParen1 and javaParen2, for example with > | |
| 1792 :hi link javaParen Comment | |
| 1793 or > | |
| 1794 :hi javaParen ctermfg=blue guifg=#0000ff | |
| 1795 | |
| 1796 If you notice highlighting errors while scrolling backwards, which are fixed | |
| 1797 when redrawing with CTRL-L, try setting the "java_minlines" internal variable | |
| 1798 to a larger number: > | |
| 1799 :let java_minlines = 50 | |
| 1800 This will make the syntax synchronization start 50 lines before the first | |
| 1801 displayed line. The default value is 10. The disadvantage of using a larger | |
| 1802 number is that redrawing can become slow. | |
| 1803 | |
| 1804 | |
| 501 | 1805 LACE *lace.vim* *ft-lace-syntax* |
| 7 | 1806 |
| 1807 Lace (Language for Assembly of Classes in Eiffel) is case insensitive, but the | |
| 1808 style guide lines are not. If you prefer case insensitive highlighting, just | |
| 1809 define the vim variable 'lace_case_insensitive' in your startup file: > | |
| 1810 :let lace_case_insensitive=1 | |
| 1811 | |
| 1812 | |
| 501 | 1813 LEX *lex.vim* *ft-lex-syntax* |
| 7 | 1814 |
| 1815 Lex uses brute-force synchronizing as the "^%%$" section delimiter | |
| 1816 gives no clue as to what section follows. Consequently, the value for > | |
| 1817 :syn sync minlines=300 | |
| 1818 may be changed by the user if s/he is experiencing synchronization | |
| 1819 difficulties (such as may happen with large lex files). | |
| 1820 | |
| 1821 | |
|
2412
ca3f40b0d95e
Prepare for 7.3b release. Fix src/Makefile enabling python3 by default.
Bram Moolenaar <bram@vim.org>
parents:
2410
diff
changeset
|
1822 LIFELINES *lifelines.vim* *ft-lifelines-syntax* |
|
ca3f40b0d95e
Prepare for 7.3b release. Fix src/Makefile enabling python3 by default.
Bram Moolenaar <bram@vim.org>
parents:
2410
diff
changeset
|
1823 |
|
ca3f40b0d95e
Prepare for 7.3b release. Fix src/Makefile enabling python3 by default.
Bram Moolenaar <bram@vim.org>
parents:
2410
diff
changeset
|
1824 To highlight deprecated functions as errors, add in your .vimrc: > |
|
ca3f40b0d95e
Prepare for 7.3b release. Fix src/Makefile enabling python3 by default.
Bram Moolenaar <bram@vim.org>
parents:
2410
diff
changeset
|
1825 |
|
ca3f40b0d95e
Prepare for 7.3b release. Fix src/Makefile enabling python3 by default.
Bram Moolenaar <bram@vim.org>
parents:
2410
diff
changeset
|
1826 :let g:lifelines_deprecated = 1 |
|
ca3f40b0d95e
Prepare for 7.3b release. Fix src/Makefile enabling python3 by default.
Bram Moolenaar <bram@vim.org>
parents:
2410
diff
changeset
|
1827 < |
|
ca3f40b0d95e
Prepare for 7.3b release. Fix src/Makefile enabling python3 by default.
Bram Moolenaar <bram@vim.org>
parents:
2410
diff
changeset
|
1828 |
| 555 | 1829 LISP *lisp.vim* *ft-lisp-syntax* |
| 1830 | |
| 1831 The lisp syntax highlighting provides two options: > | |
| 1832 | |
| 1833 g:lisp_instring : if it exists, then "(...)" strings are highlighted | |
| 1834 as if the contents of the string were lisp. | |
| 1835 Useful for AutoLisp. | |
| 1836 g:lisp_rainbow : if it exists and is nonzero, then differing levels | |
| 1837 of parenthesization will receive different | |
| 1838 highlighting. | |
| 1839 < | |
| 1840 The g:lisp_rainbow option provides 10 levels of individual colorization for | |
| 1841 the parentheses and backquoted parentheses. Because of the quantity of | |
| 1842 colorization levels, unlike non-rainbow highlighting, the rainbow mode | |
| 1843 specifies its highlighting using ctermfg and guifg, thereby bypassing the | |
| 1844 usual colorscheme control using standard highlighting groups. The actual | |
| 1845 highlighting used depends on the dark/bright setting (see |'bg'|). | |
| 1846 | |
| 1847 | |
| 501 | 1848 LITE *lite.vim* *ft-lite-syntax* |
| 7 | 1849 |
| 1850 There are two options for the lite syntax highlighting. | |
| 1851 | |
| 1852 If you like SQL syntax highlighting inside Strings, use this: > | |
| 1853 | |
| 1854 :let lite_sql_query = 1 | |
| 1855 | |
| 1856 For syncing, minlines defaults to 100. If you prefer another value, you can | |
| 1857 set "lite_minlines" to the value you desire. Example: > | |
| 1858 | |
| 1859 :let lite_minlines = 200 | |
| 1860 | |
| 1861 | |
| 501 | 1862 LPC *lpc.vim* *ft-lpc-syntax* |
| 7 | 1863 |
| 237 | 1864 LPC stands for a simple, memory-efficient language: Lars Pensj| C. The |
| 7 | 1865 file name of LPC is usually *.c. Recognizing these files as LPC would bother |
| 1866 users writing only C programs. If you want to use LPC syntax in Vim, you | |
| 1867 should set a variable in your .vimrc file: > | |
| 1868 | |
| 1869 :let lpc_syntax_for_c = 1 | |
| 1870 | |
| 1871 If it doesn't work properly for some particular C or LPC files, use a | |
| 1872 modeline. For a LPC file: | |
| 1873 | |
| 1874 // vim:set ft=lpc: | |
| 1875 | |
| 1876 For a C file that is recognized as LPC: | |
| 1877 | |
| 1878 // vim:set ft=c: | |
| 1879 | |
| 1880 If you don't want to set the variable, use the modeline in EVERY LPC file. | |
| 1881 | |
| 1882 There are several implementations for LPC, we intend to support most widely | |
| 237 | 1883 used ones. Here the default LPC syntax is for MudOS series, for MudOS v22 |
| 7 | 1884 and before, you should turn off the sensible modifiers, and this will also |
| 1885 asserts the new efuns after v22 to be invalid, don't set this variable when | |
| 1886 you are using the latest version of MudOS: > | |
| 1887 | |
| 1888 :let lpc_pre_v22 = 1 | |
| 1889 | |
| 1890 For LpMud 3.2 series of LPC: > | |
| 1891 | |
| 1892 :let lpc_compat_32 = 1 | |
| 1893 | |
| 1894 For LPC4 series of LPC: > | |
| 1895 | |
| 1896 :let lpc_use_lpc4_syntax = 1 | |
| 1897 | |
| 1898 For uLPC series of LPC: | |
| 1899 uLPC has been developed to Pike, so you should use Pike syntax | |
| 1900 instead, and the name of your source file should be *.pike | |
| 1901 | |
| 1902 | |
| 501 | 1903 LUA *lua.vim* *ft-lua-syntax* |
| 7 | 1904 |
| 3356 | 1905 The Lua syntax file can be used for versions 4.0, 5.0, 5.1 and 5.2 (5.2 is |
| 838 | 1906 the default). You can select one of these versions using the global variables |
| 1907 lua_version and lua_subversion. For example, to activate Lua | |
| 3356 | 1908 5.1 syntax highlighting, set the variables like this: |
| 838 | 1909 |
| 1910 :let lua_version = 5 | |
| 1911 :let lua_subversion = 1 | |
| 7 | 1912 |
| 1913 | |
| 501 | 1914 MAIL *mail.vim* *ft-mail.vim* |
| 7 | 1915 |
| 1916 Vim highlights all the standard elements of an email (headers, signatures, | |
| 237 | 1917 quoted text and URLs / email addresses). In keeping with standard conventions, |
| 7 | 1918 signatures begin in a line containing only "--" followed optionally by |
| 1919 whitespaces and end with a newline. | |
| 1920 | |
| 1921 Vim treats lines beginning with ']', '}', '|', '>' or a word followed by '>' | |
| 237 | 1922 as quoted text. However Vim highlights headers and signatures in quoted text |
| 7 | 1923 only if the text is quoted with '>' (optionally followed by one space). |
| 1924 | |
| 1925 By default mail.vim synchronises syntax to 100 lines before the first | |
| 237 | 1926 displayed line. If you have a slow machine, and generally deal with emails |
| 7 | 1927 with short headers, you can change this to a smaller value: > |
| 1928 | |
| 1929 :let mail_minlines = 30 | |
| 1930 | |
| 1931 | |
| 501 | 1932 MAKE *make.vim* *ft-make-syntax* |
| 7 | 1933 |
| 1934 In makefiles, commands are usually highlighted to make it easy for you to spot | |
| 1935 errors. However, this may be too much coloring for you. You can turn this | |
| 1936 feature off by using: > | |
| 1937 | |
| 1938 :let make_no_commands = 1 | |
| 1939 | |
| 1940 | |
| 501 | 1941 MAPLE *maple.vim* *ft-maple-syntax* |
| 7 | 1942 |
| 1943 Maple V, by Waterloo Maple Inc, supports symbolic algebra. The language | |
| 1944 supports many packages of functions which are selectively loaded by the user. | |
| 1945 The standard set of packages' functions as supplied in Maple V release 4 may be | |
| 1946 highlighted at the user's discretion. Users may place in their .vimrc file: > | |
| 1947 | |
| 1948 :let mvpkg_all= 1 | |
| 1949 | |
| 1950 to get all package functions highlighted, or users may select any subset by | |
| 1951 choosing a variable/package from the table below and setting that variable to | |
| 1952 1, also in their .vimrc file (prior to sourcing | |
| 1953 $VIMRUNTIME/syntax/syntax.vim). | |
| 1954 | |
| 1955 Table of Maple V Package Function Selectors > | |
| 1956 mv_DEtools mv_genfunc mv_networks mv_process | |
| 1957 mv_Galois mv_geometry mv_numapprox mv_simplex | |
| 1958 mv_GaussInt mv_grobner mv_numtheory mv_stats | |
| 1959 mv_LREtools mv_group mv_orthopoly mv_student | |
| 1960 mv_combinat mv_inttrans mv_padic mv_sumtools | |
| 1961 mv_combstruct mv_liesymm mv_plots mv_tensor | |
| 1962 mv_difforms mv_linalg mv_plottools mv_totorder | |
| 1963 mv_finance mv_logic mv_powseries | |
| 1964 | |
| 1965 | |
| 501 | 1966 MATHEMATICA *mma.vim* *ft-mma-syntax* *ft-mathematica-syntax* |
| 271 | 1967 |
| 1968 Empty *.m files will automatically be presumed to be Matlab files unless you | |
| 1969 have the following in your .vimrc: > | |
| 1970 | |
| 1971 let filetype_m = "mma" | |
| 1972 | |
| 1973 | |
| 501 | 1974 MOO *moo.vim* *ft-moo-syntax* |
| 7 | 1975 |
| 1976 If you use C-style comments inside expressions and find it mangles your | |
| 1977 highlighting, you may want to use extended (slow!) matches for C-style | |
| 1978 comments: > | |
| 1979 | |
| 1980 :let moo_extended_cstyle_comments = 1 | |
| 1981 | |
| 1982 To disable highlighting of pronoun substitution patterns inside strings: > | |
| 1983 | |
| 1984 :let moo_no_pronoun_sub = 1 | |
| 1985 | |
| 1986 To disable highlighting of the regular expression operator '%|', and matching | |
| 1987 '%(' and '%)' inside strings: > | |
| 1988 | |
| 1989 :let moo_no_regexp = 1 | |
| 1990 | |
| 1991 Unmatched double quotes can be recognized and highlighted as errors: > | |
| 1992 | |
| 1993 :let moo_unmatched_quotes = 1 | |
| 1994 | |
| 1995 To highlight builtin properties (.name, .location, .programmer etc.): > | |
| 1996 | |
| 1997 :let moo_builtin_properties = 1 | |
| 1998 | |
| 237 | 1999 Unknown builtin functions can be recognized and highlighted as errors. If you |
| 7 | 2000 use this option, add your own extensions to the mooKnownBuiltinFunction group. |
| 2001 To enable this option: > | |
| 2002 | |
| 2003 :let moo_unknown_builtin_functions = 1 | |
| 2004 | |
| 2005 An example of adding sprintf() to the list of known builtin functions: > | |
| 2006 | |
| 2007 :syn keyword mooKnownBuiltinFunction sprintf contained | |
| 2008 | |
| 2009 | |
| 501 | 2010 MSQL *msql.vim* *ft-msql-syntax* |
| 7 | 2011 |
| 2012 There are two options for the msql syntax highlighting. | |
| 2013 | |
| 2014 If you like SQL syntax highlighting inside Strings, use this: > | |
| 2015 | |
| 2016 :let msql_sql_query = 1 | |
| 2017 | |
| 2018 For syncing, minlines defaults to 100. If you prefer another value, you can | |
| 2019 set "msql_minlines" to the value you desire. Example: > | |
| 2020 | |
| 2021 :let msql_minlines = 200 | |
| 2022 | |
| 2023 | |
| 501 | 2024 NCF *ncf.vim* *ft-ncf-syntax* |
| 7 | 2025 |
| 2026 There is one option for NCF syntax highlighting. | |
| 2027 | |
| 2028 If you want to have unrecognized (by ncf.vim) statements highlighted as | |
| 2029 errors, use this: > | |
| 2030 | |
| 2031 :let ncf_highlight_unknowns = 1 | |
| 2032 | |
| 2033 If you don't want to highlight these errors, leave it unset. | |
| 2034 | |
| 2035 | |
| 501 | 2036 NROFF *nroff.vim* *ft-nroff-syntax* |
| 7 | 2037 |
| 2038 The nroff syntax file works with AT&T n/troff out of the box. You need to | |
| 2039 activate the GNU groff extra features included in the syntax file before you | |
| 2040 can use them. | |
| 2041 | |
| 2042 For example, Linux and BSD distributions use groff as their default text | |
| 237 | 2043 processing package. In order to activate the extra syntax highlighting |
| 7 | 2044 features for groff, add the following option to your start-up files: > |
| 2045 | |
| 2046 :let b:nroff_is_groff = 1 | |
| 2047 | |
| 2048 Groff is different from the old AT&T n/troff that you may still find in | |
| 2049 Solaris. Groff macro and request names can be longer than 2 characters and | |
| 2050 there are extensions to the language primitives. For example, in AT&T troff | |
| 237 | 2051 you access the year as a 2-digit number with the request \(yr. In groff you |
| 7 | 2052 can use the same request, recognized for compatibility, or you can use groff's |
| 2053 native syntax, \[yr]. Furthermore, you can use a 4-digit year directly: | |
| 2054 \[year]. Macro requests can be longer than 2 characters, for example, GNU mm | |
| 2055 accepts the requests ".VERBON" and ".VERBOFF" for creating verbatim | |
| 2056 environments. | |
| 2057 | |
| 2058 In order to obtain the best formatted output g/troff can give you, you should | |
| 2059 follow a few simple rules about spacing and punctuation. | |
| 2060 | |
| 2061 1. Do not leave empty spaces at the end of lines. | |
| 2062 | |
| 2063 2. Leave one space and one space only after an end-of-sentence period, | |
| 2064 exclamation mark, etc. | |
| 2065 | |
| 2066 3. For reasons stated below, it is best to follow all period marks with a | |
| 2067 carriage return. | |
| 2068 | |
| 2069 The reason behind these unusual tips is that g/n/troff have a line breaking | |
| 2070 algorithm that can be easily upset if you don't follow the rules given above. | |
| 2071 | |
| 2072 Unlike TeX, troff fills text line-by-line, not paragraph-by-paragraph and, | |
| 2073 furthermore, it does not have a concept of glue or stretch, all horizontal and | |
| 2074 vertical space input will be output as is. | |
| 2075 | |
| 2076 Therefore, you should be careful about not using more space between sentences | |
| 2077 than you intend to have in your final document. For this reason, the common | |
| 2078 practice is to insert a carriage return immediately after all punctuation | |
| 237 | 2079 marks. If you want to have "even" text in your final processed output, you |
| 4264 | 2080 need to maintain regular spacing in the input text. To mark both trailing |
| 7 | 2081 spaces and two or more spaces after a punctuation as an error, use: > |
| 2082 | |
| 2083 :let nroff_space_errors = 1 | |
| 2084 | |
| 2085 Another technique to detect extra spacing and other errors that will interfere | |
| 2086 with the correct typesetting of your file, is to define an eye-catching | |
| 2087 highlighting definition for the syntax groups "nroffDefinition" and | |
| 237 | 2088 "nroffDefSpecial" in your configuration files. For example: > |
| 7 | 2089 |
| 2090 hi def nroffDefinition term=italic cterm=italic gui=reverse | |
| 2091 hi def nroffDefSpecial term=italic,bold cterm=italic,bold | |
| 2092 \ gui=reverse,bold | |
| 2093 | |
| 2094 If you want to navigate preprocessor entries in your source file as easily as | |
| 2095 with section markers, you can activate the following option in your .vimrc | |
| 2096 file: > | |
| 2097 | |
| 2098 let b:preprocs_as_sections = 1 | |
| 2099 | |
| 9 | 2100 As well, the syntax file adds an extra paragraph marker for the extended |
| 7 | 2101 paragraph macro (.XP) in the ms package. |
| 2102 | |
| 2103 Finally, there is a |groff.vim| syntax file that can be used for enabling | |
| 2104 groff syntax highlighting either on a file basis or globally by default. | |
| 2105 | |
| 2106 | |
| 501 | 2107 OCAML *ocaml.vim* *ft-ocaml-syntax* |
| 7 | 2108 |
| 2109 The OCaml syntax file handles files having the following prefixes: .ml, | |
| 2110 .mli, .mll and .mly. By setting the following variable > | |
| 2111 | |
| 2112 :let ocaml_revised = 1 | |
| 2113 | |
| 2114 you can switch from standard OCaml-syntax to revised syntax as supported | |
| 2115 by the camlp4 preprocessor. Setting the variable > | |
| 2116 | |
| 2117 :let ocaml_noend_error = 1 | |
| 2118 | |
| 2119 prevents highlighting of "end" as error, which is useful when sources | |
| 2120 contain very long structures that Vim does not synchronize anymore. | |
| 2121 | |
| 2122 | |
| 501 | 2123 PAPP *papp.vim* *ft-papp-syntax* |
| 7 | 2124 |
| 2125 The PApp syntax file handles .papp files and, to a lesser extend, .pxml | |
| 2126 and .pxsl files which are all a mixture of perl/xml/html/other using xml | |
| 237 | 2127 as the top-level file format. By default everything inside phtml or pxml |
| 2128 sections is treated as a string with embedded preprocessor commands. If | |
| 7 | 2129 you set the variable: > |
| 2130 | |
| 2131 :let papp_include_html=1 | |
| 2132 | |
| 2133 in your startup file it will try to syntax-hilight html code inside phtml | |
| 2134 sections, but this is relatively slow and much too colourful to be able to | |
| 237 | 2135 edit sensibly. ;) |
| 7 | 2136 |
| 2137 The newest version of the papp.vim syntax file can usually be found at | |
| 2138 http://papp.plan9.de. | |
| 2139 | |
| 2140 | |
| 501 | 2141 PASCAL *pascal.vim* *ft-pascal-syntax* |
| 7 | 2142 |
| 2143 Files matching "*.p" could be Progress or Pascal. If the automatic detection | |
| 2144 doesn't work for you, or you don't edit Progress at all, use this in your | |
| 2145 startup vimrc: > | |
| 2146 | |
| 2147 :let filetype_p = "pascal" | |
| 2148 | |
| 2149 The Pascal syntax file has been extended to take into account some extensions | |
| 2150 provided by Turbo Pascal, Free Pascal Compiler and GNU Pascal Compiler. | |
| 237 | 2151 Delphi keywords are also supported. By default, Turbo Pascal 7.0 features are |
| 7 | 2152 enabled. If you prefer to stick with the standard Pascal keywords, add the |
| 2153 following line to your startup file: > | |
| 2154 | |
| 2155 :let pascal_traditional=1 | |
| 2156 | |
| 2157 To switch on Delphi specific constructions (such as one-line comments, | |
| 2158 keywords, etc): > | |
| 2159 | |
| 2160 :let pascal_delphi=1 | |
| 2161 | |
| 2162 | |
| 2163 The option pascal_symbol_operator controls whether symbol operators such as +, | |
| 2164 *, .., etc. are displayed using the Operator color or not. To colorize symbol | |
| 2165 operators, add the following line to your startup file: > | |
| 2166 | |
| 2167 :let pascal_symbol_operator=1 | |
| 2168 | |
| 2169 Some functions are highlighted by default. To switch it off: > | |
| 2170 | |
| 2171 :let pascal_no_functions=1 | |
| 2172 | |
|
2283
7e1bd501306d
Mainly documentation updates.
Bram Moolenaar <bram@vim.org>
parents:
2269
diff
changeset
|
2173 Furthermore, there are specific variables for some compilers. Besides |
| 7 | 2174 pascal_delphi, there are pascal_gpc and pascal_fpc. Default extensions try to |
| 2175 match Turbo Pascal. > | |
| 2176 | |
| 2177 :let pascal_gpc=1 | |
| 2178 | |
| 2179 or > | |
| 2180 | |
| 2181 :let pascal_fpc=1 | |
| 2182 | |
| 2183 To ensure that strings are defined on a single line, you can define the | |
| 2184 pascal_one_line_string variable. > | |
| 2185 | |
| 2186 :let pascal_one_line_string=1 | |
| 2187 | |
| 2188 If you dislike <Tab> chars, you can set the pascal_no_tabs variable. Tabs | |
| 2189 will be highlighted as Error. > | |
| 2190 | |
| 2191 :let pascal_no_tabs=1 | |
| 2192 | |
| 2193 | |
| 2194 | |
| 501 | 2195 PERL *perl.vim* *ft-perl-syntax* |
| 7 | 2196 |
| 2197 There are a number of possible options to the perl syntax highlighting. | |
| 2198 | |
| 2199 If you use POD files or POD segments, you might: > | |
| 2200 | |
| 2201 :let perl_include_pod = 1 | |
| 2202 | |
| 22 | 2203 The reduce the complexity of parsing (and increase performance) you can switch |
| 2204 off two elements in the parsing of variable names and contents. > | |
| 2205 | |
| 2206 To handle package references in variable and function names not differently | |
| 2207 from the rest of the name (like 'PkgName::' in '$PkgName::VarName'): > | |
| 2208 | |
| 2209 :let perl_no_scope_in_variables = 1 | |
| 2210 | |
| 2211 (In Vim 6.x it was the other way around: "perl_want_scope_in_variables" | |
| 2212 enabled it.) | |
| 2213 | |
| 2214 If you do not want complex things like '@{${"foo"}}' to be parsed: > | |
| 2215 | |
| 2216 :let perl_no_extended_vars = 1 | |
| 2217 | |
| 26 | 2218 (In Vim 6.x it was the other way around: "perl_extended_vars" enabled it.) |
| 7 | 2219 |
| 237 | 2220 The coloring strings can be changed. By default strings and qq friends will be |
| 2221 highlighted like the first line. If you set the variable | |
| 7 | 2222 perl_string_as_statement, it will be highlighted as in the second line. |
| 2223 | |
| 2224 "hello world!"; qq|hello world|; | |
| 2225 ^^^^^^^^^^^^^^NN^^^^^^^^^^^^^^^N (unlet perl_string_as_statement) | |
| 2226 S^^^^^^^^^^^^SNNSSS^^^^^^^^^^^SN (let perl_string_as_statement) | |
| 2227 | |
| 2228 (^ = perlString, S = perlStatement, N = None at all) | |
| 2229 | |
| 237 | 2230 The syncing has 3 options. The first two switch off some triggering of |
| 7 | 2231 synchronization and should only be needed in case it fails to work properly. |
| 2232 If while scrolling all of a sudden the whole screen changes color completely | |
| 237 | 2233 then you should try and switch off one of those. Let me know if you can figure |
| 7 | 2234 out the line that causes the mistake. |
| 2235 | |
| 2236 One triggers on "^\s*sub\s*" and the other on "^[$@%]" more or less. > | |
| 2237 | |
| 2238 :let perl_no_sync_on_sub | |
| 2239 :let perl_no_sync_on_global_var | |
| 2240 | |
| 2241 Below you can set the maximum distance VIM should look for starting points for | |
| 2242 its attempts in syntax highlighting. > | |
| 2243 | |
| 2244 :let perl_sync_dist = 100 | |
| 2245 | |
| 2246 If you want to use folding with perl, set perl_fold: > | |
| 2247 | |
| 22 | 2248 :let perl_fold = 1 |
| 2249 | |
| 2250 If you want to fold blocks in if statements, etc. as well set the following: > | |
| 2251 | |
| 2252 :let perl_fold_blocks = 1 | |
| 7 | 2253 |
| 632 | 2254 To avoid folding packages or subs when perl_fold is let, let the appropriate |
| 2255 variable(s): > | |
| 2256 | |
| 856 | 2257 :unlet perl_nofold_packages |
| 2258 :unlet perl_nofold_subs | |
| 632 | 2259 |
| 2260 | |
| 7 | 2261 |
| 501 | 2262 PHP3 and PHP4 *php.vim* *php3.vim* *ft-php-syntax* *ft-php3-syntax* |
| 7 | 2263 |
| 2264 [note: previously this was called "php3", but since it now also supports php4 | |
| 2265 it has been renamed to "php"] | |
| 2266 | |
| 2267 There are the following options for the php syntax highlighting. | |
| 2268 | |
| 2269 If you like SQL syntax highlighting inside Strings: > | |
| 2270 | |
| 2271 let php_sql_query = 1 | |
| 2272 | |
| 2273 For highlighting the Baselib methods: > | |
| 2274 | |
| 2275 let php_baselib = 1 | |
| 2276 | |
| 2277 Enable HTML syntax highlighting inside strings: > | |
| 2278 | |
| 2279 let php_htmlInStrings = 1 | |
| 2280 | |
| 2281 Using the old colorstyle: > | |
| 2282 | |
| 2283 let php_oldStyle = 1 | |
| 2284 | |
| 2285 Enable highlighting ASP-style short tags: > | |
| 2286 | |
| 2287 let php_asp_tags = 1 | |
| 2288 | |
| 2289 Disable short tags: > | |
| 2290 | |
| 2291 let php_noShortTags = 1 | |
| 2292 | |
| 2293 For highlighting parent error ] or ): > | |
| 2294 | |
| 2295 let php_parent_error_close = 1 | |
| 2296 | |
|
4681
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4437
diff
changeset
|
2297 For skipping a php end tag, if there exists an open ( or [ without a closing |
| 7 | 2298 one: > |
| 2299 | |
| 2300 let php_parent_error_open = 1 | |
| 2301 | |
| 2302 Enable folding for classes and functions: > | |
| 2303 | |
| 2304 let php_folding = 1 | |
| 2305 | |
| 2306 Selecting syncing method: > | |
| 2307 | |
| 2308 let php_sync_method = x | |
| 2309 | |
| 2310 x = -1 to sync by search (default), | |
| 2311 x > 0 to sync at least x lines backwards, | |
| 2312 x = 0 to sync from start. | |
| 2313 | |
| 2314 | |
| 816 | 2315 PLAINTEX *plaintex.vim* *ft-plaintex-syntax* |
| 2316 | |
| 2317 TeX is a typesetting language, and plaintex is the file type for the "plain" | |
| 2318 variant of TeX. If you never want your *.tex files recognized as plain TeX, | |
| 856 | 2319 see |ft-tex-plugin|. |
| 816 | 2320 |
| 2321 This syntax file has the option > | |
| 2322 | |
| 2323 let g:plaintex_delimiters = 1 | |
| 2324 | |
| 2325 if you want to highlight brackets "[]" and braces "{}". | |
| 2326 | |
| 2327 | |
| 501 | 2328 PPWIZARD *ppwiz.vim* *ft-ppwiz-syntax* |
| 7 | 2329 |
| 2330 PPWizard is a preprocessor for HTML and OS/2 INF files | |
| 2331 | |
| 2332 This syntax file has the options: | |
| 2333 | |
| 2334 - ppwiz_highlight_defs : determines highlighting mode for PPWizard's | |
| 237 | 2335 definitions. Possible values are |
| 7 | 2336 |
| 2337 ppwiz_highlight_defs = 1 : PPWizard #define statements retain the | |
| 237 | 2338 colors of their contents (e.g. PPWizard macros and variables) |
| 7 | 2339 |
| 2340 ppwiz_highlight_defs = 2 : preprocessor #define and #evaluate | |
| 2341 statements are shown in a single color with the exception of line | |
| 2342 continuation symbols | |
| 2343 | |
| 2344 The default setting for ppwiz_highlight_defs is 1. | |
| 2345 | |
| 2346 - ppwiz_with_html : If the value is 1 (the default), highlight literal | |
| 2347 HTML code; if 0, treat HTML code like ordinary text. | |
| 2348 | |
| 2349 | |
| 501 | 2350 PHTML *phtml.vim* *ft-phtml-syntax* |
| 7 | 2351 |
| 2352 There are two options for the phtml syntax highlighting. | |
| 2353 | |
| 2354 If you like SQL syntax highlighting inside Strings, use this: > | |
| 2355 | |
| 2356 :let phtml_sql_query = 1 | |
| 2357 | |
| 2358 For syncing, minlines defaults to 100. If you prefer another value, you can | |
| 2359 set "phtml_minlines" to the value you desire. Example: > | |
| 2360 | |
| 2361 :let phtml_minlines = 200 | |
| 2362 | |
| 2363 | |
| 501 | 2364 POSTSCRIPT *postscr.vim* *ft-postscr-syntax* |
| 7 | 2365 |
| 2366 There are several options when it comes to highlighting PostScript. | |
| 2367 | |
| 2368 First which version of the PostScript language to highlight. There are | |
| 2369 currently three defined language versions, or levels. Level 1 is the original | |
| 2370 and base version, and includes all extensions prior to the release of level 2. | |
| 2371 Level 2 is the most common version around, and includes its own set of | |
| 2372 extensions prior to the release of level 3. Level 3 is currently the highest | |
| 2373 level supported. You select which level of the PostScript language you want | |
| 2374 highlighted by defining the postscr_level variable as follows: > | |
| 2375 | |
| 2376 :let postscr_level=2 | |
| 2377 | |
| 2378 If this variable is not defined it defaults to 2 (level 2) since this is | |
| 2379 the most prevalent version currently. | |
| 2380 | |
| 2381 Note, not all PS interpreters will support all language features for a | |
| 2382 particular language level. In particular the %!PS-Adobe-3.0 at the start of | |
| 2383 PS files does NOT mean the PostScript present is level 3 PostScript! | |
| 2384 | |
| 2385 If you are working with Display PostScript, you can include highlighting of | |
| 2386 Display PS language features by defining the postscr_display variable as | |
| 2387 follows: > | |
| 2388 | |
| 2389 :let postscr_display=1 | |
| 2390 | |
| 2391 If you are working with Ghostscript, you can include highlighting of | |
| 2392 Ghostscript specific language features by defining the variable | |
| 2393 postscr_ghostscript as follows: > | |
| 2394 | |
| 2395 :let postscr_ghostscript=1 | |
| 2396 | |
| 2397 PostScript is a large language, with many predefined elements. While it | |
| 2398 useful to have all these elements highlighted, on slower machines this can | |
| 2399 cause Vim to slow down. In an attempt to be machine friendly font names and | |
| 2400 character encodings are not highlighted by default. Unless you are working | |
| 2401 explicitly with either of these this should be ok. If you want them to be | |
| 2402 highlighted you should set one or both of the following variables: > | |
| 2403 | |
| 2404 :let postscr_fonts=1 | |
| 2405 :let postscr_encodings=1 | |
| 2406 | |
| 2407 There is a stylistic option to the highlighting of and, or, and not. In | |
| 2408 PostScript the function of these operators depends on the types of their | |
| 2409 operands - if the operands are booleans then they are the logical operators, | |
| 2410 if they are integers then they are binary operators. As binary and logical | |
| 2411 operators can be highlighted differently they have to be highlighted one way | |
| 2412 or the other. By default they are treated as logical operators. They can be | |
| 2413 highlighted as binary operators by defining the variable | |
| 2414 postscr_andornot_binary as follows: > | |
| 2415 | |
| 2416 :let postscr_andornot_binary=1 | |
| 2417 < | |
| 2418 | |
| 501 | 2419 *ptcap.vim* *ft-printcap-syntax* |
| 2420 PRINTCAP + TERMCAP *ft-ptcap-syntax* *ft-termcap-syntax* | |
| 7 | 2421 |
| 2422 This syntax file applies to the printcap and termcap databases. | |
| 2423 | |
| 2424 In order for Vim to recognize printcap/termcap files that do not match | |
| 2425 the patterns *printcap*, or *termcap*, you must put additional patterns | |
| 2426 appropriate to your system in your |myfiletypefile| file. For these | |
| 2427 patterns, you must set the variable "b:ptcap_type" to either "print" or | |
| 2428 "term", and then the 'filetype' option to ptcap. | |
| 2429 | |
| 2430 For example, to make Vim identify all files in /etc/termcaps/ as termcap | |
| 2431 files, add the following: > | |
| 2432 | |
| 2433 :au BufNewFile,BufRead /etc/termcaps/* let b:ptcap_type = "term" | | |
| 2434 \ set filetype=ptcap | |
| 2435 | |
| 2436 If you notice highlighting errors while scrolling backwards, which | |
| 2437 are fixed when redrawing with CTRL-L, try setting the "ptcap_minlines" | |
| 2438 internal variable to a larger number: > | |
| 2439 | |
| 2440 :let ptcap_minlines = 50 | |
| 2441 | |
| 2442 (The default is 20 lines.) | |
| 2443 | |
| 2444 | |
| 501 | 2445 PROGRESS *progress.vim* *ft-progress-syntax* |
| 7 | 2446 |
| 2447 Files matching "*.w" could be Progress or cweb. If the automatic detection | |
| 2448 doesn't work for you, or you don't edit cweb at all, use this in your | |
| 2449 startup vimrc: > | |
| 2450 :let filetype_w = "progress" | |
| 2451 The same happens for "*.i", which could be assembly, and "*.p", which could be | |
| 2452 Pascal. Use this if you don't use assembly and Pascal: > | |
| 2453 :let filetype_i = "progress" | |
| 2454 :let filetype_p = "progress" | |
| 2455 | |
| 2456 | |
| 501 | 2457 PYTHON *python.vim* *ft-python-syntax* |
| 7 | 2458 |
| 4186 | 2459 There are six options to control Python syntax highlighting. |
| 7 | 2460 |
| 2461 For highlighted numbers: > | |
| 4186 | 2462 :let python_no_number_highlight = 1 |
| 7 | 2463 |
| 2464 For highlighted builtin functions: > | |
| 4186 | 2465 :let python_no_builtin_highlight = 1 |
| 7 | 2466 |
| 2467 For highlighted standard exceptions: > | |
| 4186 | 2468 :let python_no_exception_highlight = 1 |
| 2469 | |
| 2470 For highlighted doctests and code inside: > | |
| 2471 :let python_no_doctest_highlight = 1 | |
| 2472 or > | |
| 2473 :let python_no_doctest_code_highlight = 1 | |
| 2474 (first option implies second one). | |
| 7 | 2475 |
| 2596 | 2476 For highlighted trailing whitespace and mix of spaces and tabs: > |
| 4186 | 2477 :let python_space_error_highlight = 1 |
| 7 | 2478 |
| 2479 If you want all possible Python highlighting (the same as setting the | |
| 4186 | 2480 preceding last option and unsetting all other ones): > |
| 7 | 2481 :let python_highlight_all = 1 |
| 2482 | |
| 4186 | 2483 Note: only existence of these options matter, not their value. You can replace |
| 2484 1 above with anything. | |
| 2485 | |
| 7 | 2486 |
| 501 | 2487 QUAKE *quake.vim* *ft-quake-syntax* |
| 7 | 2488 |
| 2489 The Quake syntax definition should work for most any FPS (First Person | |
| 237 | 2490 Shooter) based on one of the Quake engines. However, the command names vary |
| 7 | 2491 a bit between the three games (Quake, Quake 2, and Quake 3 Arena) so the |
| 2492 syntax definition checks for the existence of three global variables to allow | |
| 237 | 2493 users to specify what commands are legal in their files. The three variables |
| 7 | 2494 can be set for the following effects: |
| 2495 | |
| 2496 set to highlight commands only available in Quake: > | |
| 2497 :let quake_is_quake1 = 1 | |
| 2498 | |
| 2499 set to highlight commands only available in Quake 2: > | |
| 2500 :let quake_is_quake2 = 1 | |
| 2501 | |
| 2502 set to highlight commands only available in Quake 3 Arena: > | |
| 2503 :let quake_is_quake3 = 1 | |
| 2504 | |
| 2505 Any combination of these three variables is legal, but might highlight more | |
| 2506 commands than are actually available to you by the game. | |
| 2507 | |
| 2508 | |
| 501 | 2509 READLINE *readline.vim* *ft-readline-syntax* |
| 7 | 2510 |
| 2511 The readline library is primarily used by the BASH shell, which adds quite a | |
| 237 | 2512 few commands and options to the ones already available. To highlight these |
| 7 | 2513 items as well you can add the following to your |vimrc| or just type it in the |
| 2514 command line before loading a file with the readline syntax: > | |
| 2515 let readline_has_bash = 1 | |
| 2516 | |
| 2517 This will add highlighting for the commands that BASH (version 2.05a and | |
| 2518 later, and part earlier) adds. | |
| 2519 | |
| 2520 | |
| 3920 | 2521 RESTRUCTURED TEXT *rst.vim* *ft-rst-syntax* |
| 2522 | |
| 2523 You may set what syntax definitions should be used for code blocks via | |
| 2524 let rst_syntax_code_list = ['vim', 'lisp', ...] | |
| 2525 | |
| 2526 | |
| 501 | 2527 REXX *rexx.vim* *ft-rexx-syntax* |
| 7 | 2528 |
| 2529 If you notice highlighting errors while scrolling backwards, which are fixed | |
| 2530 when redrawing with CTRL-L, try setting the "rexx_minlines" internal variable | |
| 2531 to a larger number: > | |
| 2532 :let rexx_minlines = 50 | |
| 2533 This will make the syntax synchronization start 50 lines before the first | |
| 2534 displayed line. The default value is 10. The disadvantage of using a larger | |
| 2535 number is that redrawing can become slow. | |
| 2536 | |
| 2965 | 2537 Vim tries to guess what type a ".r" file is. If it can't be detected (from |
| 2538 comment lines), the default is "r". To make the default rexx add this line to | |
| 2539 your .vimrc: *g:filetype_r* | |
| 2540 > | |
| 2541 :let g:filetype_r = "r" | |
| 2542 | |
| 7 | 2543 |
| 501 | 2544 RUBY *ruby.vim* *ft-ruby-syntax* |
| 7 | 2545 |
| 572 | 2546 There are a number of options to the Ruby syntax highlighting. |
| 7 | 2547 |
| 2548 By default, the "end" keyword is colorized according to the opening statement | |
| 572 | 2549 of the block it closes. While useful, this feature can be expensive; if you |
| 7 | 2550 experience slow redrawing (or you are on a terminal with poor color support) |
| 2551 you may want to turn it off by defining the "ruby_no_expensive" variable: > | |
| 572 | 2552 |
| 7 | 2553 :let ruby_no_expensive = 1 |
| 1224 | 2554 < |
| 7 | 2555 In this case the same color will be used for all control keywords. |
| 2556 | |
| 2557 If you do want this feature enabled, but notice highlighting errors while | |
| 2558 scrolling backwards, which are fixed when redrawing with CTRL-L, try setting | |
| 2559 the "ruby_minlines" variable to a value larger than 50: > | |
| 572 | 2560 |
| 7 | 2561 :let ruby_minlines = 100 |
| 1224 | 2562 < |
| 7 | 2563 Ideally, this value should be a number of lines large enough to embrace your |
| 2564 largest class or module. | |
| 2565 | |
| 1224 | 2566 Highlighting of special identifiers can be disabled by removing the |
| 2567 rubyIdentifier highlighting: > | |
| 2568 | |
| 2569 :hi link rubyIdentifier NONE | |
| 2570 < | |
| 7 | 2571 This will prevent highlighting of special identifiers like "ConstantName", |
| 572 | 2572 "$global_var", "@@class_var", "@instance_var", "| block_param |", and |
| 2573 ":symbol". | |
| 2574 | |
| 2575 Significant methods of Kernel, Module and Object are highlighted by default. | |
| 2576 This can be disabled by defining "ruby_no_special_methods": > | |
| 2577 | |
| 2578 :let ruby_no_special_methods = 1 | |
| 1224 | 2579 < |
| 572 | 2580 This will prevent highlighting of important methods such as "require", "attr", |
| 2581 "private", "raise" and "proc". | |
| 2582 | |
| 1224 | 2583 Ruby operators can be highlighted. This is enabled by defining |
| 2584 "ruby_operators": > | |
| 2585 | |
| 2586 :let ruby_operators = 1 | |
| 2587 < | |
| 572 | 2588 Whitespace errors can be highlighted by defining "ruby_space_errors": > |
| 2589 | |
| 2590 :let ruby_space_errors = 1 | |
| 1224 | 2591 < |
| 572 | 2592 This will highlight trailing whitespace and tabs preceded by a space character |
| 2593 as errors. This can be refined by defining "ruby_no_trail_space_error" and | |
| 2594 "ruby_no_tab_space_error" which will ignore trailing whitespace and tabs after | |
| 2595 spaces respectively. | |
| 2596 | |
| 2597 Folding can be enabled by defining "ruby_fold": > | |
| 2598 | |
| 2599 :let ruby_fold = 1 | |
| 1224 | 2600 < |
| 572 | 2601 This will set the 'foldmethod' option to "syntax" and allow folding of |
| 2602 classes, modules, methods, code blocks, heredocs and comments. | |
| 1125 | 2603 |
| 1224 | 2604 Folding of multiline comments can be disabled by defining |
| 2605 "ruby_no_comment_fold": > | |
| 2606 | |
| 2607 :let ruby_no_comment_fold = 1 | |
| 2608 < | |
| 1125 | 2609 |
| 501 | 2610 SCHEME *scheme.vim* *ft-scheme-syntax* |
| 17 | 2611 |
| 2612 By default only R5RS keywords are highlighted and properly indented. | |
| 2613 | |
| 2614 MzScheme-specific stuff will be used if b:is_mzscheme or g:is_mzscheme | |
| 2615 variables are defined. | |
| 856 | 2616 |
| 36 | 2617 Also scheme.vim supports keywords of the Chicken Scheme->C compiler. Define |
| 2618 b:is_chicken or g:is_chicken, if you need them. | |
| 17 | 2619 |
| 2620 | |
| 501 | 2621 SDL *sdl.vim* *ft-sdl-syntax* |
| 7 | 2622 |
| 2623 The SDL highlighting probably misses a few keywords, but SDL has so many | |
| 2624 of them it's almost impossibly to cope. | |
| 2625 | |
| 2626 The new standard, SDL-2000, specifies that all identifiers are | |
| 2627 case-sensitive (which was not so before), and that all keywords can be | |
| 237 | 2628 used either completely lowercase or completely uppercase. To have the |
| 7 | 2629 highlighting reflect this, you can set the following variable: > |
| 2630 :let sdl_2000=1 | |
| 2631 | |
| 237 | 2632 This also sets many new keywords. If you want to disable the old |
| 7 | 2633 keywords, which is probably a good idea, use: > |
| 2634 :let SDL_no_96=1 | |
| 2635 | |
| 2636 | |
| 2637 The indentation is probably also incomplete, but right now I am very | |
| 2638 satisfied with it for my own projects. | |
| 2639 | |
| 2640 | |
| 501 | 2641 SED *sed.vim* *ft-sed-syntax* |
| 7 | 2642 |
| 2643 To make tabs stand out from regular blanks (accomplished by using Todo | |
| 2644 highlighting on the tabs), define "highlight_sedtabs" by putting > | |
| 2645 | |
| 2646 :let highlight_sedtabs = 1 | |
| 2647 | |
| 2648 in the vimrc file. (This special highlighting only applies for tabs | |
| 2649 inside search patterns, replacement texts, addresses or text included | |
| 2650 by an Append/Change/Insert command.) If you enable this option, it is | |
| 2651 also a good idea to set the tab width to one character; by doing that, | |
| 2652 you can easily count the number of tabs in a string. | |
| 2653 | |
| 2654 Bugs: | |
| 2655 | |
| 2656 The transform command (y) is treated exactly like the substitute | |
| 2657 command. This means that, as far as this syntax file is concerned, | |
| 2658 transform accepts the same flags as substitute, which is wrong. | |
| 2659 (Transform accepts no flags.) I tolerate this bug because the | |
| 2660 involved commands need very complex treatment (95 patterns, one for | |
| 2661 each plausible pattern delimiter). | |
| 2662 | |
| 2663 | |
| 501 | 2664 SGML *sgml.vim* *ft-sgml-syntax* |
| 7 | 2665 |
| 2666 The coloring scheme for tags in the SGML file works as follows. | |
| 2667 | |
| 2668 The <> of opening tags are colored differently than the </> of a closing tag. | |
| 2669 This is on purpose! For opening tags the 'Function' color is used, while for | |
| 2670 closing tags the 'Type' color is used (See syntax.vim to check how those are | |
| 2671 defined for you) | |
| 2672 | |
| 2673 Known tag names are colored the same way as statements in C. Unknown tag | |
| 2674 names are not colored which makes it easy to spot errors. | |
| 2675 | |
| 237 | 2676 Note that the same is true for argument (or attribute) names. Known attribute |
| 7 | 2677 names are colored differently than unknown ones. |
| 2678 | |
| 237 | 2679 Some SGML tags are used to change the rendering of text. The following tags |
| 7 | 2680 are recognized by the sgml.vim syntax coloring file and change the way normal |
| 2681 text is shown: <varname> <emphasis> <command> <function> <literal> | |
| 2682 <replaceable> <ulink> and <link>. | |
| 2683 | |
| 2684 If you want to change how such text is rendered, you must redefine the | |
| 2685 following syntax groups: | |
| 2686 | |
| 2687 - sgmlBold | |
| 2688 - sgmlBoldItalic | |
| 2689 - sgmlUnderline | |
| 2690 - sgmlItalic | |
| 2691 - sgmlLink for links | |
| 2692 | |
| 2693 To make this redefinition work you must redefine them all and define the | |
| 2694 following variable in your vimrc (this is due to the order in which the files | |
| 2695 are read during initialization) > | |
| 2696 let sgml_my_rendering=1 | |
| 2697 | |
| 2698 You can also disable this rendering by adding the following line to your | |
| 2699 vimrc file: > | |
| 2700 let sgml_no_rendering=1 | |
| 2701 | |
| 2702 (Adapted from the html.vim help text by Claudio Fleiner <claudio@fleiner.com>) | |
| 2703 | |
| 2704 | |
| 501 | 2705 SH *sh.vim* *ft-sh-syntax* *ft-bash-syntax* *ft-ksh-syntax* |
| 7 | 2706 |
| 1624 | 2707 This covers the "normal" Unix (Bourne) sh, bash and the Korn shell. |
| 7 | 2708 |
| 2709 Vim attempts to determine which shell type is in use by specifying that | |
| 2710 various filenames are of specific types: > | |
| 2711 | |
| 2712 ksh : .kshrc* *.ksh | |
| 2713 bash: .bashrc* bashrc bash.bashrc .bash_profile* *.bash | |
| 2714 < | |
| 2715 If none of these cases pertain, then the first line of the file is examined | |
| 2716 (ex. /bin/sh /bin/ksh /bin/bash). If the first line specifies a shelltype, | |
| 2717 then that shelltype is used. However some files (ex. .profile) are known to | |
| 2718 be shell files but the type is not apparent. Furthermore, on many systems | |
| 828 | 2719 sh is symbolically linked to "bash" (Linux, Windows+cygwin) or "ksh" (Posix). |
| 7 | 2720 |
| 2721 One may specify a global default by instantiating one of the following three | |
| 2722 variables in your <.vimrc>: | |
| 2723 | |
| 2724 ksh: > | |
| 828 | 2725 let g:is_kornshell = 1 |
| 2726 < posix: (using this is the same as setting is_kornshell to 1) > | |
| 2727 let g:is_posix = 1 | |
| 7 | 2728 < bash: > |
| 828 | 2729 let g:is_bash = 1 |
| 1624 | 2730 < sh: (default) Bourne shell > |
| 828 | 2731 let g:is_sh = 1 |
| 7 | 2732 |
| 819 | 2733 If there's no "#! ..." line, and the user hasn't availed himself/herself of a |
| 2734 default sh.vim syntax setting as just shown, then syntax/sh.vim will assume | |
| 1624 | 2735 the Bourne shell syntax. No need to quote RFCs or market penetration |
| 2736 statistics in error reports, please -- just select the default version of the | |
| 2737 sh your system uses in your <.vimrc>. | |
| 2738 | |
| 2739 The syntax/sh.vim file provides several levels of syntax-based folding: > | |
| 2740 | |
| 2741 let g:sh_fold_enabled= 0 (default, no syntax folding) | |
| 2742 let g:sh_fold_enabled= 1 (enable function folding) | |
| 2743 let g:sh_fold_enabled= 2 (enable heredoc folding) | |
| 2744 let g:sh_fold_enabled= 4 (enable if/do/for folding) | |
| 7 | 2745 > |
| 2746 then various syntax items (HereDocuments and function bodies) become | |
| 1624 | 2747 syntax-foldable (see |:syn-fold|). You also may add these together |
| 2748 to get multiple types of folding: > | |
| 2749 | |
| 2750 let g:sh_fold_enabled= 3 (enables function and heredoc folding) | |
| 2751 | |
| 2752 If you notice highlighting errors while scrolling backwards which are fixed | |
| 2753 when one redraws with CTRL-L, try setting the "sh_minlines" internal variable | |
| 7 | 2754 to a larger number. Example: > |
| 2755 | |
| 2756 let sh_minlines = 500 | |
| 2757 | |
| 2758 This will make syntax synchronization start 500 lines before the first | |
| 2759 displayed line. The default value is 200. The disadvantage of using a larger | |
| 2760 number is that redrawing can become slow. | |
| 2761 | |
| 2762 If you don't have much to synchronize on, displaying can be very slow. To | |
| 2763 reduce this, the "sh_maxlines" internal variable can be set. Example: > | |
| 2764 | |
| 2765 let sh_maxlines = 100 | |
| 2766 < | |
| 2767 The default is to use the twice sh_minlines. Set it to a smaller number to | |
| 2768 speed up displaying. The disadvantage is that highlight errors may appear. | |
| 2769 | |
|
3099
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2770 *g:sh_isk* *g:sh_noisk* |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2771 The shell languages appear to let "." be part of words, commands, etc; |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2772 consequently it should be in the isk for sh.vim. As of v116 of syntax/sh.vim, |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2773 syntax/sh.vim will append the "." to |'iskeyword'| by default; you may control |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2774 this behavior with: > |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2775 let g:sh_isk = '..whatever characters you want as part of iskeyword' |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2776 let g:sh_noisk= 1 " otherwise, if this exists, the isk will NOT chg |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2777 < |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2778 *sh-embed* *sh-awk* |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2779 Sh: EMBEDDING LANGUAGES~ |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2780 |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2781 You may wish to embed languages into sh. I'll give an example courtesy of |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2782 Lorance Stinson on how to do this with awk as an example. Put the following |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2783 file into $HOME/.vim/after/syntax/sh/awkembed.vim: > |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2784 |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2785 " AWK Embedding: {{{1 |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2786 " ============== |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2787 " Shamelessly ripped from aspperl.vim by Aaron Hope. |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2788 if exists("b:current_syntax") |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2789 unlet b:current_syntax |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2790 endif |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2791 syn include @AWKScript syntax/awk.vim |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2792 syn region AWKScriptCode matchgroup=AWKCommand start=+[=\\]\@<!'+ skip=+\\'+ end=+'+ contains=@AWKScript contained |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2793 syn region AWKScriptEmbedded matchgroup=AWKCommand start=+\<awk\>+ skip=+\\$+ end=+[=\\]\@<!'+me=e-1 contains=@shIdList,@shExprList2 nextgroup=AWKScriptCode |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2794 syn cluster shCommandSubList add=AWKScriptEmbedded |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2795 hi def link AWKCommand Type |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2796 < |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2797 This code will then let the awk code in the single quotes: > |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2798 awk '...awk code here...' |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2799 be highlighted using the awk highlighting syntax. Clearly this may be |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2800 extended to other languages. |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2801 |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2802 |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2803 SPEEDUP *spup.vim* *ft-spup-syntax* |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2804 (AspenTech plant simulator) |
| 7 | 2805 |
| 2806 The Speedup syntax file has some options: | |
| 2807 | |
| 2808 - strict_subsections : If this variable is defined, only keywords for | |
| 2809 sections and subsections will be highlighted as statements but not | |
| 2810 other keywords (like WITHIN in the OPERATION section). | |
| 2811 | |
| 2812 - highlight_types : Definition of this variable causes stream types | |
| 2813 like temperature or pressure to be highlighted as Type, not as a | |
| 237 | 2814 plain Identifier. Included are the types that are usually found in |
| 7 | 2815 the DECLARE section; if you defined own types, you have to include |
| 2816 them in the syntax file. | |
| 2817 | |
| 2818 - oneline_comments : this value ranges from 1 to 3 and determines the | |
| 2819 highlighting of # style comments. | |
| 2820 | |
| 2821 oneline_comments = 1 : allow normal Speedup code after an even | |
| 2822 number of #s. | |
| 2823 | |
| 2824 oneline_comments = 2 : show code starting with the second # as | |
| 237 | 2825 error. This is the default setting. |
| 7 | 2826 |
| 2827 oneline_comments = 3 : show the whole line as error if it contains | |
| 2828 more than one #. | |
| 2829 | |
| 2830 Since especially OPERATION sections tend to become very large due to | |
| 237 | 2831 PRESETting variables, syncing may be critical. If your computer is |
| 7 | 2832 fast enough, you can increase minlines and/or maxlines near the end of |
| 2833 the syntax file. | |
| 2834 | |
| 2835 | |
| 501 | 2836 SQL *sql.vim* *ft-sql-syntax* |
| 2837 *sqlinformix.vim* *ft-sqlinformix-syntax* | |
| 720 | 2838 *sqlanywhere.vim* *ft-sqlanywhere-syntax* |
| 2839 | |
| 2840 While there is an ANSI standard for SQL, most database engines add their own | |
| 2841 custom extensions. Vim currently supports the Oracle and Informix dialects of | |
| 2842 SQL. Vim assumes "*.sql" files are Oracle SQL by default. | |
| 2843 | |
| 2844 Vim currently has SQL support for a variety of different vendors via syntax | |
| 2845 scripts. You can change Vim's default from Oracle to any of the current SQL | |
| 2846 supported types. You can also easily alter the SQL dialect being used on a | |
| 2847 buffer by buffer basis. | |
| 2848 | |
| 1624 | 2849 For more detailed instructions see |ft_sql.txt|. |
| 22 | 2850 |
| 2851 | |
| 501 | 2852 TCSH *tcsh.vim* *ft-tcsh-syntax* |
| 7 | 2853 |
| 2854 This covers the shell named "tcsh". It is a superset of csh. See |csh.vim| | |
| 2855 for how the filetype is detected. | |
| 2856 | |
| 2857 Tcsh does not allow \" in strings unless the "backslash_quote" shell variable | |
| 237 | 2858 is set. If you want VIM to assume that no backslash quote constructs exist add |
| 7 | 2859 this line to your .vimrc: > |
| 2860 | |
| 2861 :let tcsh_backslash_quote = 0 | |
| 2862 | |
| 2863 If you notice highlighting errors while scrolling backwards, which are fixed | |
| 2864 when redrawing with CTRL-L, try setting the "tcsh_minlines" internal variable | |
| 2865 to a larger number: > | |
| 2866 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
2867 :let tcsh_minlines = 1000 |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
2868 |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
2869 This will make the syntax synchronization start 1000 lines before the first |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
2870 displayed line. If you set "tcsh_minlines" to "fromstart", then |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
2871 synchronization is done from the start of the file. The default value for |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
2872 tcsh_minlines is 100. The disadvantage of using a larger number is that |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
2873 redrawing can become slow. |
| 7 | 2874 |
| 2875 | |
| 501 | 2876 TEX *tex.vim* *ft-tex-syntax* |
| 7 | 2877 |
| 1624 | 2878 *tex-folding* |
|
2535
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
2879 Tex: Want Syntax Folding? ~ |
| 477 | 2880 |
| 2881 As of version 28 of <syntax/tex.vim>, syntax-based folding of parts, chapters, | |
| 2882 sections, subsections, etc are supported. Put > | |
| 2883 let g:tex_fold_enabled=1 | |
| 2884 in your <.vimrc>, and :set fdm=syntax. I suggest doing the latter via a | |
| 2885 modeline at the end of your LaTeX file: > | |
| 2886 % vim: fdm=syntax | |
|
3099
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2887 If your system becomes too slow, then you might wish to look into > |
| 3153 | 2888 http://vim.wikia.com/wiki/Keep_folds_closed_while_inserting_text |
| 477 | 2889 < |
| 1624 | 2890 *tex-nospell* |
|
2535
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
2891 Tex: Don't Want Spell Checking In Comments? ~ |
| 1624 | 2892 |
| 2893 Some folks like to include things like source code in comments and so would | |
| 2894 prefer that spell checking be disabled in comments in LaTeX files. To do | |
| 2895 this, put the following in your <.vimrc>: > | |
| 2896 let g:tex_comment_nospell= 1 | |
| 3492 | 2897 The comment lines > |
| 2898 % nospell{ | |
| 2899 ... | |
| 2900 % nospell} | |
| 2901 will suppress spell checking between them. These comment lines spelling | |
| 2902 control are known to be fragile; for example, don't include any of the section | |
| 2903 commands (\part, \chapter, \section, \paragraph, etc) inside nospell blocks | |
| 2904 or interleave environments (such as math) across nospell blocks. | |
|
2494
ed997d0ceb26
Updated syntax files. (Charles Campbell)
Bram Moolenaar <bram@vim.org>
parents:
2490
diff
changeset
|
2905 *tex-verb* |
|
2535
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
2906 Tex: Want Spell Checking in Verbatim Zones?~ |
|
2494
ed997d0ceb26
Updated syntax files. (Charles Campbell)
Bram Moolenaar <bram@vim.org>
parents:
2490
diff
changeset
|
2907 |
|
ed997d0ceb26
Updated syntax files. (Charles Campbell)
Bram Moolenaar <bram@vim.org>
parents:
2490
diff
changeset
|
2908 Often verbatim regions are used for things like source code; seldom does |
|
ed997d0ceb26
Updated syntax files. (Charles Campbell)
Bram Moolenaar <bram@vim.org>
parents:
2490
diff
changeset
|
2909 one want source code spell-checked. However, for those of you who do |
|
ed997d0ceb26
Updated syntax files. (Charles Campbell)
Bram Moolenaar <bram@vim.org>
parents:
2490
diff
changeset
|
2910 want your verbatim zones spell-checked, put the following in your <.vimrc>: > |
|
ed997d0ceb26
Updated syntax files. (Charles Campbell)
Bram Moolenaar <bram@vim.org>
parents:
2490
diff
changeset
|
2911 let g:tex_verbspell= 1 |
|
2535
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
2912 < |
| 1624 | 2913 *tex-runon* |
|
2535
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
2914 Tex: Run-on Comments or MathZones ~ |
| 7 | 2915 |
| 477 | 2916 The <syntax/tex.vim> highlighting supports TeX, LaTeX, and some AmsTeX. The |
| 2917 highlighting supports three primary zones/regions: normal, texZone, and | |
| 2918 texMathZone. Although considerable effort has been made to have these zones | |
| 2919 terminate properly, zones delineated by $..$ and $$..$$ cannot be synchronized | |
| 2920 as there's no difference between start and end patterns. Consequently, a | |
| 7 | 2921 special "TeX comment" has been provided > |
| 2922 %stopzone | |
| 2923 which will forcibly terminate the highlighting of either a texZone or a | |
| 2924 texMathZone. | |
| 2925 | |
| 1624 | 2926 *tex-slow* |
|
2535
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
2927 Tex: Slow Syntax Highlighting? ~ |
| 7 | 2928 |
| 2929 If you have a slow computer, you may wish to reduce the values for > | |
| 2930 :syn sync maxlines=200 | |
| 2931 :syn sync minlines=50 | |
| 2932 (especially the latter). If your computer is fast, you may wish to | |
| 237 | 2933 increase them. This primarily affects synchronizing (i.e. just what group, |
| 7 | 2934 if any, is the text at the top of the screen supposed to be in?). |
| 2935 | |
|
3099
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2936 Another cause of slow highlighting is due to syntax-driven folding; see |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2937 |tex-folding| for a way around this. |
|
887d6d91882e
Updated a few runtime files.
Bram Moolenaar <bram@vim.org>
parents:
2965
diff
changeset
|
2938 |
| 4229 | 2939 *g:tex_fast* |
| 2940 | |
| 2941 Finally, if syntax highlighting is still too slow, you may set > | |
| 2942 | |
| 2943 :let g:tex_fast= "" | |
| 2944 | |
| 2945 in your .vimrc. Used this way, the g:tex_fast variable causes the syntax | |
| 2946 highlighting script to avoid defining any regions and associated | |
| 2947 synchronization. The result will be much faster syntax highlighting; the | |
| 2948 price: you will no longer have as much highlighting or any syntax-based | |
| 2949 folding, and you will be missing syntax-based error checking. | |
| 2950 | |
| 2951 You may decide that some syntax is acceptable; you may use the following table | |
| 2952 selectively to enable just some syntax highlighting: > | |
| 2953 | |
| 2954 b : allow bold and italic syntax | |
| 2955 c : allow texComment syntax | |
| 2956 m : allow texMatcher syntax (ie. {...} and [...]) | |
| 2957 M : allow texMath syntax | |
| 2958 p : allow parts, chapter, section, etc syntax | |
| 2959 r : allow texRefZone syntax (nocite, bibliography, label, pageref, eqref) | |
| 2960 s : allow superscript/subscript regions | |
| 2961 S : allow texStyle syntax | |
| 2962 v : allow verbatim syntax | |
| 2963 V : allow texNewEnv and texNewCmd syntax | |
| 2964 < | |
| 2965 As an example, let g:tex_fast= "M" will allow math-associated highlighting | |
| 2966 but suppress all the other region-based syntax highlighting. | |
| 2967 | |
| 1624 | 2968 *tex-morecommands* *tex-package* |
|
2535
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
2969 Tex: Want To Highlight More Commands? ~ |
| 1125 | 2970 |
| 2971 LaTeX is a programmable language, and so there are thousands of packages full | |
| 2972 of specialized LaTeX commands, syntax, and fonts. If you're using such a | |
| 2973 package you'll often wish that the distributed syntax/tex.vim would support | |
| 2974 it. However, clearly this is impractical. So please consider using the | |
| 2975 techniques in |mysyntaxfile-add| to extend or modify the highlighting provided | |
| 3237 | 2976 by syntax/tex.vim. Please consider uploading any extensions that you write, |
| 2977 which typically would go in $HOME/after/syntax/tex/[pkgname].vim, to | |
| 2978 http://vim.sf.net/. | |
| 1125 | 2979 |
| 1624 | 2980 *tex-error* |
|
2535
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
2981 Tex: Excessive Error Highlighting? ~ |
| 7 | 2982 |
| 2983 The <tex.vim> supports lexical error checking of various sorts. Thus, | |
| 2984 although the error checking is ofttimes very useful, it can indicate | |
| 2985 errors where none actually are. If this proves to be a problem for you, | |
| 2986 you may put in your <.vimrc> the following statement: > | |
| 2987 let tex_no_error=1 | |
| 477 | 2988 and all error checking by <syntax/tex.vim> will be suppressed. |
| 2989 | |
| 1624 | 2990 *tex-math* |
|
2535
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
2991 Tex: Need a new Math Group? ~ |
| 7 | 2992 |
| 2993 If you want to include a new math group in your LaTeX, the following | |
| 2994 code shows you an example as to how you might do so: > | |
| 477 | 2995 call TexNewMathZone(sfx,mathzone,starform) |
| 2996 You'll want to provide the new math group with a unique suffix | |
| 2997 (currently, A-L and V-Z are taken by <syntax/tex.vim> itself). | |
| 2998 As an example, consider how eqnarray is set up by <syntax/tex.vim>: > | |
| 2999 call TexNewMathZone("D","eqnarray",1) | |
| 3000 You'll need to change "mathzone" to the name of your new math group, | |
| 3001 and then to the call to it in .vim/after/syntax/tex.vim. | |
| 3002 The "starform" variable, if true, implies that your new math group | |
| 3003 has a starred form (ie. eqnarray*). | |
| 3004 | |
| 1624 | 3005 *tex-style* |
|
2535
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3006 Tex: Starting a New Style? ~ |
| 7 | 3007 |
| 3008 One may use "\makeatletter" in *.tex files, thereby making the use of "@" in | |
| 3009 commands available. However, since the *.tex file doesn't have one of the | |
| 3010 following suffices: sty cls clo dtx ltx, the syntax highlighting will flag | |
| 3011 such use of @ as an error. To solve this: > | |
| 3012 | |
| 3013 :let b:tex_stylish = 1 | |
| 3014 :set ft=tex | |
| 3015 | |
| 3016 Putting "let g:tex_stylish=1" into your <.vimrc> will make <syntax/tex.vim> | |
| 3017 always accept such use of @. | |
| 3018 | |
| 2417 | 3019 *tex-cchar* *tex-cole* *tex-conceal* |
|
2535
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3020 Tex: Taking Advantage of Conceal Mode~ |
| 2417 | 3021 |
| 2426 | 3022 If you have |'conceallevel'| set to 2 and if your encoding is utf-8, then a |
| 3023 number of character sequences can be translated into appropriate utf-8 glyphs, | |
| 3024 including various accented characters, Greek characters in MathZones, and | |
| 3025 superscripts and subscripts in MathZones. Not all characters can be made into | |
| 3026 superscripts or subscripts; the constraint is due to what utf-8 supports. | |
| 3027 In fact, only a few characters are supported as subscripts. | |
| 3028 | |
| 3029 One way to use this is to have vertically split windows (see |CTRL-W_v|); one | |
| 3030 with |'conceallevel'| at 0 and the other at 2; and both using |'scrollbind'|. | |
| 2417 | 3031 |
|
2535
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3032 *g:tex_conceal* |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3033 Tex: Selective Conceal Mode~ |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3034 |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3035 You may selectively use conceal mode by setting g:tex_conceal in your |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3036 <.vimrc>. By default it is set to "admgs" to enable conceal for the |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3037 following sets of characters: > |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3038 |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3039 a = accents/ligatures |
| 3492 | 3040 b = bold and italic |
|
2535
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3041 d = delimiters |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3042 m = math symbols |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3043 g = Greek |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3044 s = superscripts/subscripts |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3045 < |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3046 By leaving one or more of these out, the associated conceal-character |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3047 substitution will not be made. |
|
31e51111bd14
Runtime file updates. Fix tar plugin window split.
Bram Moolenaar <bram@vim.org>
parents:
2527
diff
changeset
|
3048 |
| 3456 | 3049 *g:tex_isk* |
| 3050 Tex: Controlling What's In A Keyword~ | |
| 3051 | |
| 3052 (La)Tex keywords normally use the characters 0-9,a-z,A-Z,192-255 only | |
| 3053 but the "_" is the only one that causes problems. So, by default, | |
| 3465 | 3054 syntax/tex.vim overrides the usual |'iskeyword'| setting (using |:setlocal|) |
| 3456 | 3055 with one that works for LaTeX. |
| 3056 | |
| 3057 However, one may override this iskeyword re-setting by setting the | |
| 3058 variable, g:tex_isk, in one's .vimrc to whatever one wishes and | |
| 3059 it will be used instead. | |
| 3060 | |
| 7 | 3061 |
| 501 | 3062 TF *tf.vim* *ft-tf-syntax* |
| 7 | 3063 |
| 3064 There is one option for the tf syntax highlighting. | |
| 3065 | |
| 3066 For syncing, minlines defaults to 100. If you prefer another value, you can | |
| 3067 set "tf_minlines" to the value you desire. Example: > | |
| 3068 | |
| 3069 :let tf_minlines = your choice | |
| 3070 | |
| 3071 | |
| 1624 | 3072 VIM *vim.vim* *ft-vim-syntax* |
| 3073 *g:vimsyn_minlines* *g:vimsyn_maxlines* | |
|
2283
7e1bd501306d
Mainly documentation updates.
Bram Moolenaar <bram@vim.org>
parents:
2269
diff
changeset
|
3074 There is a trade-off between more accurate syntax highlighting versus screen |
| 1624 | 3075 updating speed. To improve accuracy, you may wish to increase the |
| 3076 g:vimsyn_minlines variable. The g:vimsyn_maxlines variable may be used to | |
| 3077 improve screen updating rates (see |:syn-sync| for more on this). > | |
| 3078 | |
| 3079 g:vimsyn_minlines : used to set synchronization minlines | |
| 3080 g:vimsyn_maxlines : used to set synchronization maxlines | |
| 3081 < | |
| 3082 (g:vim_minlines and g:vim_maxlines are deprecated variants of | |
| 3083 these two options) | |
| 3084 | |
| 3085 *g:vimsyn_embed* | |
| 3086 The g:vimsyn_embed option allows users to select what, if any, types of | |
| 3087 embedded script highlighting they wish to have. > | |
| 3088 | |
| 3089 g:vimsyn_embed == 0 : don't embed any scripts | |
| 3090 g:vimsyn_embed =~ 'm' : embed mzscheme (but only if vim supports it) | |
| 3091 g:vimsyn_embed =~ 'p' : embed perl (but only if vim supports it) | |
| 3092 g:vimsyn_embed =~ 'P' : embed python (but only if vim supports it) | |
| 3093 g:vimsyn_embed =~ 'r' : embed ruby (but only if vim supports it) | |
| 3094 g:vimsyn_embed =~ 't' : embed tcl (but only if vim supports it) | |
| 3095 < | |
| 3096 By default, g:vimsyn_embed is "mpPr"; ie. syntax/vim.vim will support | |
| 3097 highlighting mzscheme, perl, python, and ruby by default. Vim's has("tcl") | |
| 3098 test appears to hang vim when tcl is not truly available. Thus, by default, | |
| 3099 tcl is not supported for embedding (but those of you who like tcl embedded in | |
| 3100 their vim syntax highlighting can simply include it in the g:vimembedscript | |
| 3101 option). | |
| 3102 *g:vimsyn_folding* | |
| 3103 | |
| 3104 Some folding is now supported with syntax/vim.vim: > | |
| 3105 | |
| 3106 g:vimsyn_folding == 0 or doesn't exist: no syntax-based folding | |
| 3107 g:vimsyn_folding =~ 'a' : augroups | |
| 3108 g:vimsyn_folding =~ 'f' : fold functions | |
| 3109 g:vimsyn_folding =~ 'm' : fold mzscheme script | |
| 3110 g:vimsyn_folding =~ 'p' : fold perl script | |
| 3111 g:vimsyn_folding =~ 'P' : fold python script | |
| 3112 g:vimsyn_folding =~ 'r' : fold ruby script | |
| 3113 g:vimsyn_folding =~ 't' : fold tcl script | |
| 3682 | 3114 < |
| 1624 | 3115 *g:vimsyn_noerror* |
| 846 | 3116 Not all error highlighting that syntax/vim.vim does may be correct; VimL is a |
| 3117 difficult language to highlight correctly. A way to suppress error | |
| 1624 | 3118 highlighting is to put the following line in your |vimrc|: > |
| 3119 | |
| 3120 let g:vimsyn_noerror = 1 | |
| 3121 < | |
| 846 | 3122 |
| 7 | 3123 |
| 501 | 3124 XF86CONFIG *xf86conf.vim* *ft-xf86conf-syntax* |
| 7 | 3125 |
| 3126 The syntax of XF86Config file differs in XFree86 v3.x and v4.x. Both | |
| 3127 variants are supported. Automatic detection is used, but is far from perfect. | |
| 3128 You may need to specify the version manually. Set the variable | |
| 3129 xf86conf_xfree86_version to 3 or 4 according to your XFree86 version in | |
| 3130 your .vimrc. Example: > | |
| 3131 :let xf86conf_xfree86_version=3 | |
| 3132 When using a mix of versions, set the b:xf86conf_xfree86_version variable. | |
| 3133 | |
| 3134 Note that spaces and underscores in option names are not supported. Use | |
| 3135 "SyncOnGreen" instead of "__s yn con gr_e_e_n" if you want the option name | |
| 3136 highlighted. | |
| 3137 | |
| 3138 | |
| 501 | 3139 XML *xml.vim* *ft-xml-syntax* |
| 7 | 3140 |
| 237 | 3141 Xml namespaces are highlighted by default. This can be inhibited by |
| 7 | 3142 setting a global variable: > |
| 3143 | |
| 3144 :let g:xml_namespace_transparent=1 | |
| 3145 < | |
| 3146 *xml-folding* | |
| 3147 The xml syntax file provides syntax |folding| (see |:syn-fold|) between | |
| 237 | 3148 start and end tags. This can be turned on by > |
| 7 | 3149 |
| 3150 :let g:xml_syntax_folding = 1 | |
| 3151 :set foldmethod=syntax | |
| 3152 | |
| 3153 Note: syntax folding might slow down syntax highlighting significantly, | |
| 3154 especially for large files. | |
| 3155 | |
| 3156 | |
| 501 | 3157 X Pixmaps (XPM) *xpm.vim* *ft-xpm-syntax* |
| 7 | 3158 |
| 3159 xpm.vim creates its syntax items dynamically based upon the contents of the | |
| 3160 XPM file. Thus if you make changes e.g. in the color specification strings, | |
| 3161 you have to source it again e.g. with ":set syn=xpm". | |
| 3162 | |
| 3163 To copy a pixel with one of the colors, yank a "pixel" with "yl" and insert it | |
| 3164 somewhere else with "P". | |
| 3165 | |
| 3166 Do you want to draw with the mouse? Try the following: > | |
| 3167 :function! GetPixel() | |
| 823 | 3168 : let c = getline(".")[col(".") - 1] |
| 7 | 3169 : echo c |
| 3170 : exe "noremap <LeftMouse> <LeftMouse>r".c | |
| 3171 : exe "noremap <LeftDrag> <LeftMouse>r".c | |
| 3172 :endfunction | |
| 3173 :noremap <RightMouse> <LeftMouse>:call GetPixel()<CR> | |
| 3174 :set guicursor=n:hor20 " to see the color beneath the cursor | |
| 3175 This turns the right button into a pipette and the left button into a pen. | |
| 3176 It will work with XPM files that have one character per pixel only and you | |
| 3177 must not click outside of the pixel strings, but feel free to improve it. | |
| 3178 | |
| 3179 It will look much better with a font in a quadratic cell size, e.g. for X: > | |
| 3180 :set guifont=-*-clean-medium-r-*-*-8-*-*-*-*-80-* | |
| 3181 | |
| 3182 ============================================================================== | |
| 3183 5. Defining a syntax *:syn-define* *E410* | |
| 3184 | |
| 3185 Vim understands three types of syntax items: | |
| 3186 | |
| 419 | 3187 1. Keyword |
| 7 | 3188 It can only contain keyword characters, according to the 'iskeyword' |
| 3189 option. It cannot contain other syntax items. It will only match with a | |
| 3190 complete word (there are no keyword characters before or after the match). | |
| 3191 The keyword "if" would match in "if(a=b)", but not in "ifdef x", because | |
| 3192 "(" is not a keyword character and "d" is. | |
| 3193 | |
| 419 | 3194 2. Match |
| 7 | 3195 This is a match with a single regexp pattern. |
| 3196 | |
| 419 | 3197 3. Region |
| 7 | 3198 This starts at a match of the "start" regexp pattern and ends with a match |
| 3199 with the "end" regexp pattern. Any other text can appear in between. A | |
| 3200 "skip" regexp pattern can be used to avoid matching the "end" pattern. | |
| 3201 | |
| 3202 Several syntax ITEMs can be put into one syntax GROUP. For a syntax group | |
| 3203 you can give highlighting attributes. For example, you could have an item | |
| 3204 to define a "/* .. */" comment and another one that defines a "// .." comment, | |
| 3205 and put them both in the "Comment" group. You can then specify that a | |
| 3206 "Comment" will be in bold font and have a blue color. You are free to make | |
| 3207 one highlight group for one syntax item, or put all items into one group. | |
| 3208 This depends on how you want to specify your highlighting attributes. Putting | |
| 3209 each item in its own group results in having to specify the highlighting | |
| 3210 for a lot of groups. | |
| 3211 | |
| 3212 Note that a syntax group and a highlight group are similar. For a highlight | |
| 3213 group you will have given highlight attributes. These attributes will be used | |
| 3214 for the syntax group with the same name. | |
| 3215 | |
| 3216 In case more than one item matches at the same position, the one that was | |
| 3217 defined LAST wins. Thus you can override previously defined syntax items by | |
| 3218 using an item that matches the same text. But a keyword always goes before a | |
| 3219 match or region. And a keyword with matching case always goes before a | |
| 3220 keyword with ignoring case. | |
| 3221 | |
| 3222 | |
| 3223 PRIORITY *:syn-priority* | |
| 3224 | |
| 3225 When several syntax items may match, these rules are used: | |
| 3226 | |
| 3227 1. When multiple Match or Region items start in the same position, the item | |
| 3228 defined last has priority. | |
| 3229 2. A Keyword has priority over Match and Region items. | |
| 3230 3. An item that starts in an earlier position has priority over items that | |
| 3231 start in later positions. | |
| 3232 | |
| 3233 | |
| 3234 DEFINING CASE *:syn-case* *E390* | |
| 3235 | |
| 419 | 3236 :sy[ntax] case [match | ignore] |
| 7 | 3237 This defines if the following ":syntax" commands will work with |
| 3238 matching case, when using "match", or with ignoring case, when using | |
| 3239 "ignore". Note that any items before this are not affected, and all | |
| 3240 items until the next ":syntax case" command are affected. | |
| 3241 | |
| 3242 | |
| 419 | 3243 SPELL CHECKING *:syn-spell* |
| 3244 | |
| 3245 :sy[ntax] spell [toplevel | notoplevel | default] | |
| 3246 This defines where spell checking is to be done for text that is not | |
| 3247 in a syntax item: | |
| 3248 | |
| 3249 toplevel: Text is spell checked. | |
| 3250 notoplevel: Text is not spell checked. | |
| 3251 default: When there is a @Spell cluster no spell checking. | |
| 3252 | |
| 3253 For text in syntax items use the @Spell and @NoSpell clusters | |
| 3254 |spell-syntax|. When there is no @Spell and no @NoSpell cluster then | |
| 3255 spell checking is done for "default" and "toplevel". | |
| 3256 | |
| 3257 To activate spell checking the 'spell' option must be set. | |
| 3258 | |
| 3259 | |
| 7 | 3260 DEFINING KEYWORDS *:syn-keyword* |
| 3261 | |
| 3262 :sy[ntax] keyword {group-name} [{options}] {keyword} .. [{options}] | |
| 3263 | |
| 3264 This defines a number of keywords. | |
| 3265 | |
| 3266 {group-name} Is a syntax group name such as "Comment". | |
| 3267 [{options}] See |:syn-arguments| below. | |
| 3268 {keyword} .. Is a list of keywords which are part of this group. | |
| 3269 | |
| 3270 Example: > | |
| 3271 :syntax keyword Type int long char | |
| 3272 < | |
| 3273 The {options} can be given anywhere in the line. They will apply to | |
| 3274 all keywords given, also for options that come after a keyword. | |
| 3275 These examples do exactly the same: > | |
| 3276 :syntax keyword Type contained int long char | |
| 3277 :syntax keyword Type int long contained char | |
| 3278 :syntax keyword Type int long char contained | |
| 838 | 3279 < *E789* |
| 7 | 3280 When you have a keyword with an optional tail, like Ex commands in |
| 3281 Vim, you can put the optional characters inside [], to define all the | |
| 3282 variations at once: > | |
| 3283 :syntax keyword vimCommand ab[breviate] n[ext] | |
| 3284 < | |
| 3285 Don't forget that a keyword can only be recognized if all the | |
| 3286 characters are included in the 'iskeyword' option. If one character | |
| 3287 isn't, the keyword will never be recognized. | |
| 3288 Multi-byte characters can also be used. These do not have to be in | |
| 3289 'iskeyword'. | |
| 3290 | |
| 3291 A keyword always has higher priority than a match or region, the | |
| 3292 keyword is used if more than one item matches. Keywords do not nest | |
| 3293 and a keyword can't contain anything else. | |
| 3294 | |
| 3295 Note that when you have a keyword that is the same as an option (even | |
| 3296 one that isn't allowed here), you can not use it. Use a match | |
| 3297 instead. | |
| 3298 | |
| 3299 The maximum length of a keyword is 80 characters. | |
| 3300 | |
| 3301 The same keyword can be defined multiple times, when its containment | |
| 3302 differs. For example, you can define the keyword once not contained | |
| 3303 and use one highlight group, and once contained, and use a different | |
| 237 | 3304 highlight group. Example: > |
| 7 | 3305 :syn keyword vimCommand tag |
| 3306 :syn keyword vimSetting contained tag | |
| 3307 < When finding "tag" outside of any syntax item, the "vimCommand" | |
| 3308 highlight group is used. When finding "tag" in a syntax item that | |
| 3309 contains "vimSetting", the "vimSetting" group is used. | |
| 3310 | |
| 3311 | |
| 3312 DEFINING MATCHES *:syn-match* | |
| 3313 | |
| 3314 :sy[ntax] match {group-name} [{options}] [excludenl] {pattern} [{options}] | |
| 3315 | |
| 3316 This defines one match. | |
| 3317 | |
| 3318 {group-name} A syntax group name such as "Comment". | |
| 3319 [{options}] See |:syn-arguments| below. | |
| 3320 [excludenl] Don't make a pattern with the end-of-line "$" | |
| 3321 extend a containing match or region. Must be | |
| 3322 given before the pattern. |:syn-excludenl| | |
| 3323 {pattern} The search pattern that defines the match. | |
| 3324 See |:syn-pattern| below. | |
| 3325 Note that the pattern may match more than one | |
| 3326 line, which makes the match depend on where | |
| 3327 Vim starts searching for the pattern. You | |
| 3328 need to make sure syncing takes care of this. | |
| 3329 | |
| 3330 Example (match a character constant): > | |
| 3331 :syntax match Character /'.'/hs=s+1,he=e-1 | |
| 3332 < | |
| 3333 | |
| 3334 DEFINING REGIONS *:syn-region* *:syn-start* *:syn-skip* *:syn-end* | |
| 3335 *E398* *E399* | |
| 3336 :sy[ntax] region {group-name} [{options}] | |
| 3337 [matchgroup={group-name}] | |
| 3338 [keepend] | |
| 3339 [extend] | |
| 3340 [excludenl] | |
| 3341 start={start_pattern} .. | |
| 3342 [skip={skip_pattern}] | |
| 3343 end={end_pattern} .. | |
| 3344 [{options}] | |
| 3345 | |
| 3346 This defines one region. It may span several lines. | |
| 3347 | |
| 3348 {group-name} A syntax group name such as "Comment". | |
| 3349 [{options}] See |:syn-arguments| below. | |
| 3350 [matchgroup={group-name}] The syntax group to use for the following | |
| 3351 start or end pattern matches only. Not used | |
| 3352 for the text in between the matched start and | |
| 3353 end patterns. Use NONE to reset to not using | |
| 3354 a different group for the start or end match. | |
| 3355 See |:syn-matchgroup|. | |
| 3356 keepend Don't allow contained matches to go past a | |
| 3357 match with the end pattern. See | |
| 3358 |:syn-keepend|. | |
| 3359 extend Override a "keepend" for an item this region | |
| 237 | 3360 is contained in. See |:syn-extend|. |
| 7 | 3361 excludenl Don't make a pattern with the end-of-line "$" |
| 3362 extend a containing match or item. Only | |
| 3363 useful for end patterns. Must be given before | |
| 3364 the patterns it applies to. |:syn-excludenl| | |
| 3365 start={start_pattern} The search pattern that defines the start of | |
| 3366 the region. See |:syn-pattern| below. | |
| 3367 skip={skip_pattern} The search pattern that defines text inside | |
| 3368 the region where not to look for the end | |
| 3369 pattern. See |:syn-pattern| below. | |
| 3370 end={end_pattern} The search pattern that defines the end of | |
| 3371 the region. See |:syn-pattern| below. | |
| 3372 | |
| 3373 Example: > | |
| 3374 :syntax region String start=+"+ skip=+\\"+ end=+"+ | |
| 3375 < | |
| 3376 The start/skip/end patterns and the options can be given in any order. | |
| 3377 There can be zero or one skip pattern. There must be one or more | |
| 3378 start and end patterns. This means that you can omit the skip | |
| 3379 pattern, but you must give at least one start and one end pattern. It | |
| 3380 is allowed to have white space before and after the equal sign | |
| 3381 (although it mostly looks better without white space). | |
| 3382 | |
| 3383 When more than one start pattern is given, a match with one of these | |
| 3384 is sufficient. This means there is an OR relation between the start | |
| 3385 patterns. The last one that matches is used. The same is true for | |
| 3386 the end patterns. | |
| 3387 | |
| 3388 The search for the end pattern starts right after the start pattern. | |
| 3389 Offsets are not used for this. This implies that the match for the | |
| 3390 end pattern will never overlap with the start pattern. | |
| 3391 | |
| 3392 The skip and end pattern can match across line breaks, but since the | |
| 3393 search for the pattern can start in any line it often does not do what | |
| 3394 you want. The skip pattern doesn't avoid a match of an end pattern in | |
| 3395 the next line. Use single-line patterns to avoid trouble. | |
| 3396 | |
| 3397 Note: The decision to start a region is only based on a matching start | |
| 3398 pattern. There is no check for a matching end pattern. This does NOT | |
| 3399 work: > | |
| 3400 :syn region First start="(" end=":" | |
| 3401 :syn region Second start="(" end=";" | |
| 3402 < The Second always matches before the First (last defined pattern has | |
| 3403 higher priority). The Second region then continues until the next | |
| 3404 ';', no matter if there is a ':' before it. Using a match does work: > | |
| 3405 :syn match First "(\_.\{-}:" | |
| 3406 :syn match Second "(\_.\{-};" | |
| 3407 < This pattern matches any character or line break with "\_." and | |
| 3408 repeats that with "\{-}" (repeat as few as possible). | |
| 3409 | |
| 3410 *:syn-keepend* | |
| 3411 By default, a contained match can obscure a match for the end pattern. | |
| 3412 This is useful for nesting. For example, a region that starts with | |
| 3413 "{" and ends with "}", can contain another region. An encountered "}" | |
| 3414 will then end the contained region, but not the outer region: | |
| 3415 { starts outer "{}" region | |
| 3416 { starts contained "{}" region | |
| 3417 } ends contained "{}" region | |
| 3418 } ends outer "{} region | |
| 3419 If you don't want this, the "keepend" argument will make the matching | |
| 3420 of an end pattern of the outer region also end any contained item. | |
| 3421 This makes it impossible to nest the same region, but allows for | |
| 3422 contained items to highlight parts of the end pattern, without causing | |
| 3423 that to skip the match with the end pattern. Example: > | |
| 3424 :syn match vimComment +"[^"]\+$+ | |
| 3425 :syn region vimCommand start="set" end="$" contains=vimComment keepend | |
| 3426 < The "keepend" makes the vimCommand always end at the end of the line, | |
| 3427 even though the contained vimComment includes a match with the <EOL>. | |
| 3428 | |
| 3429 When "keepend" is not used, a match with an end pattern is retried | |
| 3430 after each contained match. When "keepend" is included, the first | |
| 3431 encountered match with an end pattern is used, truncating any | |
| 3432 contained matches. | |
| 3433 *:syn-extend* | |
| 3434 The "keepend" behavior can be changed by using the "extend" argument. | |
| 3435 When an item with "extend" is contained in an item that uses | |
| 3436 "keepend", the "keepend" is ignored and the containing region will be | |
| 3437 extended. | |
| 3438 This can be used to have some contained items extend a region while | |
| 3439 others don't. Example: > | |
| 3440 | |
| 3441 :syn region htmlRef start=+<a>+ end=+</a>+ keepend contains=htmlItem,htmlScript | |
| 3442 :syn match htmlItem +<[^>]*>+ contained | |
| 3443 :syn region htmlScript start=+<script+ end=+</script[^>]*>+ contained extend | |
| 3444 | |
| 3445 < Here the htmlItem item does not make the htmlRef item continue | |
| 3446 further, it is only used to highlight the <> items. The htmlScript | |
| 3447 item does extend the htmlRef item. | |
| 3448 | |
| 3449 Another example: > | |
| 3450 :syn region xmlFold start="<a>" end="</a>" fold transparent keepend extend | |
| 3451 < This defines a region with "keepend", so that its end cannot be | |
| 3452 changed by contained items, like when the "</a>" is matched to | |
| 3453 highlight it differently. But when the xmlFold region is nested (it | |
| 3454 includes itself), the "extend" applies, so that the "</a>" of a nested | |
| 3455 region only ends that region, and not the one it is contained in. | |
| 3456 | |
| 3457 *:syn-excludenl* | |
| 3458 When a pattern for a match or end pattern of a region includes a '$' | |
| 3459 to match the end-of-line, it will make a region item that it is | |
| 3460 contained in continue on the next line. For example, a match with | |
| 3461 "\\$" (backslash at the end of the line) can make a region continue | |
| 3462 that would normally stop at the end of the line. This is the default | |
| 3463 behavior. If this is not wanted, there are two ways to avoid it: | |
| 3464 1. Use "keepend" for the containing item. This will keep all | |
| 3465 contained matches from extending the match or region. It can be | |
| 3466 used when all contained items must not extend the containing item. | |
| 3467 2. Use "excludenl" in the contained item. This will keep that match | |
| 3468 from extending the containing match or region. It can be used if | |
| 3469 only some contained items must not extend the containing item. | |
| 3470 "excludenl" must be given before the pattern it applies to. | |
| 3471 | |
| 3472 *:syn-matchgroup* | |
| 3473 "matchgroup" can be used to highlight the start and/or end pattern | |
| 3474 differently than the body of the region. Example: > | |
| 3475 :syntax region String matchgroup=Quote start=+"+ skip=+\\"+ end=+"+ | |
| 3476 < This will highlight the quotes with the "Quote" group, and the text in | |
| 3477 between with the "String" group. | |
| 3478 The "matchgroup" is used for all start and end patterns that follow, | |
| 3479 until the next "matchgroup". Use "matchgroup=NONE" to go back to not | |
| 3480 using a matchgroup. | |
| 3481 | |
| 3482 In a start or end pattern that is highlighted with "matchgroup" the | |
| 3483 contained items of the region are not used. This can be used to avoid | |
| 3484 that a contained item matches in the start or end pattern match. When | |
| 3485 using "transparent", this does not apply to a start or end pattern | |
| 3486 match that is highlighted with "matchgroup". | |
| 3487 | |
| 3488 Here is an example, which highlights three levels of parentheses in | |
| 3489 different colors: > | |
| 3490 :sy region par1 matchgroup=par1 start=/(/ end=/)/ contains=par2 | |
| 3491 :sy region par2 matchgroup=par2 start=/(/ end=/)/ contains=par3 contained | |
| 3492 :sy region par3 matchgroup=par3 start=/(/ end=/)/ contains=par1 contained | |
| 3493 :hi par1 ctermfg=red guifg=red | |
| 3494 :hi par2 ctermfg=blue guifg=blue | |
| 3495 :hi par3 ctermfg=darkgreen guifg=darkgreen | |
| 2751 | 3496 < |
| 3497 *E849* | |
| 3498 The maximum number of syntax groups is 19999. | |
| 7 | 3499 |
| 3500 ============================================================================== | |
| 3501 6. :syntax arguments *:syn-arguments* | |
| 3502 | |
| 3503 The :syntax commands that define syntax items take a number of arguments. | |
| 3504 The common ones are explained here. The arguments may be given in any order | |
| 3505 and may be mixed with patterns. | |
| 3506 | |
| 3507 Not all commands accept all arguments. This table shows which arguments | |
| 3508 can not be used for all commands: | |
| 2520 | 3509 *E395* |
|
2250
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3510 contains oneline fold display extend concealends~ |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3511 :syntax keyword - - - - - - |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3512 :syntax match yes - yes yes yes - |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3513 :syntax region yes yes yes yes yes yes |
| 7 | 3514 |
| 3515 These arguments can be used for all three commands: | |
|
2250
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3516 conceal |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3517 cchar |
| 7 | 3518 contained |
| 3519 containedin | |
| 3520 nextgroup | |
| 3521 transparent | |
| 3522 skipwhite | |
| 3523 skipnl | |
| 3524 skipempty | |
| 3525 | |
|
2250
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3526 conceal *conceal* *:syn-conceal* |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3527 |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3528 When the "conceal" argument is given, the item is marked as concealable. |
|
2269
fb627e94e6c6
Couple of small fixes for conceal feature. (Dominique Pelle)
Bram Moolenaar <bram@vim.org>
parents:
2254
diff
changeset
|
3529 Whether or not it is actually concealed depends on the value of the |
|
2378
85b7dc8da5eb
Add the 'concealcursor' option to decide when the cursor line is to be
Bram Moolenaar <bram@vim.org>
parents:
2370
diff
changeset
|
3530 'conceallevel' option. The 'concealcursor' option is used to decide whether |
|
85b7dc8da5eb
Add the 'concealcursor' option to decide when the cursor line is to be
Bram Moolenaar <bram@vim.org>
parents:
2370
diff
changeset
|
3531 concealable items in the current line are displayed unconcealed to be able to |
|
85b7dc8da5eb
Add the 'concealcursor' option to decide when the cursor line is to be
Bram Moolenaar <bram@vim.org>
parents:
2370
diff
changeset
|
3532 edit the line. |
|
2250
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3533 |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3534 concealends *:syn-concealends* |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3535 |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3536 When the "concealends" argument is given, the start and end matches of |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3537 the region, but not the contents of the region, are marked as concealable. |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3538 Whether or not they are actually concealed depends on the setting on the |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3539 'conceallevel' option. The ends of a region can only be concealed separately |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3540 in this way when they have their own highlighting via "matchgroup" |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3541 |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3542 cchar *:syn-cchar* |
|
2698
b6471224d2af
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
2681
diff
changeset
|
3543 *E844* |
|
2250
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3544 The "cchar" argument defines the character shown in place of the item |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3545 when it is concealed (setting "cchar" only makes sense when the conceal |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3546 argument is given.) If "cchar" is not set then the default conceal |
|
2698
b6471224d2af
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
2681
diff
changeset
|
3547 character defined in the 'listchars' option is used. The character cannot be |
|
b6471224d2af
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
2681
diff
changeset
|
3548 a control character such as Tab. Example: > |
|
2250
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3549 :syntax match Entity "&" conceal cchar=& |
|
2296
eb7be7b075a6
Support :browse for commands that use an error file argument. (Lech Lorens)
Bram Moolenaar <bram@vim.org>
parents:
2283
diff
changeset
|
3550 See |hl-Conceal| for highlighting. |
| 7 | 3551 |
| 3552 contained *:syn-contained* | |
| 3553 | |
| 3554 When the "contained" argument is given, this item will not be recognized at | |
| 3555 the top level, but only when it is mentioned in the "contains" field of | |
| 3556 another match. Example: > | |
| 3557 :syntax keyword Todo TODO contained | |
| 3558 :syntax match Comment "//.*" contains=Todo | |
| 3559 | |
| 3560 | |
| 3561 display *:syn-display* | |
| 3562 | |
| 3563 If the "display" argument is given, this item will be skipped when the | |
| 3564 detected highlighting will not be displayed. This will speed up highlighting, | |
| 3565 by skipping this item when only finding the syntax state for the text that is | |
| 3566 to be displayed. | |
| 3567 | |
| 3568 Generally, you can use "display" for match and region items that meet these | |
| 3569 conditions: | |
| 3570 - The item does not continue past the end of a line. Example for C: A region | |
| 3571 for a "/*" comment can't contain "display", because it continues on the next | |
| 3572 line. | |
| 3573 - The item does not contain items that continue past the end of the line or | |
| 3574 make it continue on the next line. | |
| 3575 - The item does not change the size of any item it is contained in. Example | |
| 3576 for C: A match with "\\$" in a preprocessor match can't have "display", | |
| 3577 because it may make that preprocessor match shorter. | |
| 3578 - The item does not allow other items to match that didn't match otherwise, | |
| 3579 and that item may extend the match too far. Example for C: A match for a | |
| 3580 "//" comment can't use "display", because a "/*" inside that comment would | |
| 3581 match then and start a comment which extends past the end of the line. | |
| 3582 | |
| 3583 Examples, for the C language, where "display" can be used: | |
| 3584 - match with a number | |
| 3585 - match with a label | |
| 3586 | |
| 3587 | |
| 3588 transparent *:syn-transparent* | |
| 3589 | |
| 3590 If the "transparent" argument is given, this item will not be highlighted | |
| 3591 itself, but will take the highlighting of the item it is contained in. This | |
| 3592 is useful for syntax items that don't need any highlighting but are used | |
| 3593 only to skip over a part of the text. | |
| 3594 | |
| 3595 The "contains=" argument is also inherited from the item it is contained in, | |
| 3596 unless a "contains" argument is given for the transparent item itself. To | |
| 3597 avoid that unwanted items are contained, use "contains=NONE". Example, which | |
| 3598 highlights words in strings, but makes an exception for "vim": > | |
| 3599 :syn match myString /'[^']*'/ contains=myWord,myVim | |
| 3600 :syn match myWord /\<[a-z]*\>/ contained | |
| 3601 :syn match myVim /\<vim\>/ transparent contained contains=NONE | |
| 3602 :hi link myString String | |
| 3603 :hi link myWord Comment | |
| 3604 Since the "myVim" match comes after "myWord" it is the preferred match (last | |
| 3605 match in the same position overrules an earlier one). The "transparent" | |
| 3606 argument makes the "myVim" match use the same highlighting as "myString". But | |
| 3607 it does not contain anything. If the "contains=NONE" argument would be left | |
| 3608 out, then "myVim" would use the contains argument from myString and allow | |
| 3609 "myWord" to be contained, which will be highlighted as a Constant. This | |
| 3610 happens because a contained match doesn't match inside itself in the same | |
| 3611 position, thus the "myVim" match doesn't overrule the "myWord" match here. | |
| 3612 | |
| 3613 When you look at the colored text, it is like looking at layers of contained | |
| 3614 items. The contained item is on top of the item it is contained in, thus you | |
| 3615 see the contained item. When a contained item is transparent, you can look | |
| 3616 through, thus you see the item it is contained in. In a picture: | |
| 3617 | |
| 3618 look from here | |
| 3619 | |
| 3620 | | | | | | | |
| 3621 V V V V V V | |
| 3622 | |
| 3623 xxxx yyy more contained items | |
| 3624 .................... contained item (transparent) | |
| 3625 ============================= first item | |
| 3626 | |
| 3627 The 'x', 'y' and '=' represent a highlighted syntax item. The '.' represent a | |
| 3628 transparent group. | |
| 3629 | |
| 3630 What you see is: | |
| 3631 | |
| 3632 =======xxxx=======yyy======== | |
| 3633 | |
| 3634 Thus you look through the transparent "....". | |
| 3635 | |
| 3636 | |
| 3637 oneline *:syn-oneline* | |
| 3638 | |
| 3639 The "oneline" argument indicates that the region does not cross a line | |
| 3640 boundary. It must match completely in the current line. However, when the | |
| 3641 region has a contained item that does cross a line boundary, it continues on | |
| 3642 the next line anyway. A contained item can be used to recognize a line | |
| 3643 continuation pattern. But the "end" pattern must still match in the first | |
| 3644 line, otherwise the region doesn't even start. | |
| 3645 | |
| 3646 When the start pattern includes a "\n" to match an end-of-line, the end | |
| 3647 pattern must be found in the same line as where the start pattern ends. The | |
| 3648 end pattern may also include an end-of-line. Thus the "oneline" argument | |
| 3649 means that the end of the start pattern and the start of the end pattern must | |
| 3650 be within one line. This can't be changed by a skip pattern that matches a | |
| 3651 line break. | |
| 3652 | |
| 3653 | |
| 3654 fold *:syn-fold* | |
| 3655 | |
| 1624 | 3656 The "fold" argument makes the fold level increase by one for this item. |
| 7 | 3657 Example: > |
| 3658 :syn region myFold start="{" end="}" transparent fold | |
| 3659 :syn sync fromstart | |
| 3660 :set foldmethod=syntax | |
| 3661 This will make each {} block form one fold. | |
| 3662 | |
| 3663 The fold will start on the line where the item starts, and end where the item | |
| 3664 ends. If the start and end are within the same line, there is no fold. | |
| 3665 The 'foldnestmax' option limits the nesting of syntax folds. | |
| 3666 {not available when Vim was compiled without |+folding| feature} | |
| 3667 | |
| 3668 | |
| 3669 *:syn-contains* *E405* *E406* *E407* *E408* *E409* | |
| 3670 contains={groupname},.. | |
| 3671 | |
| 3672 The "contains" argument is followed by a list of syntax group names. These | |
| 3673 groups will be allowed to begin inside the item (they may extend past the | |
| 3674 containing group's end). This allows for recursive nesting of matches and | |
| 3675 regions. If there is no "contains" argument, no groups will be contained in | |
| 3676 this item. The group names do not need to be defined before they can be used | |
| 3677 here. | |
| 3678 | |
| 3679 contains=ALL | |
| 3680 If the only item in the contains list is "ALL", then all | |
| 3681 groups will be accepted inside the item. | |
| 3682 | |
| 3683 contains=ALLBUT,{group-name},.. | |
| 3684 If the first item in the contains list is "ALLBUT", then all | |
| 3685 groups will be accepted inside the item, except the ones that | |
| 3686 are listed. Example: > | |
| 3687 :syntax region Block start="{" end="}" ... contains=ALLBUT,Function | |
| 3688 | |
| 3689 contains=TOP | |
| 3690 If the first item in the contains list is "TOP", then all | |
| 3691 groups will be accepted that don't have the "contained" | |
| 3692 argument. | |
| 3693 contains=TOP,{group-name},.. | |
| 3694 Like "TOP", but excluding the groups that are listed. | |
| 3695 | |
| 3696 contains=CONTAINED | |
| 3697 If the first item in the contains list is "CONTAINED", then | |
| 3698 all groups will be accepted that have the "contained" | |
| 3699 argument. | |
| 3700 contains=CONTAINED,{group-name},.. | |
| 3701 Like "CONTAINED", but excluding the groups that are | |
| 3702 listed. | |
| 3703 | |
| 3704 | |
| 3705 The {group-name} in the "contains" list can be a pattern. All group names | |
| 3706 that match the pattern will be included (or excluded, if "ALLBUT" is used). | |
| 3707 The pattern cannot contain white space or a ','. Example: > | |
| 3708 ... contains=Comment.*,Keyw[0-3] | |
| 3709 The matching will be done at moment the syntax command is executed. Groups | |
| 3710 that are defined later will not be matched. Also, if the current syntax | |
| 3711 command defines a new group, it is not matched. Be careful: When putting | |
| 3712 syntax commands in a file you can't rely on groups NOT being defined, because | |
| 3713 the file may have been sourced before, and ":syn clear" doesn't remove the | |
| 3714 group names. | |
| 3715 | |
| 3716 The contained groups will also match in the start and end patterns of a | |
| 3717 region. If this is not wanted, the "matchgroup" argument can be used | |
| 3718 |:syn-matchgroup|. The "ms=" and "me=" offsets can be used to change the | |
| 3719 region where contained items do match. Note that this may also limit the | |
| 3720 area that is highlighted | |
| 3721 | |
| 3722 | |
| 3723 containedin={groupname}... *:syn-containedin* | |
| 3724 | |
| 3725 The "containedin" argument is followed by a list of syntax group names. The | |
| 3726 item will be allowed to begin inside these groups. This works as if the | |
| 3727 containing item has a "contains=" argument that includes this item. | |
| 3728 | |
| 3729 The {groupname}... can be used just like for "contains", as explained above. | |
| 3730 | |
| 3731 This is useful when adding a syntax item afterwards. An item can be told to | |
| 3732 be included inside an already existing item, without changing the definition | |
| 3733 of that item. For example, to highlight a word in a C comment after loading | |
| 3734 the C syntax: > | |
| 3735 :syn keyword myword HELP containedin=cComment contained | |
| 3736 Note that "contained" is also used, to avoid that the item matches at the top | |
| 3737 level. | |
| 3738 | |
| 3739 Matches for "containedin" are added to the other places where the item can | |
| 3740 appear. A "contains" argument may also be added as usual. Don't forget that | |
| 3741 keywords never contain another item, thus adding them to "containedin" won't | |
| 3742 work. | |
| 3743 | |
| 3744 | |
| 3745 nextgroup={groupname},.. *:syn-nextgroup* | |
| 3746 | |
| 3747 The "nextgroup" argument is followed by a list of syntax group names, | |
| 3748 separated by commas (just like with "contains", so you can also use patterns). | |
| 3749 | |
| 3750 If the "nextgroup" argument is given, the mentioned syntax groups will be | |
| 3751 tried for a match, after the match or region ends. If none of the groups have | |
| 3752 a match, highlighting continues normally. If there is a match, this group | |
| 3753 will be used, even when it is not mentioned in the "contains" field of the | |
| 3754 current group. This is like giving the mentioned group priority over all | |
| 3755 other groups. Example: > | |
| 3756 :syntax match ccFoobar "Foo.\{-}Bar" contains=ccFoo | |
| 3757 :syntax match ccFoo "Foo" contained nextgroup=ccFiller | |
| 3758 :syntax region ccFiller start="." matchgroup=ccBar end="Bar" contained | |
| 3759 | |
| 3760 This will highlight "Foo" and "Bar" differently, and only when there is a | |
| 3761 "Bar" after "Foo". In the text line below, "f" shows where ccFoo is used for | |
| 3762 highlighting, and "bbb" where ccBar is used. > | |
| 3763 | |
| 3764 Foo asdfasd Bar asdf Foo asdf Bar asdf | |
| 3765 fff bbb fff bbb | |
| 3766 | |
| 3767 Note the use of ".\{-}" to skip as little as possible until the next Bar. | |
| 3768 when ".*" would be used, the "asdf" in between "Bar" and "Foo" would be | |
| 3769 highlighted according to the "ccFoobar" group, because the ccFooBar match | |
| 3770 would include the first "Foo" and the last "Bar" in the line (see |pattern|). | |
| 3771 | |
| 3772 | |
| 3773 skipwhite *:syn-skipwhite* | |
| 3774 skipnl *:syn-skipnl* | |
| 3775 skipempty *:syn-skipempty* | |
| 3776 | |
| 3777 These arguments are only used in combination with "nextgroup". They can be | |
| 3778 used to allow the next group to match after skipping some text: | |
| 1275 | 3779 skipwhite skip over space and tab characters |
| 7 | 3780 skipnl skip over the end of a line |
| 3781 skipempty skip over empty lines (implies a "skipnl") | |
| 3782 | |
| 3783 When "skipwhite" is present, the white space is only skipped if there is no | |
| 3784 next group that matches the white space. | |
| 3785 | |
| 3786 When "skipnl" is present, the match with nextgroup may be found in the next | |
| 3787 line. This only happens when the current item ends at the end of the current | |
| 3788 line! When "skipnl" is not present, the nextgroup will only be found after | |
| 3789 the current item in the same line. | |
| 3790 | |
| 3791 When skipping text while looking for a next group, the matches for other | |
| 3792 groups are ignored. Only when no next group matches, other items are tried | |
| 3793 for a match again. This means that matching a next group and skipping white | |
| 3794 space and <EOL>s has a higher priority than other items. | |
| 3795 | |
| 3796 Example: > | |
| 3797 :syn match ifstart "\<if.*" nextgroup=ifline skipwhite skipempty | |
| 3798 :syn match ifline "[^ \t].*" nextgroup=ifline skipwhite skipempty contained | |
| 3799 :syn match ifline "endif" contained | |
| 3800 Note that the "[^ \t].*" match matches all non-white text. Thus it would also | |
| 3801 match "endif". Therefore the "endif" match is put last, so that it takes | |
| 3802 precedence. | |
| 3803 Note that this example doesn't work for nested "if"s. You need to add | |
| 3804 "contains" arguments to make that work (omitted for simplicity of the | |
| 3805 example). | |
| 3806 | |
|
2250
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3807 IMPLICIT CONCEAL *:syn-conceal-implicit* |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3808 |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3809 :sy[ntax] conceal [on|off] |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3810 This defines if the following ":syntax" commands will define keywords, |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3811 matches or regions with the "conceal" flag set. After ":syn conceal |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3812 on", all subsequent ":syn keyword", ":syn match" or ":syn region" |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3813 defined will have the "conceal" flag set implicitly. ":syn conceal |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3814 off" returns to the normal state where the "conceal" flag must be |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3815 given explicitly. |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
3816 |
| 7 | 3817 ============================================================================== |
| 3818 7. Syntax patterns *:syn-pattern* *E401* *E402* | |
| 3819 | |
| 3820 In the syntax commands, a pattern must be surrounded by two identical | |
| 3821 characters. This is like it works for the ":s" command. The most common to | |
| 3822 use is the double quote. But if the pattern contains a double quote, you can | |
| 3823 use another character that is not used in the pattern. Examples: > | |
| 3824 :syntax region Comment start="/\*" end="\*/" | |
| 3825 :syntax region String start=+"+ end=+"+ skip=+\\"+ | |
| 3826 | |
| 3827 See |pattern| for the explanation of what a pattern is. Syntax patterns are | |
| 1624 | 3828 always interpreted like the 'magic' option is set, no matter what the actual |
| 7 | 3829 value of 'magic' is. And the patterns are interpreted like the 'l' flag is |
| 3830 not included in 'cpoptions'. This was done to make syntax files portable and | |
| 3831 independent of 'compatible' and 'magic' settings. | |
| 3832 | |
| 3833 Try to avoid patterns that can match an empty string, such as "[a-z]*". | |
| 3834 This slows down the highlighting a lot, because it matches everywhere. | |
| 3835 | |
| 3836 *:syn-pattern-offset* | |
| 3837 The pattern can be followed by a character offset. This can be used to | |
| 3838 change the highlighted part, and to change the text area included in the | |
| 3839 match or region (which only matters when trying to match other items). Both | |
| 3840 are relative to the matched pattern. The character offset for a skip | |
| 3841 pattern can be used to tell where to continue looking for an end pattern. | |
| 3842 | |
| 3843 The offset takes the form of "{what}={offset}" | |
| 3844 The {what} can be one of seven strings: | |
| 3845 | |
| 3846 ms Match Start offset for the start of the matched text | |
| 3847 me Match End offset for the end of the matched text | |
| 3848 hs Highlight Start offset for where the highlighting starts | |
| 3849 he Highlight End offset for where the highlighting ends | |
| 3850 rs Region Start offset for where the body of a region starts | |
| 3851 re Region End offset for where the body of a region ends | |
| 3852 lc Leading Context offset past "leading context" of pattern | |
| 3853 | |
| 3854 The {offset} can be: | |
| 3855 | |
| 3856 s start of the matched pattern | |
| 3857 s+{nr} start of the matched pattern plus {nr} chars to the right | |
| 3858 s-{nr} start of the matched pattern plus {nr} chars to the left | |
| 3859 e end of the matched pattern | |
| 3860 e+{nr} end of the matched pattern plus {nr} chars to the right | |
| 3861 e-{nr} end of the matched pattern plus {nr} chars to the left | |
| 4229 | 3862 {nr} (for "lc" only): start matching {nr} chars right of the start |
| 7 | 3863 |
| 3864 Examples: "ms=s+1", "hs=e-2", "lc=3". | |
| 3865 | |
| 3866 Although all offsets are accepted after any pattern, they are not always | |
| 3867 meaningful. This table shows which offsets are actually used: | |
| 3868 | |
| 3869 ms me hs he rs re lc ~ | |
| 3870 match item yes yes yes yes - - yes | |
| 3871 region item start yes - yes - yes - yes | |
| 3872 region item skip - yes - - - - yes | |
| 3873 region item end - yes - yes - yes yes | |
| 3874 | |
| 3875 Offsets can be concatenated, with a ',' in between. Example: > | |
| 3876 :syn match String /"[^"]*"/hs=s+1,he=e-1 | |
| 3877 < | |
| 3878 some "string" text | |
| 3879 ^^^^^^ highlighted | |
| 3880 | |
| 3881 Notes: | |
| 3882 - There must be no white space between the pattern and the character | |
| 3883 offset(s). | |
| 3884 - The highlighted area will never be outside of the matched text. | |
| 3885 - A negative offset for an end pattern may not always work, because the end | |
| 3886 pattern may be detected when the highlighting should already have stopped. | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
3887 - Before Vim 7.2 the offsets were counted in bytes instead of characters. |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
3888 This didn't work well for multi-byte characters, so it was changed with the |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
3889 Vim 7.2 release. |
| 7 | 3890 - The start of a match cannot be in a line other than where the pattern |
| 3891 matched. This doesn't work: "a\nb"ms=e. You can make the highlighting | |
| 3892 start in another line, this does work: "a\nb"hs=e. | |
| 3893 | |
| 3894 Example (match a comment but don't highlight the /* and */): > | |
| 3895 :syntax region Comment start="/\*"hs=e+1 end="\*/"he=s-1 | |
| 3896 < | |
| 3897 /* this is a comment */ | |
| 3898 ^^^^^^^^^^^^^^^^^^^ highlighted | |
| 3899 | |
| 3900 A more complicated Example: > | |
| 3901 :syn region Exa matchgroup=Foo start="foo"hs=s+2,rs=e+2 matchgroup=Bar end="bar"me=e-1,he=e-1,re=s-1 | |
| 3902 < | |
| 3903 abcfoostringbarabc | |
| 3904 mmmmmmmmmmm match | |
| 625 | 3905 sssrrreee highlight start/region/end ("Foo", "Exa" and "Bar") |
| 7 | 3906 |
| 3907 Leading context *:syn-lc* *:syn-leading* *:syn-context* | |
| 3908 | |
| 3909 Note: This is an obsolete feature, only included for backwards compatibility | |
| 3910 with previous Vim versions. It's now recommended to use the |/\@<=| construct | |
| 3911 in the pattern. | |
| 3912 | |
| 3913 The "lc" offset specifies leading context -- a part of the pattern that must | |
| 3914 be present, but is not considered part of the match. An offset of "lc=n" will | |
| 3915 cause Vim to step back n columns before attempting the pattern match, allowing | |
| 3916 characters which have already been matched in previous patterns to also be | |
| 3917 used as leading context for this match. This can be used, for instance, to | |
| 3918 specify that an "escaping" character must not precede the match: > | |
| 3919 | |
| 3920 :syn match ZNoBackslash "[^\\]z"ms=s+1 | |
| 3921 :syn match WNoBackslash "[^\\]w"lc=1 | |
| 3922 :syn match Underline "_\+" | |
| 3923 < | |
| 3924 ___zzzz ___wwww | |
| 3925 ^^^ ^^^ matches Underline | |
| 3926 ^ ^ matches ZNoBackslash | |
| 3927 ^^^^ matches WNoBackslash | |
| 3928 | |
| 3929 The "ms" offset is automatically set to the same value as the "lc" offset, | |
| 3930 unless you set "ms" explicitly. | |
| 3931 | |
| 3932 | |
| 3933 Multi-line patterns *:syn-multi-line* | |
| 3934 | |
| 3935 The patterns can include "\n" to match an end-of-line. Mostly this works as | |
| 3936 expected, but there are a few exceptions. | |
| 3937 | |
| 3938 When using a start pattern with an offset, the start of the match is not | |
| 3939 allowed to start in a following line. The highlighting can start in a | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
3940 following line though. Using the "\zs" item also requires that the start of |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
3941 the match doesn't move to another line. |
| 7 | 3942 |
| 3943 The skip pattern can include the "\n", but the search for an end pattern will | |
| 3944 continue in the first character of the next line, also when that character is | |
| 3945 matched by the skip pattern. This is because redrawing may start in any line | |
| 3946 halfway a region and there is no check if the skip pattern started in a | |
| 3947 previous line. For example, if the skip pattern is "a\nb" and an end pattern | |
| 3948 is "b", the end pattern does match in the second line of this: > | |
| 3949 x x a | |
| 3950 b x x | |
| 3951 Generally this means that the skip pattern should not match any characters | |
| 3952 after the "\n". | |
| 3953 | |
| 3954 | |
| 3955 External matches *:syn-ext-match* | |
| 3956 | |
| 3957 These extra regular expression items are available in region patterns: | |
| 3958 | |
| 3959 */\z(* */\z(\)* *E50* *E52* | |
| 4073 | 3960 \z(\) Marks the sub-expression as "external", meaning that it can be |
| 3961 accessed from another pattern match. Currently only usable in | |
| 3962 defining a syntax region start pattern. | |
| 7 | 3963 |
| 3964 */\z1* */\z2* */\z3* */\z4* */\z5* | |
| 3965 \z1 ... \z9 */\z6* */\z7* */\z8* */\z9* *E66* *E67* | |
| 3966 Matches the same string that was matched by the corresponding | |
| 3967 sub-expression in a previous start pattern match. | |
| 3968 | |
| 3969 Sometimes the start and end patterns of a region need to share a common | |
| 3970 sub-expression. A common example is the "here" document in Perl and many Unix | |
| 3971 shells. This effect can be achieved with the "\z" special regular expression | |
| 3972 items, which marks a sub-expression as "external", in the sense that it can be | |
| 3973 referenced from outside the pattern in which it is defined. The here-document | |
| 3974 example, for instance, can be done like this: > | |
| 3975 :syn region hereDoc start="<<\z(\I\i*\)" end="^\z1$" | |
| 3976 | |
| 3977 As can be seen here, the \z actually does double duty. In the start pattern, | |
| 3978 it marks the "\(\I\i*\)" sub-expression as external; in the end pattern, it | |
| 3979 changes the \1 back-reference into an external reference referring to the | |
| 3980 first external sub-expression in the start pattern. External references can | |
| 3981 also be used in skip patterns: > | |
| 3982 :syn region foo start="start \(\I\i*\)" skip="not end \z1" end="end \z1" | |
| 3983 | |
| 3984 Note that normal and external sub-expressions are completely orthogonal and | |
| 3985 indexed separately; for instance, if the pattern "\z(..\)\(..\)" is applied | |
| 3986 to the string "aabb", then \1 will refer to "bb" and \z1 will refer to "aa". | |
| 3987 Note also that external sub-expressions cannot be accessed as back-references | |
| 3988 within the same pattern like normal sub-expressions. If you want to use one | |
| 3989 sub-expression as both a normal and an external sub-expression, you can nest | |
| 3990 the two, as in "\(\z(...\)\)". | |
| 3991 | |
| 3992 Note that only matches within a single line can be used. Multi-line matches | |
| 3993 cannot be referred to. | |
| 3994 | |
| 3995 ============================================================================== | |
| 3996 8. Syntax clusters *:syn-cluster* *E400* | |
| 3997 | |
| 3998 :sy[ntax] cluster {cluster-name} [contains={group-name}..] | |
| 3999 [add={group-name}..] | |
| 4000 [remove={group-name}..] | |
| 4001 | |
| 4002 This command allows you to cluster a list of syntax groups together under a | |
| 4003 single name. | |
| 4004 | |
| 4005 contains={group-name}.. | |
| 4006 The cluster is set to the specified list of groups. | |
| 4007 add={group-name}.. | |
| 4008 The specified groups are added to the cluster. | |
| 4009 remove={group-name}.. | |
| 4010 The specified groups are removed from the cluster. | |
| 4011 | |
| 1624 | 4012 A cluster so defined may be referred to in a contains=.., containedin=.., |
| 4013 nextgroup=.., add=.. or remove=.. list with a "@" prefix. You can also use | |
| 4014 this notation to implicitly declare a cluster before specifying its contents. | |
| 7 | 4015 |
| 4016 Example: > | |
| 4017 :syntax match Thing "# [^#]\+ #" contains=@ThingMembers | |
| 4018 :syntax cluster ThingMembers contains=ThingMember1,ThingMember2 | |
| 4019 | |
| 4020 As the previous example suggests, modifications to a cluster are effectively | |
| 4021 retroactive; the membership of the cluster is checked at the last minute, so | |
| 4022 to speak: > | |
| 4023 :syntax keyword A aaa | |
| 4024 :syntax keyword B bbb | |
| 4025 :syntax cluster AandB contains=A | |
| 4026 :syntax match Stuff "( aaa bbb )" contains=@AandB | |
| 4027 :syntax cluster AandB add=B " now both keywords are matched in Stuff | |
| 4028 | |
| 4029 This also has implications for nested clusters: > | |
| 4030 :syntax keyword A aaa | |
| 4031 :syntax keyword B bbb | |
| 4032 :syntax cluster SmallGroup contains=B | |
| 4033 :syntax cluster BigGroup contains=A,@SmallGroup | |
| 4034 :syntax match Stuff "( aaa bbb )" contains=@BigGroup | |
| 4035 :syntax cluster BigGroup remove=B " no effect, since B isn't in BigGroup | |
| 4036 :syntax cluster SmallGroup remove=B " now bbb isn't matched within Stuff | |
| 2751 | 4037 < |
| 4038 *E848* | |
| 4039 The maximum number of clusters is 9767. | |
| 7 | 4040 |
| 4041 ============================================================================== | |
| 4042 9. Including syntax files *:syn-include* *E397* | |
| 4043 | |
| 4044 It is often useful for one language's syntax file to include a syntax file for | |
| 4045 a related language. Depending on the exact relationship, this can be done in | |
| 4046 two different ways: | |
| 4047 | |
| 4048 - If top-level syntax items in the included syntax file are to be | |
| 4049 allowed at the top level in the including syntax, you can simply use | |
| 4050 the |:runtime| command: > | |
| 4051 | |
| 4052 " In cpp.vim: | |
| 4053 :runtime! syntax/c.vim | |
| 4054 :unlet b:current_syntax | |
| 4055 | |
| 4056 < - If top-level syntax items in the included syntax file are to be | |
| 4057 contained within a region in the including syntax, you can use the | |
| 4058 ":syntax include" command: | |
| 4059 | |
| 4060 :sy[ntax] include [@{grouplist-name}] {file-name} | |
| 4061 | |
| 4062 All syntax items declared in the included file will have the | |
| 4063 "contained" flag added. In addition, if a group list is specified, | |
| 4064 all top-level syntax items in the included file will be added to | |
| 4065 that list. > | |
| 4066 | |
| 4067 " In perl.vim: | |
| 4068 :syntax include @Pod <sfile>:p:h/pod.vim | |
| 4069 :syntax region perlPOD start="^=head" end="^=cut" contains=@Pod | |
| 4070 < | |
| 4071 When {file-name} is an absolute path (starts with "/", "c:", "$VAR" | |
| 4072 or "<sfile>") that file is sourced. When it is a relative path | |
| 4073 (e.g., "syntax/pod.vim") the file is searched for in 'runtimepath'. | |
| 4074 All matching files are loaded. Using a relative path is | |
| 4075 recommended, because it allows a user to replace the included file | |
| 4076 with his own version, without replacing the file that does the ":syn | |
| 4077 include". | |
| 4078 | |
| 2751 | 4079 *E847* |
| 4080 The maximum number of includes is 999. | |
| 4081 | |
| 7 | 4082 ============================================================================== |
| 4083 10. Synchronizing *:syn-sync* *E403* *E404* | |
| 4084 | |
| 4085 Vim wants to be able to start redrawing in any position in the document. To | |
| 4086 make this possible it needs to know the syntax state at the position where | |
| 4087 redrawing starts. | |
| 4088 | |
| 4089 :sy[ntax] sync [ccomment [group-name] | minlines={N} | ...] | |
| 4090 | |
| 4091 There are four ways to synchronize: | |
| 4092 1. Always parse from the start of the file. | |
| 4093 |:syn-sync-first| | |
| 4094 2. Based on C-style comments. Vim understands how C-comments work and can | |
| 4095 figure out if the current line starts inside or outside a comment. | |
| 4096 |:syn-sync-second| | |
| 4097 3. Jumping back a certain number of lines and start parsing there. | |
| 4098 |:syn-sync-third| | |
| 4099 4. Searching backwards in the text for a pattern to sync on. | |
| 4100 |:syn-sync-fourth| | |
| 4101 | |
| 4102 *:syn-sync-maxlines* *:syn-sync-minlines* | |
| 4103 For the last three methods, the line range where the parsing can start is | |
| 4104 limited by "minlines" and "maxlines". | |
| 4105 | |
| 4106 If the "minlines={N}" argument is given, the parsing always starts at least | |
| 4107 that many lines backwards. This can be used if the parsing may take a few | |
| 4108 lines before it's correct, or when it's not possible to use syncing. | |
| 4109 | |
| 4110 If the "maxlines={N}" argument is given, the number of lines that are searched | |
| 4111 for a comment or syncing pattern is restricted to N lines backwards (after | |
| 4112 adding "minlines"). This is useful if you have few things to sync on and a | |
| 4113 slow machine. Example: > | |
| 4114 :syntax sync ccomment maxlines=500 | |
| 4115 < | |
| 4116 *:syn-sync-linebreaks* | |
| 4117 When using a pattern that matches multiple lines, a change in one line may | |
| 4118 cause a pattern to no longer match in a previous line. This means has to | |
| 4119 start above where the change was made. How many lines can be specified with | |
| 4120 the "linebreaks" argument. For example, when a pattern may include one line | |
| 4121 break use this: > | |
| 4122 :syntax sync linebreaks=1 | |
| 4123 The result is that redrawing always starts at least one line before where a | |
| 4124 change was made. The default value for "linebreaks" is zero. Usually the | |
| 4125 value for "minlines" is bigger than "linebreaks". | |
| 4126 | |
| 4127 | |
| 4128 First syncing method: *:syn-sync-first* | |
| 4129 > | |
| 4130 :syntax sync fromstart | |
| 4131 | |
| 4132 The file will be parsed from the start. This makes syntax highlighting | |
| 4133 accurate, but can be slow for long files. Vim caches previously parsed text, | |
| 4134 so that it's only slow when parsing the text for the first time. However, | |
| 3224 | 4135 when making changes some part of the text needs to be parsed again (worst |
| 7 | 4136 case: to the end of the file). |
| 4137 | |
| 4138 Using "fromstart" is equivalent to using "minlines" with a very large number. | |
| 4139 | |
| 4140 | |
| 4141 Second syncing method: *:syn-sync-second* *:syn-sync-ccomment* | |
| 4142 | |
| 4143 For the second method, only the "ccomment" argument needs to be given. | |
| 4144 Example: > | |
| 4145 :syntax sync ccomment | |
| 4146 | |
| 4147 When Vim finds that the line where displaying starts is inside a C-style | |
| 4148 comment, the last region syntax item with the group-name "Comment" will be | |
| 4149 used. This requires that there is a region with the group-name "Comment"! | |
| 4150 An alternate group name can be specified, for example: > | |
| 4151 :syntax sync ccomment javaComment | |
| 4152 This means that the last item specified with "syn region javaComment" will be | |
| 4153 used for the detected C comment region. This only works properly if that | |
| 4154 region does have a start pattern "\/*" and an end pattern "*\/". | |
| 4155 | |
| 4156 The "maxlines" argument can be used to restrict the search to a number of | |
| 4157 lines. The "minlines" argument can be used to at least start a number of | |
| 4158 lines back (e.g., for when there is some construct that only takes a few | |
| 4159 lines, but it hard to sync on). | |
| 4160 | |
| 4161 Note: Syncing on a C comment doesn't work properly when strings are used | |
| 4162 that cross a line and contain a "*/". Since letting strings cross a line | |
| 4163 is a bad programming habit (many compilers give a warning message), and the | |
| 4164 chance of a "*/" appearing inside a comment is very small, this restriction | |
| 4165 is hardly ever noticed. | |
| 4166 | |
| 4167 | |
| 4168 Third syncing method: *:syn-sync-third* | |
| 4169 | |
| 4170 For the third method, only the "minlines={N}" argument needs to be given. | |
| 4171 Vim will subtract {N} from the line number and start parsing there. This | |
| 4172 means {N} extra lines need to be parsed, which makes this method a bit slower. | |
| 4173 Example: > | |
| 4174 :syntax sync minlines=50 | |
| 4175 | |
| 4176 "lines" is equivalent to "minlines" (used by older versions). | |
| 4177 | |
| 4178 | |
| 4179 Fourth syncing method: *:syn-sync-fourth* | |
| 4180 | |
| 4181 The idea is to synchronize on the end of a few specific regions, called a | |
| 4182 sync pattern. Only regions can cross lines, so when we find the end of some | |
| 4183 region, we might be able to know in which syntax item we are. The search | |
| 4184 starts in the line just above the one where redrawing starts. From there | |
| 4185 the search continues backwards in the file. | |
| 4186 | |
| 4187 This works just like the non-syncing syntax items. You can use contained | |
| 4188 matches, nextgroup, etc. But there are a few differences: | |
| 4189 - Keywords cannot be used. | |
| 4190 - The syntax items with the "sync" keyword form a completely separated group | |
| 4191 of syntax items. You can't mix syncing groups and non-syncing groups. | |
| 4192 - The matching works backwards in the buffer (line by line), instead of | |
| 4193 forwards. | |
| 4194 - A line continuation pattern can be given. It is used to decide which group | |
| 4195 of lines need to be searched like they were one line. This means that the | |
| 4196 search for a match with the specified items starts in the first of the | |
| 4197 consecutive that contain the continuation pattern. | |
| 4198 - When using "nextgroup" or "contains", this only works within one line (or | |
| 4199 group of continued lines). | |
| 4200 - When using a region, it must start and end in the same line (or group of | |
| 4201 continued lines). Otherwise the end is assumed to be at the end of the | |
| 4202 line (or group of continued lines). | |
| 4203 - When a match with a sync pattern is found, the rest of the line (or group of | |
| 4204 continued lines) is searched for another match. The last match is used. | |
| 4205 This is used when a line can contain both the start end the end of a region | |
| 4206 (e.g., in a C-comment like /* this */, the last "*/" is used). | |
| 4207 | |
| 4208 There are two ways how a match with a sync pattern can be used: | |
| 4209 1. Parsing for highlighting starts where redrawing starts (and where the | |
| 4210 search for the sync pattern started). The syntax group that is expected | |
| 4211 to be valid there must be specified. This works well when the regions | |
| 4212 that cross lines cannot contain other regions. | |
| 4213 2. Parsing for highlighting continues just after the match. The syntax group | |
| 4214 that is expected to be present just after the match must be specified. | |
| 4215 This can be used when the previous method doesn't work well. It's much | |
| 4216 slower, because more text needs to be parsed. | |
| 4217 Both types of sync patterns can be used at the same time. | |
| 4218 | |
| 4219 Besides the sync patterns, other matches and regions can be specified, to | |
| 4220 avoid finding unwanted matches. | |
| 4221 | |
| 4222 [The reason that the sync patterns are given separately, is that mostly the | |
| 4223 search for the sync point can be much simpler than figuring out the | |
| 4224 highlighting. The reduced number of patterns means it will go (much) | |
| 4225 faster.] | |
| 4226 | |
| 4227 *syn-sync-grouphere* *E393* *E394* | |
| 4228 :syntax sync match {sync-group-name} grouphere {group-name} "pattern" .. | |
| 4229 | |
| 4230 Define a match that is used for syncing. {group-name} is the | |
| 4231 name of a syntax group that follows just after the match. Parsing | |
| 4232 of the text for highlighting starts just after the match. A region | |
| 4233 must exist for this {group-name}. The first one defined will be used. | |
| 4234 "NONE" can be used for when there is no syntax group after the match. | |
| 4235 | |
| 4236 *syn-sync-groupthere* | |
| 4237 :syntax sync match {sync-group-name} groupthere {group-name} "pattern" .. | |
| 4238 | |
| 4239 Like "grouphere", but {group-name} is the name of a syntax group that | |
| 4240 is to be used at the start of the line where searching for the sync | |
| 4241 point started. The text between the match and the start of the sync | |
| 4242 pattern searching is assumed not to change the syntax highlighting. | |
| 4243 For example, in C you could search backwards for "/*" and "*/". If | |
| 4244 "/*" is found first, you know that you are inside a comment, so the | |
| 4245 "groupthere" is "cComment". If "*/" is found first, you know that you | |
| 4246 are not in a comment, so the "groupthere" is "NONE". (in practice | |
| 4247 it's a bit more complicated, because the "/*" and "*/" could appear | |
| 4248 inside a string. That's left as an exercise to the reader...). | |
| 4249 | |
| 4250 :syntax sync match .. | |
| 4251 :syntax sync region .. | |
| 4252 | |
| 4253 Without a "groupthere" argument. Define a region or match that is | |
| 4254 skipped while searching for a sync point. | |
| 4255 | |
| 856 | 4256 *syn-sync-linecont* |
| 7 | 4257 :syntax sync linecont {pattern} |
| 4258 | |
| 4259 When {pattern} matches in a line, it is considered to continue in | |
| 4260 the next line. This means that the search for a sync point will | |
| 4261 consider the lines to be concatenated. | |
| 4262 | |
| 4263 If the "maxlines={N}" argument is given too, the number of lines that are | |
| 4264 searched for a match is restricted to N. This is useful if you have very | |
| 4265 few things to sync on and a slow machine. Example: > | |
| 4266 :syntax sync maxlines=100 | |
| 4267 | |
| 4268 You can clear all sync settings with: > | |
| 4269 :syntax sync clear | |
| 4270 | |
| 4271 You can clear specific sync patterns with: > | |
| 4272 :syntax sync clear {sync-group-name} .. | |
| 4273 | |
| 4274 ============================================================================== | |
| 4275 11. Listing syntax items *:syntax* *:sy* *:syn* *:syn-list* | |
| 4276 | |
| 534 | 4277 This command lists all the syntax items: > |
| 7 | 4278 |
| 4279 :sy[ntax] [list] | |
| 4280 | |
| 4281 To show the syntax items for one syntax group: > | |
| 4282 | |
| 4283 :sy[ntax] list {group-name} | |
| 4284 | |
| 2581 | 4285 To list the syntax groups in one cluster: *E392* > |
| 7 | 4286 |
| 4287 :sy[ntax] list @{cluster-name} | |
| 4288 | |
| 4289 See above for other arguments for the ":syntax" command. | |
| 4290 | |
| 4291 Note that the ":syntax" command can be abbreviated to ":sy", although ":syn" | |
| 4292 is mostly used, because it looks better. | |
| 4293 | |
| 4294 ============================================================================== | |
| 4295 12. Highlight command *:highlight* *:hi* *E28* *E411* *E415* | |
| 4296 | |
| 4297 There are three types of highlight groups: | |
| 4298 - The ones used for specific languages. For these the name starts with the | |
| 4299 name of the language. Many of these don't have any attributes, but are | |
| 4300 linked to a group of the second type. | |
| 4301 - The ones used for all syntax languages. | |
| 4302 - The ones used for the 'highlight' option. | |
| 4303 *hitest.vim* | |
| 4304 You can see all the groups currently active with this command: > | |
| 4305 :so $VIMRUNTIME/syntax/hitest.vim | |
| 4306 This will open a new window containing all highlight group names, displayed | |
| 4307 in their own color. | |
| 4308 | |
| 4309 *:colo* *:colorscheme* *E185* | |
| 2152 | 4310 :colo[rscheme] Output the name of the currently active color scheme. |
| 4311 This is basically the same as > | |
| 4312 :echo g:colors_name | |
| 4313 < In case g:colors_name has not been defined :colo will | |
| 4314 output "default". When compiled without the |+eval| | |
| 4315 feature it will output "unknown". | |
| 4316 | |
| 7 | 4317 :colo[rscheme] {name} Load color scheme {name}. This searches 'runtimepath' |
| 4318 for the file "colors/{name}.vim. The first one that | |
| 4319 is found is loaded. | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
4320 To see the name of the currently active color scheme: > |
| 2152 | 4321 :colo |
| 4322 < The name is also stored in the g:colors_name variable. | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
4323 Doesn't work recursively, thus you can't use |
| 7 | 4324 ":colorscheme" in a color scheme script. |
| 12 | 4325 After the color scheme has been loaded the |
| 4326 |ColorScheme| autocommand event is triggered. | |
| 22 | 4327 For info about writing a colorscheme file: > |
| 4328 :edit $VIMRUNTIME/colors/README.txt | |
| 7 | 4329 |
| 4330 :hi[ghlight] List all the current highlight groups that have | |
| 4331 attributes set. | |
| 4332 | |
| 4333 :hi[ghlight] {group-name} | |
| 4334 List one highlight group. | |
| 4335 | |
| 4336 :hi[ghlight] clear Reset all highlighting to the defaults. Removes all | |
| 4337 highlighting for groups added by the user! | |
| 4338 Uses the current value of 'background' to decide which | |
| 4339 default colors to use. | |
| 4340 | |
| 4341 :hi[ghlight] clear {group-name} | |
| 4342 :hi[ghlight] {group-name} NONE | |
| 4343 Disable the highlighting for one highlight group. It | |
| 4344 is _not_ set back to the default colors. | |
| 4345 | |
| 4346 :hi[ghlight] [default] {group-name} {key}={arg} .. | |
| 4347 Add a highlight group, or change the highlighting for | |
| 4348 an existing group. | |
| 4349 See |highlight-args| for the {key}={arg} arguments. | |
| 4350 See |:highlight-default| for the optional [default] | |
| 4351 argument. | |
| 4352 | |
| 4353 Normally a highlight group is added once when starting up. This sets the | |
| 4354 default values for the highlighting. After that, you can use additional | |
| 4355 highlight commands to change the arguments that you want to set to non-default | |
| 4356 values. The value "NONE" can be used to switch the value off or go back to | |
| 4357 the default value. | |
| 4358 | |
| 4359 A simple way to change colors is with the |:colorscheme| command. This loads | |
| 4360 a file with ":highlight" commands such as this: > | |
| 4361 | |
| 4362 :hi Comment gui=bold | |
| 4363 | |
| 4364 Note that all settings that are not included remain the same, only the | |
| 4365 specified field is used, and settings are merged with previous ones. So, the | |
| 4366 result is like this single command has been used: > | |
| 4367 :hi Comment term=bold ctermfg=Cyan guifg=#80a0ff gui=bold | |
| 4368 < | |
| 856 | 4369 *:highlight-verbose* |
| 448 | 4370 When listing a highlight group and 'verbose' is non-zero, the listing will |
| 4371 also tell where it was last set. Example: > | |
| 4372 :verbose hi Comment | |
| 4373 < Comment xxx term=bold ctermfg=4 guifg=Blue ~ | |
| 856 | 4374 Last set from /home/mool/vim/vim7/runtime/syntax/syncolor.vim ~ |
| 448 | 4375 |
| 484 | 4376 When ":hi clear" is used then the script where this command is used will be |
| 4377 mentioned for the default values. See |:verbose-cmd| for more information. | |
| 448 | 4378 |
| 7 | 4379 *highlight-args* *E416* *E417* *E423* |
| 4380 There are three types of terminals for highlighting: | |
| 4381 term a normal terminal (vt100, xterm) | |
| 4382 cterm a color terminal (MS-DOS console, color-xterm, these have the "Co" | |
| 4383 termcap entry) | |
| 4384 gui the GUI | |
| 4385 | |
| 4386 For each type the highlighting can be given. This makes it possible to use | |
| 4387 the same syntax file on all terminals, and use the optimal highlighting. | |
| 4388 | |
| 4389 1. highlight arguments for normal terminals | |
| 4390 | |
| 301 | 4391 *bold* *underline* *undercurl* |
| 4392 *inverse* *italic* *standout* | |
| 7 | 4393 term={attr-list} *attr-list* *highlight-term* *E418* |
| 4394 attr-list is a comma separated list (without spaces) of the | |
| 4395 following items (in any order): | |
| 4396 bold | |
| 4397 underline | |
| 217 | 4398 undercurl not always available |
| 7 | 4399 reverse |
| 4400 inverse same as reverse | |
| 4401 italic | |
| 4402 standout | |
| 4403 NONE no attributes used (used to reset it) | |
| 4404 | |
| 4405 Note that "bold" can be used here and by using a bold font. They | |
| 4406 have the same effect. | |
| 217 | 4407 "undercurl" is a curly underline. When "undercurl" is not possible |
| 4408 then "underline" is used. In general "undercurl" is only available in | |
| 819 | 4409 the GUI. The color is set with |highlight-guisp|. |
| 7 | 4410 |
| 4411 start={term-list} *highlight-start* *E422* | |
| 4412 stop={term-list} *term-list* *highlight-stop* | |
| 4413 These lists of terminal codes can be used to get | |
| 4414 non-standard attributes on a terminal. | |
| 4415 | |
| 4416 The escape sequence specified with the "start" argument | |
| 4417 is written before the characters in the highlighted | |
| 4418 area. It can be anything that you want to send to the | |
| 4419 terminal to highlight this area. The escape sequence | |
| 4420 specified with the "stop" argument is written after the | |
| 4421 highlighted area. This should undo the "start" argument. | |
| 4422 Otherwise the screen will look messed up. | |
| 4423 | |
| 4424 The {term-list} can have two forms: | |
| 4425 | |
| 4426 1. A string with escape sequences. | |
| 4427 This is any string of characters, except that it can't start with | |
| 4428 "t_" and blanks are not allowed. The <> notation is recognized | |
| 4429 here, so you can use things like "<Esc>" and "<Space>". Example: | |
| 4430 start=<Esc>[27h;<Esc>[<Space>r; | |
| 4431 | |
| 4432 2. A list of terminal codes. | |
| 4433 Each terminal code has the form "t_xx", where "xx" is the name of | |
| 4434 the termcap entry. The codes have to be separated with commas. | |
| 4435 White space is not allowed. Example: | |
| 4436 start=t_C1,t_BL | |
| 4437 The terminal codes must exist for this to work. | |
| 4438 | |
| 4439 | |
| 4440 2. highlight arguments for color terminals | |
| 4441 | |
| 4442 cterm={attr-list} *highlight-cterm* | |
| 4443 See above for the description of {attr-list} |attr-list|. | |
| 4444 The "cterm" argument is likely to be different from "term", when | |
| 4445 colors are used. For example, in a normal terminal comments could | |
| 4446 be underlined, in a color terminal they can be made Blue. | |
| 4447 Note: Many terminals (e.g., DOS console) can't mix these attributes | |
| 4448 with coloring. Use only one of "cterm=" OR "ctermfg=" OR "ctermbg=". | |
| 4449 | |
| 4450 ctermfg={color-nr} *highlight-ctermfg* *E421* | |
| 4451 ctermbg={color-nr} *highlight-ctermbg* | |
| 4452 The {color-nr} argument is a color number. Its range is zero to | |
| 4453 (not including) the number given by the termcap entry "Co". | |
| 4454 The actual color with this number depends on the type of terminal | |
| 4455 and its settings. Sometimes the color also depends on the settings of | |
| 4456 "cterm". For example, on some systems "cterm=bold ctermfg=3" gives | |
| 4457 another color, on others you just get color 3. | |
| 4458 | |
| 4459 For an xterm this depends on your resources, and is a bit | |
| 4460 unpredictable. See your xterm documentation for the defaults. The | |
| 4461 colors for a color-xterm can be changed from the .Xdefaults file. | |
| 4462 Unfortunately this means that it's not possible to get the same colors | |
| 4463 for each user. See |xterm-color| for info about color xterms. | |
| 4464 | |
| 4465 The MSDOS standard colors are fixed (in a console window), so these | |
| 4466 have been used for the names. But the meaning of color names in X11 | |
| 4467 are fixed, so these color settings have been used, to make the | |
| 4468 highlighting settings portable (complicated, isn't it?). The | |
| 4469 following names are recognized, with the color number used: | |
| 4470 | |
| 4471 *cterm-colors* | |
| 4472 NR-16 NR-8 COLOR NAME ~ | |
| 4473 0 0 Black | |
| 4474 1 4 DarkBlue | |
| 4475 2 2 DarkGreen | |
| 4476 3 6 DarkCyan | |
| 4477 4 1 DarkRed | |
| 4478 5 5 DarkMagenta | |
| 4479 6 3 Brown, DarkYellow | |
| 4480 7 7 LightGray, LightGrey, Gray, Grey | |
| 4481 8 0* DarkGray, DarkGrey | |
| 4482 9 4* Blue, LightBlue | |
| 4483 10 2* Green, LightGreen | |
| 4484 11 6* Cyan, LightCyan | |
| 4485 12 1* Red, LightRed | |
| 4486 13 5* Magenta, LightMagenta | |
| 4487 14 3* Yellow, LightYellow | |
| 4488 15 7* White | |
| 4489 | |
| 4490 The number under "NR-16" is used for 16-color terminals ('t_Co' | |
| 4491 greater than or equal to 16). The number under "NR-8" is used for | |
| 4492 8-color terminals ('t_Co' less than 16). The '*' indicates that the | |
| 4493 bold attribute is set for ctermfg. In many 8-color terminals (e.g., | |
| 4494 "linux"), this causes the bright colors to appear. This doesn't work | |
| 4495 for background colors! Without the '*' the bold attribute is removed. | |
| 4496 If you want to set the bold attribute in a different way, put a | |
| 4497 "cterm=" argument AFTER the "ctermfg=" or "ctermbg=" argument. Or use | |
| 4498 a number instead of a color name. | |
| 4499 | |
| 4500 The case of the color names is ignored. | |
| 4501 Note that for 16 color ansi style terminals (including xterms), the | |
| 237 | 4502 numbers in the NR-8 column is used. Here '*' means 'add 8' so that Blue |
| 7 | 4503 is 12, DarkGray is 8 etc. |
| 4504 | |
| 4505 Note that for some color terminals these names may result in the wrong | |
| 4506 colors! | |
| 4507 | |
| 4508 *:hi-normal-cterm* | |
| 4509 When setting the "ctermfg" or "ctermbg" colors for the Normal group, | |
| 4510 these will become the colors used for the non-highlighted text. | |
| 4511 Example: > | |
| 4512 :highlight Normal ctermfg=grey ctermbg=darkblue | |
| 4513 < When setting the "ctermbg" color for the Normal group, the | |
| 4514 'background' option will be adjusted automatically. This causes the | |
| 4515 highlight groups that depend on 'background' to change! This means | |
| 4516 you should set the colors for Normal first, before setting other | |
| 4517 colors. | |
| 4518 When a colorscheme is being used, changing 'background' causes it to | |
| 4519 be reloaded, which may reset all colors (including Normal). First | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
4520 delete the "g:colors_name" variable when you don't want this. |
| 7 | 4521 |
| 4522 When you have set "ctermfg" or "ctermbg" for the Normal group, Vim | |
| 4523 needs to reset the color when exiting. This is done with the "op" | |
| 4524 termcap entry |t_op|. If this doesn't work correctly, try setting the | |
| 4525 't_op' option in your .vimrc. | |
| 4526 *E419* *E420* | |
| 4527 When Vim knows the normal foreground and background colors, "fg" and | |
| 4528 "bg" can be used as color names. This only works after setting the | |
| 4529 colors for the Normal group and for the MS-DOS console. Example, for | |
| 4530 reverse video: > | |
| 4531 :highlight Visual ctermfg=bg ctermbg=fg | |
| 4532 < Note that the colors are used that are valid at the moment this | |
| 4533 command are given. If the Normal group colors are changed later, the | |
| 4534 "fg" and "bg" colors will not be adjusted. | |
| 4535 | |
| 4536 | |
| 4537 3. highlight arguments for the GUI | |
| 4538 | |
| 4539 gui={attr-list} *highlight-gui* | |
| 4540 These give the attributes to use in the GUI mode. | |
| 4541 See |attr-list| for a description. | |
| 4542 Note that "bold" can be used here and by using a bold font. They | |
| 4543 have the same effect. | |
| 4544 Note that the attributes are ignored for the "Normal" group. | |
| 4545 | |
| 4546 font={font-name} *highlight-font* | |
| 4547 font-name is the name of a font, as it is used on the system Vim | |
| 4548 runs on. For X11 this is a complicated name, for example: > | |
| 4549 font=-misc-fixed-bold-r-normal--14-130-75-75-c-70-iso8859-1 | |
| 4550 < | |
| 4551 The font-name "NONE" can be used to revert to the default font. | |
| 4552 When setting the font for the "Normal" group, this becomes the default | |
| 4553 font (until the 'guifont' option is changed; the last one set is | |
| 4554 used). | |
| 4555 The following only works with Motif and Athena, not with other GUIs: | |
| 4556 When setting the font for the "Menu" group, the menus will be changed. | |
| 4557 When setting the font for the "Tooltip" group, the tooltips will be | |
| 4558 changed. | |
| 4559 All fonts used, except for Menu and Tooltip, should be of the same | |
| 4560 character size as the default font! Otherwise redrawing problems will | |
| 4561 occur. | |
| 4562 | |
| 4563 guifg={color-name} *highlight-guifg* | |
| 4564 guibg={color-name} *highlight-guibg* | |
| 217 | 4565 guisp={color-name} *highlight-guisp* |
| 4566 These give the foreground (guifg), background (guibg) and special | |
| 642 | 4567 (guisp) color to use in the GUI. "guisp" is used for undercurl. |
| 4568 There are a few special names: | |
| 7 | 4569 NONE no color (transparent) |
| 4570 bg use normal background color | |
| 4571 background use normal background color | |
| 4572 fg use normal foreground color | |
| 4573 foreground use normal foreground color | |
| 4574 To use a color name with an embedded space or other special character, | |
| 4575 put it in single quotes. The single quote cannot be used then. | |
| 4576 Example: > | |
| 4577 :hi comment guifg='salmon pink' | |
| 4578 < | |
| 4579 *gui-colors* | |
| 4580 Suggested color names (these are available on most systems): | |
| 4581 Red LightRed DarkRed | |
| 4582 Green LightGreen DarkGreen SeaGreen | |
| 4583 Blue LightBlue DarkBlue SlateBlue | |
| 4584 Cyan LightCyan DarkCyan | |
| 4585 Magenta LightMagenta DarkMagenta | |
| 4586 Yellow LightYellow Brown DarkYellow | |
| 4587 Gray LightGray DarkGray | |
| 4588 Black White | |
| 4589 Orange Purple Violet | |
| 4590 | |
| 4591 In the Win32 GUI version, additional system colors are available. See | |
| 4592 |win32-colors|. | |
| 4593 | |
| 4594 You can also specify a color by its Red, Green and Blue values. | |
| 4595 The format is "#rrggbb", where | |
| 4596 "rr" is the Red value | |
| 217 | 4597 "gg" is the Green value |
| 7 | 4598 "bb" is the Blue value |
| 4599 All values are hexadecimal, range from "00" to "ff". Examples: > | |
| 4600 :highlight Comment guifg=#11f0c3 guibg=#ff00ff | |
| 4601 < | |
| 4602 *highlight-groups* *highlight-default* | |
| 4603 These are the default highlighting groups. These groups are used by the | |
| 4604 'highlight' option default. Note that the highlighting depends on the value | |
| 4605 of 'background'. You can see the current settings with the ":highlight" | |
| 4606 command. | |
|
2314
233eb4412f5d
Added 'colorcolumn' option. Partly by Gregor Uhlenheuer.
Bram Moolenaar <bram@vim.org>
parents:
2304
diff
changeset
|
4607 *hl-ColorColumn* |
|
233eb4412f5d
Added 'colorcolumn' option. Partly by Gregor Uhlenheuer.
Bram Moolenaar <bram@vim.org>
parents:
2304
diff
changeset
|
4608 ColorColumn used for the columns set with 'colorcolumn' |
|
2250
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4609 *hl-Conceal* |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4610 Conceal placeholder characters substituted for concealed |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4611 text (see 'conceallevel') |
| 7 | 4612 *hl-Cursor* |
| 4613 Cursor the character under the cursor | |
| 4614 *hl-CursorIM* | |
| 4615 CursorIM like Cursor, but used when in IME mode |CursorIM| | |
| 746 | 4616 *hl-CursorColumn* |
| 4617 CursorColumn the screen column that the cursor is in when 'cursorcolumn' is | |
| 4618 set | |
| 4619 *hl-CursorLine* | |
| 4620 CursorLine the screen line that the cursor is in when 'cursorline' is | |
| 4621 set | |
| 7 | 4622 *hl-Directory* |
| 4623 Directory directory names (and other special names in listings) | |
| 4624 *hl-DiffAdd* | |
| 4625 DiffAdd diff mode: Added line |diff.txt| | |
| 4626 *hl-DiffChange* | |
| 4627 DiffChange diff mode: Changed line |diff.txt| | |
| 4628 *hl-DiffDelete* | |
| 4629 DiffDelete diff mode: Deleted line |diff.txt| | |
| 4630 *hl-DiffText* | |
| 4631 DiffText diff mode: Changed text within a changed line |diff.txt| | |
| 4632 *hl-ErrorMsg* | |
| 4633 ErrorMsg error messages on the command line | |
| 4634 *hl-VertSplit* | |
| 4635 VertSplit the column separating vertically split windows | |
| 4636 *hl-Folded* | |
| 4637 Folded line used for closed folds | |
| 4638 *hl-FoldColumn* | |
| 4639 FoldColumn 'foldcolumn' | |
| 4640 *hl-SignColumn* | |
| 4641 SignColumn column where |signs| are displayed | |
| 4642 *hl-IncSearch* | |
| 4643 IncSearch 'incsearch' highlighting; also used for the text replaced with | |
| 4644 ":s///c" | |
| 4645 *hl-LineNr* | |
| 699 | 4646 LineNr Line number for ":number" and ":#" commands, and when 'number' |
|
2178
c6f1aa1e9f32
Add 'relativenumber' patch from Markus Heidelberg.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
4647 or 'relativenumber' option is set. |
| 3445 | 4648 *hl-CursorLineNr* |
| 4073 | 4649 CursorLineNr Like LineNr when 'cursorline' or 'relativenumber' is set for |
| 4650 the cursor line. | |
| 699 | 4651 *hl-MatchParen* |
| 4652 MatchParen The character under the cursor or just before it, if it | |
| 4653 is a paired bracket, and its match. |pi_paren.txt| | |
| 4654 | |
| 7 | 4655 *hl-ModeMsg* |
| 4656 ModeMsg 'showmode' message (e.g., "-- INSERT --") | |
| 4657 *hl-MoreMsg* | |
| 4658 MoreMsg |more-prompt| | |
| 4659 *hl-NonText* | |
| 4660 NonText '~' and '@' at the end of the window, characters from | |
| 4661 'showbreak' and other characters that do not really exist in | |
| 4662 the text (e.g., ">" displayed when a double-wide character | |
| 4663 doesn't fit at the end of the line). | |
| 4664 *hl-Normal* | |
| 4665 Normal normal text | |
| 540 | 4666 *hl-Pmenu* |
| 4667 Pmenu Popup menu: normal item. | |
| 4668 *hl-PmenuSel* | |
| 4669 PmenuSel Popup menu: selected item. | |
| 4670 *hl-PmenuSbar* | |
| 4671 PmenuSbar Popup menu: scrollbar. | |
| 4672 *hl-PmenuThumb* | |
| 4673 PmenuThumb Popup menu: Thumb of the scrollbar. | |
| 7 | 4674 *hl-Question* |
| 4675 Question |hit-enter| prompt and yes/no questions | |
| 4676 *hl-Search* | |
| 4677 Search Last search pattern highlighting (see 'hlsearch'). | |
| 4678 Also used for highlighting the current line in the quickfix | |
| 4679 window and similar items that need to stand out. | |
| 4680 *hl-SpecialKey* | |
| 4681 SpecialKey Meta and special keys listed with ":map", also for text used | |
| 4682 to show unprintable characters in the text, 'listchars'. | |
| 4683 Generally: text that is displayed differently from what it | |
| 4684 really is. | |
| 221 | 4685 *hl-SpellBad* |
| 4686 SpellBad Word that is not recognized by the spellchecker. |spell| | |
| 4687 This will be combined with the highlighting used otherwise. | |
| 391 | 4688 *hl-SpellCap* |
| 4689 SpellCap Word that should start with a capital. |spell| | |
| 4690 This will be combined with the highlighting used otherwise. | |
| 221 | 4691 *hl-SpellLocal* |
| 4692 SpellLocal Word that is recognized by the spellchecker as one that is | |
| 4693 used in another region. |spell| | |
| 4694 This will be combined with the highlighting used otherwise. | |
| 4695 *hl-SpellRare* | |
| 4696 SpellRare Word that is recognized by the spellchecker as one that is | |
| 4697 hardly ever used. |spell| | |
| 4698 This will be combined with the highlighting used otherwise. | |
| 7 | 4699 *hl-StatusLine* |
| 4700 StatusLine status line of current window | |
| 4701 *hl-StatusLineNC* | |
| 4702 StatusLineNC status lines of not-current windows | |
| 4703 Note: if this is equal to "StatusLine" Vim will use "^^^" in | |
| 4704 the status line of the current window. | |
| 677 | 4705 *hl-TabLine* |
| 4706 TabLine tab pages line, not active tab page label | |
| 4707 *hl-TabLineFill* | |
| 4708 TabLineFill tab pages line, where there are no labels | |
| 4709 *hl-TabLineSel* | |
| 4710 TabLineSel tab pages line, active tab page label | |
| 7 | 4711 *hl-Title* |
| 4712 Title titles for output from ":set all", ":autocmd" etc. | |
| 4713 *hl-Visual* | |
| 4714 Visual Visual mode selection | |
| 4715 *hl-VisualNOS* | |
| 4716 VisualNOS Visual mode selection when vim is "Not Owning the Selection". | |
| 4717 Only X11 Gui's |gui-x11| and |xterm-clipboard| supports this. | |
| 4718 *hl-WarningMsg* | |
| 4719 WarningMsg warning messages | |
| 4720 *hl-WildMenu* | |
| 4721 WildMenu current match in 'wildmenu' completion | |
| 4722 | |
| 523 | 4723 *hl-User1* *hl-User1..9* *hl-User9* |
| 7 | 4724 The 'statusline' syntax allows the use of 9 different highlights in the |
| 237 | 4725 statusline and ruler (via 'rulerformat'). The names are User1 to User9. |
| 7 | 4726 |
| 1624 | 4727 For the GUI you can use the following groups to set the colors for the menu, |
| 7 | 4728 scrollbars and tooltips. They don't have defaults. This doesn't work for the |
| 4729 Win32 GUI. Only three highlight arguments have any effect here: font, guibg, | |
| 4730 and guifg. | |
| 4731 | |
| 4732 *hl-Menu* | |
| 4733 Menu Current font, background and foreground colors of the menus. | |
| 4734 Also used for the toolbar. | |
| 4735 Applicable highlight arguments: font, guibg, guifg. | |
| 4736 | |
| 4737 NOTE: For Motif and Athena the font argument actually | |
| 4738 specifies a fontset at all times, no matter if 'guifontset' is | |
| 4739 empty, and as such it is tied to the current |:language| when | |
| 4740 set. | |
| 4741 | |
| 4742 *hl-Scrollbar* | |
| 4743 Scrollbar Current background and foreground of the main window's | |
| 4744 scrollbars. | |
| 4745 Applicable highlight arguments: guibg, guifg. | |
| 4746 | |
| 4747 *hl-Tooltip* | |
| 4748 Tooltip Current font, background and foreground of the tooltips. | |
| 4749 Applicable highlight arguments: font, guibg, guifg. | |
| 4750 | |
| 4751 NOTE: For Motif and Athena the font argument actually | |
| 4752 specifies a fontset at all times, no matter if 'guifontset' is | |
| 4753 empty, and as such it is tied to the current |:language| when | |
| 4754 set. | |
| 4755 | |
| 4756 ============================================================================== | |
| 4757 13. Linking groups *:hi-link* *:highlight-link* *E412* *E413* | |
| 4758 | |
| 4759 When you want to use the same highlighting for several syntax groups, you | |
| 4760 can do this more easily by linking the groups into one common highlight | |
| 4761 group, and give the color attributes only for that group. | |
| 4762 | |
| 4763 To set a link: | |
| 4764 | |
| 4765 :hi[ghlight][!] [default] link {from-group} {to-group} | |
| 4766 | |
| 4767 To remove a link: | |
| 4768 | |
| 4769 :hi[ghlight][!] [default] link {from-group} NONE | |
| 4770 | |
| 4771 Notes: *E414* | |
| 4772 - If the {from-group} and/or {to-group} doesn't exist, it is created. You | |
| 4773 don't get an error message for a non-existing group. | |
| 4774 - As soon as you use a ":highlight" command for a linked group, the link is | |
| 4775 removed. | |
| 4776 - If there are already highlight settings for the {from-group}, the link is | |
| 4777 not made, unless the '!' is given. For a ":highlight link" command in a | |
| 4778 sourced file, you don't get an error message. This can be used to skip | |
| 4779 links for groups that already have settings. | |
| 4780 | |
| 4781 *:hi-default* *:highlight-default* | |
| 4782 The [default] argument is used for setting the default highlighting for a | |
| 4783 group. If highlighting has already been specified for the group the command | |
| 4784 will be ignored. Also when there is an existing link. | |
| 4785 | |
| 4786 Using [default] is especially useful to overrule the highlighting of a | |
| 4787 specific syntax file. For example, the C syntax file contains: > | |
| 4788 :highlight default link cComment Comment | |
| 4789 If you like Question highlighting for C comments, put this in your vimrc file: > | |
| 4790 :highlight link cComment Question | |
| 4791 Without the "default" in the C syntax file, the highlighting would be | |
| 4792 overruled when the syntax file is loaded. | |
| 4793 | |
| 4794 ============================================================================== | |
| 4795 14. Cleaning up *:syn-clear* *E391* | |
| 4796 | |
| 4797 If you want to clear the syntax stuff for the current buffer, you can use this | |
| 4798 command: > | |
| 4799 :syntax clear | |
| 4800 | |
| 4801 This command should be used when you want to switch off syntax highlighting, | |
| 4802 or when you want to switch to using another syntax. It's normally not needed | |
| 4803 in a syntax file itself, because syntax is cleared by the autocommands that | |
| 4804 load the syntax file. | |
| 4805 The command also deletes the "b:current_syntax" variable, since no syntax is | |
| 4806 loaded after this command. | |
| 4807 | |
| 4808 If you want to disable syntax highlighting for all buffers, you need to remove | |
| 4809 the autocommands that load the syntax files: > | |
| 4810 :syntax off | |
| 4811 | |
| 4812 What this command actually does, is executing the command > | |
| 4813 :source $VIMRUNTIME/syntax/nosyntax.vim | |
| 4814 See the "nosyntax.vim" file for details. Note that for this to work | |
| 4815 $VIMRUNTIME must be valid. See |$VIMRUNTIME|. | |
| 4816 | |
| 4817 To clean up specific syntax groups for the current buffer: > | |
| 4818 :syntax clear {group-name} .. | |
| 4819 This removes all patterns and keywords for {group-name}. | |
| 4820 | |
| 4821 To clean up specific syntax group lists for the current buffer: > | |
| 4822 :syntax clear @{grouplist-name} .. | |
| 4823 This sets {grouplist-name}'s contents to an empty list. | |
| 4824 | |
| 4825 *:syntax-reset* *:syn-reset* | |
| 4826 If you have changed the colors and messed them up, use this command to get the | |
| 4827 defaults back: > | |
| 4828 | |
| 4829 :syntax reset | |
| 4830 | |
| 4831 This doesn't change the colors for the 'highlight' option. | |
| 4832 | |
| 4833 Note that the syntax colors that you set in your vimrc file will also be reset | |
| 4834 back to their Vim default. | |
| 4835 Note that if you are using a color scheme, the colors defined by the color | |
| 4836 scheme for syntax highlighting will be lost. | |
| 4837 | |
| 4838 What this actually does is: > | |
| 4839 | |
| 4840 let g:syntax_cmd = "reset" | |
| 4841 runtime! syntax/syncolor.vim | |
| 4842 | |
| 4843 Note that this uses the 'runtimepath' option. | |
| 4844 | |
| 4845 *syncolor* | |
| 4846 If you want to use different colors for syntax highlighting, you can add a Vim | |
| 4847 script file to set these colors. Put this file in a directory in | |
| 4848 'runtimepath' which comes after $VIMRUNTIME, so that your settings overrule | |
| 4849 the default colors. This way these colors will be used after the ":syntax | |
| 4850 reset" command. | |
| 4851 | |
| 4852 For Unix you can use the file ~/.vim/after/syntax/syncolor.vim. Example: > | |
| 4853 | |
| 4854 if &background == "light" | |
| 4855 highlight comment ctermfg=darkgreen guifg=darkgreen | |
| 4856 else | |
| 4857 highlight comment ctermfg=green guifg=green | |
| 4858 endif | |
| 4859 | |
| 24 | 4860 *E679* |
| 4861 Do make sure this syncolor.vim script does not use a "syntax on", set the | |
| 4862 'background' option or uses a "colorscheme" command, because it results in an | |
| 4863 endless loop. | |
| 4864 | |
| 7 | 4865 Note that when a color scheme is used, there might be some confusion whether |
| 4866 your defined colors are to be used or the colors from the scheme. This | |
| 4867 depends on the color scheme file. See |:colorscheme|. | |
| 4868 | |
| 4869 *syntax_cmd* | |
| 4870 The "syntax_cmd" variable is set to one of these values when the | |
| 4871 syntax/syncolor.vim files are loaded: | |
| 4872 "on" ":syntax on" command. Highlight colors are overruled but | |
| 4873 links are kept | |
| 4874 "enable" ":syntax enable" command. Only define colors for groups that | |
| 4875 don't have highlighting yet. Use ":syntax default". | |
| 4876 "reset" ":syntax reset" command or loading a color scheme. Define all | |
| 4877 the colors. | |
| 4878 "skip" Don't define colors. Used to skip the default settings when a | |
| 4879 syncolor.vim file earlier in 'runtimepath' has already set | |
| 4880 them. | |
| 4881 | |
| 4882 ============================================================================== | |
| 4883 15. Highlighting tags *tag-highlight* | |
| 4884 | |
| 4885 If you want to highlight all the tags in your file, you can use the following | |
| 4886 mappings. | |
| 4887 | |
| 4888 <F11> -- Generate tags.vim file, and highlight tags. | |
| 4889 <F12> -- Just highlight tags based on existing tags.vim file. | |
| 4890 > | |
| 4891 :map <F11> :sp tags<CR>:%s/^\([^ :]*:\)\=\([^ ]*\).*/syntax keyword Tag \2/<CR>:wq! tags.vim<CR>/^<CR><F12> | |
| 4892 :map <F12> :so tags.vim<CR> | |
| 4893 | |
| 4894 WARNING: The longer the tags file, the slower this will be, and the more | |
| 4895 memory Vim will consume. | |
| 4896 | |
| 4897 Only highlighting typedefs, unions and structs can be done too. For this you | |
| 4898 must use Exuberant ctags (found at http://ctags.sf.net). | |
| 4899 | |
| 4900 Put these lines in your Makefile: | |
| 4901 | |
| 4902 # Make a highlight file for types. Requires Exuberant ctags and awk | |
| 4903 types: types.vim | |
| 4904 types.vim: *.[ch] | |
| 1125 | 4905 ctags --c-kinds=gstu -o- *.[ch] |\ |
| 7 | 4906 awk 'BEGIN{printf("syntax keyword Type\t")}\ |
| 4907 {printf("%s ", $$1)}END{print ""}' > $@ | |
| 4908 | |
| 4909 And put these lines in your .vimrc: > | |
| 4910 | |
| 4911 " load the types.vim highlighting file, if it exists | |
| 4912 autocmd BufRead,BufNewFile *.[ch] let fname = expand('<afile>:p:h') . '/types.vim' | |
| 4913 autocmd BufRead,BufNewFile *.[ch] if filereadable(fname) | |
| 4914 autocmd BufRead,BufNewFile *.[ch] exe 'so ' . fname | |
| 4915 autocmd BufRead,BufNewFile *.[ch] endif | |
| 4916 | |
| 4917 ============================================================================== | |
|
2250
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4918 16. Window-local syntax *:ownsyntax* |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4919 |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4920 Normally all windows on a buffer share the same syntax settings. It is |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4921 possible, however, to set a particular window on a file to have its own |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4922 private syntax setting. A possible example would be to edit LaTeX source |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4923 with conventional highlighting in one window, while seeing the same source |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4924 highlighted differently (so as to hide control sequences and indicate bold, |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4925 italic etc regions) in another. The 'scrollbind' option is useful here. |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4926 |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4927 To set the current window to have the syntax "foo", separately from all other |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4928 windows on the buffer: > |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4929 :ownsyntax foo |
|
2254
4620acaf4814
One more fix for conceal patch.
Bram Moolenaar <bram@vim.org>
parents:
2250
diff
changeset
|
4930 < *w:current_syntax* |
|
4620acaf4814
One more fix for conceal patch.
Bram Moolenaar <bram@vim.org>
parents:
2250
diff
changeset
|
4931 This will set the "w:current_syntax" variable to "foo". The value of |
|
4620acaf4814
One more fix for conceal patch.
Bram Moolenaar <bram@vim.org>
parents:
2250
diff
changeset
|
4932 "b:current_syntax" does not change. This is implemented by saving and |
|
4620acaf4814
One more fix for conceal patch.
Bram Moolenaar <bram@vim.org>
parents:
2250
diff
changeset
|
4933 restoring "b:current_syntax", since the syntax files do set |
|
4620acaf4814
One more fix for conceal patch.
Bram Moolenaar <bram@vim.org>
parents:
2250
diff
changeset
|
4934 "b:current_syntax". The value set by the syntax file is assigned to |
|
4620acaf4814
One more fix for conceal patch.
Bram Moolenaar <bram@vim.org>
parents:
2250
diff
changeset
|
4935 "w:current_syntax". |
|
2250
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4936 |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4937 Once a window has its own syntax, syntax commands executed from other windows |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4938 on the same buffer (including :syntax clear) have no effect. Conversely, |
| 4264 | 4939 syntax commands executed from that window do not affect other windows on the |
|
2250
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4940 same buffer. |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4941 |
|
2254
4620acaf4814
One more fix for conceal patch.
Bram Moolenaar <bram@vim.org>
parents:
2250
diff
changeset
|
4942 A window with its own syntax reverts to normal behavior when another buffer |
|
4620acaf4814
One more fix for conceal patch.
Bram Moolenaar <bram@vim.org>
parents:
2250
diff
changeset
|
4943 is loaded into that window or the file is reloaded. |
|
4620acaf4814
One more fix for conceal patch.
Bram Moolenaar <bram@vim.org>
parents:
2250
diff
changeset
|
4944 When splitting the window, the new window will use the original syntax. |
|
2250
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4945 |
|
1bac28a53fae
Add the conceal patch from Vince Negri.
Bram Moolenaar <bram@vim.org>
parents:
2236
diff
changeset
|
4946 ============================================================================== |
| 2581 | 4947 17. Color xterms *xterm-color* *color-xterm* |
| 7 | 4948 |
| 4949 Most color xterms have only eight colors. If you don't get colors with the | |
| 4950 default setup, it should work with these lines in your .vimrc: > | |
| 4951 :if &term =~ "xterm" | |
| 4952 : if has("terminfo") | |
| 4953 : set t_Co=8 | |
| 4954 : set t_Sf=<Esc>[3%p1%dm | |
| 4955 : set t_Sb=<Esc>[4%p1%dm | |
| 4956 : else | |
| 4957 : set t_Co=8 | |
| 4958 : set t_Sf=<Esc>[3%dm | |
| 4959 : set t_Sb=<Esc>[4%dm | |
| 4960 : endif | |
| 4961 :endif | |
| 4962 < [<Esc> is a real escape, type CTRL-V <Esc>] | |
| 4963 | |
| 4964 You might want to change the first "if" to match the name of your terminal, | |
| 4965 e.g. "dtterm" instead of "xterm". | |
| 4966 | |
| 4967 Note: Do these settings BEFORE doing ":syntax on". Otherwise the colors may | |
| 4968 be wrong. | |
| 4969 *xiterm* *rxvt* | |
| 4970 The above settings have been mentioned to work for xiterm and rxvt too. | |
| 4971 But for using 16 colors in an rxvt these should work with terminfo: > | |
| 4972 :set t_AB=<Esc>[%?%p1%{8}%<%t25;%p1%{40}%+%e5;%p1%{32}%+%;%dm | |
| 4973 :set t_AF=<Esc>[%?%p1%{8}%<%t22;%p1%{30}%+%e1;%p1%{22}%+%;%dm | |
| 4974 < | |
| 4975 *colortest.vim* | |
| 4976 To test your color setup, a file has been included in the Vim distribution. | |
| 671 | 4977 To use it, execute this command: > |
| 4978 :runtime syntax/colortest.vim | |
| 7 | 4979 |
| 237 | 4980 Some versions of xterm (and other terminals, like the Linux console) can |
| 7 | 4981 output lighter foreground colors, even though the number of colors is defined |
| 4982 at 8. Therefore Vim sets the "cterm=bold" attribute for light foreground | |
| 4983 colors, when 't_Co' is 8. | |
| 4984 | |
| 4985 *xfree-xterm* | |
| 4986 To get 16 colors or more, get the newest xterm version (which should be | |
| 237 | 4987 included with XFree86 3.3 and later). You can also find the latest version |
| 7 | 4988 at: > |
| 4989 http://invisible-island.net/xterm/xterm.html | |
| 4990 Here is a good way to configure it. This uses 88 colors and enables the | |
| 4991 termcap-query feature, which allows Vim to ask the xterm how many colors it | |
| 4992 supports. > | |
| 4993 ./configure --disable-bold-color --enable-88-color --enable-tcap-query | |
| 4994 If you only get 8 colors, check the xterm compilation settings. | |
| 4995 (Also see |UTF8-xterm| for using this xterm with UTF-8 character encoding). | |
| 4996 | |
| 4997 This xterm should work with these lines in your .vimrc (for 16 colors): > | |
| 4998 :if has("terminfo") | |
| 4999 : set t_Co=16 | |
| 5000 : set t_AB=<Esc>[%?%p1%{8}%<%t%p1%{40}%+%e%p1%{92}%+%;%dm | |
| 5001 : set t_AF=<Esc>[%?%p1%{8}%<%t%p1%{30}%+%e%p1%{82}%+%;%dm | |
| 5002 :else | |
| 5003 : set t_Co=16 | |
| 5004 : set t_Sf=<Esc>[3%dm | |
| 5005 : set t_Sb=<Esc>[4%dm | |
| 5006 :endif | |
| 5007 < [<Esc> is a real escape, type CTRL-V <Esc>] | |
| 5008 | |
| 5009 Without |+terminfo|, Vim will recognize these settings, and automatically | |
| 5010 translate cterm colors of 8 and above to "<Esc>[9%dm" and "<Esc>[10%dm". | |
| 5011 Colors above 16 are also translated automatically. | |
| 5012 | |
| 5013 For 256 colors this has been reported to work: > | |
| 5014 | |
| 5015 :set t_AB=<Esc>[48;5;%dm | |
| 5016 :set t_AF=<Esc>[38;5;%dm | |
| 5017 | |
| 5018 Or just set the TERM environment variable to "xterm-color" or "xterm-16color" | |
| 5019 and try if that works. | |
| 5020 | |
| 5021 You probably want to use these X resources (in your ~/.Xdefaults file): | |
| 5022 XTerm*color0: #000000 | |
| 5023 XTerm*color1: #c00000 | |
| 5024 XTerm*color2: #008000 | |
| 5025 XTerm*color3: #808000 | |
| 5026 XTerm*color4: #0000c0 | |
| 5027 XTerm*color5: #c000c0 | |
| 5028 XTerm*color6: #008080 | |
| 5029 XTerm*color7: #c0c0c0 | |
| 5030 XTerm*color8: #808080 | |
| 5031 XTerm*color9: #ff6060 | |
| 5032 XTerm*color10: #00ff00 | |
| 5033 XTerm*color11: #ffff00 | |
| 5034 XTerm*color12: #8080ff | |
| 5035 XTerm*color13: #ff40ff | |
| 5036 XTerm*color14: #00ffff | |
| 5037 XTerm*color15: #ffffff | |
| 5038 Xterm*cursorColor: Black | |
| 5039 | |
| 5040 [Note: The cursorColor is required to work around a bug, which changes the | |
| 5041 cursor color to the color of the last drawn text. This has been fixed by a | |
| 1125 | 5042 newer version of xterm, but not everybody is using it yet.] |
| 7 | 5043 |
| 5044 To get these right away, reload the .Xdefaults file to the X Option database | |
| 5045 Manager (you only need to do this when you just changed the .Xdefaults file): > | |
| 5046 xrdb -merge ~/.Xdefaults | |
| 5047 < | |
| 5048 *xterm-blink* *xterm-blinking-cursor* | |
| 5049 To make the cursor blink in an xterm, see tools/blink.c. Or use Thomas | |
| 5050 Dickey's xterm above patchlevel 107 (see above for where to get it), with | |
| 5051 these resources: | |
| 5052 XTerm*cursorBlink: on | |
| 5053 XTerm*cursorOnTime: 400 | |
| 5054 XTerm*cursorOffTime: 250 | |
| 5055 XTerm*cursorColor: White | |
| 5056 | |
| 5057 *hpterm-color* | |
| 1125 | 5058 These settings work (more or less) for an hpterm, which only supports 8 |
| 7 | 5059 foreground colors: > |
| 5060 :if has("terminfo") | |
| 5061 : set t_Co=8 | |
| 5062 : set t_Sf=<Esc>[&v%p1%dS | |
| 5063 : set t_Sb=<Esc>[&v7S | |
| 5064 :else | |
| 5065 : set t_Co=8 | |
| 5066 : set t_Sf=<Esc>[&v%dS | |
| 5067 : set t_Sb=<Esc>[&v7S | |
| 5068 :endif | |
| 5069 < [<Esc> is a real escape, type CTRL-V <Esc>] | |
| 5070 | |
| 5071 *Eterm* *enlightened-terminal* | |
| 5072 These settings have been reported to work for the Enlightened terminal | |
| 5073 emulator, or Eterm. They might work for all xterm-like terminals that use the | |
| 5074 bold attribute to get bright colors. Add an ":if" like above when needed. > | |
| 5075 :set t_Co=16 | |
| 5076 :set t_AF=^[[%?%p1%{8}%<%t3%p1%d%e%p1%{22}%+%d;1%;m | |
| 5077 :set t_AB=^[[%?%p1%{8}%<%t4%p1%d%e%p1%{32}%+%d;1%;m | |
| 5078 < | |
| 5079 *TTpro-telnet* | |
| 5080 These settings should work for TTpro telnet. Tera Term Pro is a freeware / | |
| 5081 open-source program for MS-Windows. > | |
| 5082 set t_Co=16 | |
| 5083 set t_AB=^[[%?%p1%{8}%<%t%p1%{40}%+%e%p1%{32}%+5;%;%dm | |
| 5084 set t_AF=^[[%?%p1%{8}%<%t%p1%{30}%+%e%p1%{22}%+1;%;%dm | |
| 5085 Also make sure TTpro's Setup / Window / Full Color is enabled, and make sure | |
| 5086 that Setup / Font / Enable Bold is NOT enabled. | |
| 5087 (info provided by John Love-Jensen <eljay@Adobe.COM>) | |
| 5088 | |
| 5089 vim:tw=78:sw=4:ts=8:ft=help:norl: |