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