Mercurial > vim

comparison runtime/doc/syntax.txt @ 4229:fa4089df54bc

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Update runtime files.
author Bram Moolenaar <bram@vim.org>
date Tue, 19 Mar 2013 11:35:58 +0100
parents 7ffc704cb7c1
children 2d1383658bb4
comparison
equal deleted inserted replaced
4228:1e1297b26329 4229:fa4089df54bc
1 *syntax.txt* For Vim version 7.3. Last change: 2013 Mar 01 1 *syntax.txt* For Vim version 7.3. Last change: 2013 Mar 13
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
2926 if any, is the text at the top of the screen supposed to be in?). 2926 if any, is the text at the top of the screen supposed to be in?).
2927 2927
2928 Another cause of slow highlighting is due to syntax-driven folding; see 2928 Another cause of slow highlighting is due to syntax-driven folding; see
2929 |tex-folding| for a way around this. 2929 |tex-folding| for a way around this.
2930 2930
2931 *g:tex_fast*
2932
2933 Finally, if syntax highlighting is still too slow, you may set >
2934
2935 :let g:tex_fast= ""
2936
2937 in your .vimrc. Used this way, the g:tex_fast variable causes the syntax
2938 highlighting script to avoid defining any regions and associated
2939 synchronization. The result will be much faster syntax highlighting; the
2940 price: you will no longer have as much highlighting or any syntax-based
2941 folding, and you will be missing syntax-based error checking.
2942
2943 You may decide that some syntax is acceptable; you may use the following table
2944 selectively to enable just some syntax highlighting: >
2945
2946 b : allow bold and italic syntax
2947 c : allow texComment syntax
2948 m : allow texMatcher syntax (ie. {...} and [...])
2949 M : allow texMath syntax
2950 p : allow parts, chapter, section, etc syntax
2951 r : allow texRefZone syntax (nocite, bibliography, label, pageref, eqref)
2952 s : allow superscript/subscript regions
2953 S : allow texStyle syntax
2954 v : allow verbatim syntax
2955 V : allow texNewEnv and texNewCmd syntax
2956 <
2957 As an example, let g:tex_fast= "M" will allow math-associated highlighting
2958 but suppress all the other region-based syntax highlighting.
2959
2931 *tex-morecommands* *tex-package* 2960 *tex-morecommands* *tex-package*
2932 Tex: Want To Highlight More Commands? ~ 2961 Tex: Want To Highlight More Commands? ~
2933 2962
2934 LaTeX is a programmable language, and so there are thousands of packages full 2963 LaTeX is a programmable language, and so there are thousands of packages full
2935 of specialized LaTeX commands, syntax, and fonts. If you're using such a 2964 of specialized LaTeX commands, syntax, and fonts. If you're using such a
3820 s+{nr} start of the matched pattern plus {nr} chars to the right 3849 s+{nr} start of the matched pattern plus {nr} chars to the right
3821 s-{nr} start of the matched pattern plus {nr} chars to the left 3850 s-{nr} start of the matched pattern plus {nr} chars to the left
3822 e end of the matched pattern 3851 e end of the matched pattern
3823 e+{nr} end of the matched pattern plus {nr} chars to the right 3852 e+{nr} end of the matched pattern plus {nr} chars to the right
3824 e-{nr} end of the matched pattern plus {nr} chars to the left 3853 e-{nr} end of the matched pattern plus {nr} chars to the left
3825 {nr} (for "lc" only): start matching {nr} chars to the left 3854 {nr} (for "lc" only): start matching {nr} chars right of the start
3826 3855
3827 Examples: "ms=s+1", "hs=e-2", "lc=3". 3856 Examples: "ms=s+1", "hs=e-2", "lc=3".
3828 3857
3829 Although all offsets are accepted after any pattern, they are not always 3858 Although all offsets are accepted after any pattern, they are not always
3830 meaningful. This table shows which offsets are actually used: 3859 meaningful. This table shows which offsets are actually used: