Mercurial > vim
comparison runtime/doc/syntax.txt @ 10895:c391bfbdb452
Updated runtime files.
commit https://github.com/vim/vim/commit/3df0173fa6d0418e89ef4e9c1d04a97c92eec27c
Author: Bram Moolenaar <Bram@vim.org>
Date: Fri Feb 17 22:47:16 2017 +0100
Updated runtime files.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Fri, 17 Feb 2017 23:00:06 +0100 |
parents | 523cd59d6db0 |
children | e05695e59f6d |
comparison
equal
deleted
inserted
replaced
10894:f1cb20e3550e | 10895:c391bfbdb452 |
---|---|
1 *syntax.txt* For Vim version 8.0. Last change: 2017 Jan 17 | 1 *syntax.txt* For Vim version 8.0. Last change: 2017 Feb 06 |
2 | 2 |
3 | 3 |
4 VIM REFERENCE MANUAL by Bram Moolenaar | 4 VIM REFERENCE MANUAL by Bram Moolenaar |
5 | 5 |
6 | 6 |
1474 are detected, then the file is assumed to be in fixed source form. The | 1474 are detected, then the file is assumed to be in fixed source form. The |
1475 algorithm should work in the vast majority of cases. In some cases, such as a | 1475 algorithm should work in the vast majority of cases. In some cases, such as a |
1476 file that begins with 500 or more full-line comments, the script may | 1476 file that begins with 500 or more full-line comments, the script may |
1477 incorrectly decide that the fortran code is in fixed form. If that happens, | 1477 incorrectly decide that the fortran code is in fixed form. If that happens, |
1478 just add a non-comment statement beginning anywhere in the first five columns | 1478 just add a non-comment statement beginning anywhere in the first five columns |
1479 of the first twenty five lines, save (:w) and then reload (:e!) the file. | 1479 of the first twenty-five lines, save (:w) and then reload (:e!) the file. |
1480 | 1480 |
1481 Tabs in fortran files ~ | 1481 Tabs in fortran files ~ |
1482 Tabs are not recognized by the Fortran standards. Tabs are not a good idea in | 1482 Tabs are not recognized by the Fortran standards. Tabs are not a good idea in |
1483 fixed format fortran source code which requires fixed column boundaries. | 1483 fixed format fortran source code which requires fixed column boundaries. |
1484 Therefore, tabs are marked as errors. Nevertheless, some programmers like | 1484 Therefore, tabs are marked as errors. Nevertheless, some programmers like |
2931 let sh_maxlines = 100 | 2931 let sh_maxlines = 100 |
2932 < | 2932 < |
2933 The default is to use the twice sh_minlines. Set it to a smaller number to | 2933 The default is to use the twice sh_minlines. Set it to a smaller number to |
2934 speed up displaying. The disadvantage is that highlight errors may appear. | 2934 speed up displaying. The disadvantage is that highlight errors may appear. |
2935 | 2935 |
2936 syntax/sh.vim tries to flag certain problems as errors; usually things like | |
2937 extra ']'s, 'done's, 'fi's, etc. If you find the error handling problematic | |
2938 for your purposes, you may suppress such error highlighting by putting | |
2939 the following line in your .vimrc: > | |
2940 | |
2941 let g:sh_no_error= 1 | |
2942 < | |
2936 | 2943 |
2937 *sh-embed* *sh-awk* | 2944 *sh-embed* *sh-awk* |
2938 Sh: EMBEDDING LANGUAGES~ | 2945 Sh: EMBEDDING LANGUAGES~ |
2939 | 2946 |
2940 You may wish to embed languages into sh. I'll give an example courtesy of | 2947 You may wish to embed languages into sh. I'll give an example courtesy of |
3233 syntax highlighting script handles this with the following logic: | 3240 syntax highlighting script handles this with the following logic: |
3234 | 3241 |
3235 * If g:tex_stylish exists and is 1 | 3242 * If g:tex_stylish exists and is 1 |
3236 then the file will be treated as a "sty" file, so the "_" | 3243 then the file will be treated as a "sty" file, so the "_" |
3237 will be allowed as part of keywords | 3244 will be allowed as part of keywords |
3238 (irregardless of g:tex_isk) | 3245 (regardless of g:tex_isk) |
3239 * Else if the file's suffix is sty, cls, clo, dtx, or ltx, | 3246 * Else if the file's suffix is sty, cls, clo, dtx, or ltx, |
3240 then the file will be treated as a "sty" file, so the "_" | 3247 then the file will be treated as a "sty" file, so the "_" |
3241 will be allowed as part of keywords | 3248 will be allowed as part of keywords |
3242 (irregardless of g:tex_isk) | 3249 (regardless of g:tex_isk) |
3243 | 3250 |
3244 * If g:tex_isk exists, then it will be used for the local 'iskeyword' | 3251 * If g:tex_isk exists, then it will be used for the local 'iskeyword' |
3245 * Else the local 'iskeyword' will be set to 48-57,a-z,A-Z,192-255 | 3252 * Else the local 'iskeyword' will be set to 48-57,a-z,A-Z,192-255 |
3246 | 3253 |
3247 *tex-supersub* *g:tex_superscripts* *g:tex_subscripts* | 3254 *tex-supersub* *g:tex_superscripts* *g:tex_subscripts* |