Mercurial > vim
comparison runtime/doc/syntax.txt @ 22:cc049b00ee70
updated for version 7.0014
author | vimboss |
---|---|
date | Thu, 02 Sep 2004 19:12:26 +0000 |
parents | 9be87deaeb52 |
children | 8ff7fd162d3c |
comparison
equal
deleted
inserted
replaced
21:db5102f7e29f | 22:cc049b00ee70 |
---|---|
1 *syntax.txt* For Vim version 7.0aa. Last change: 2004 Jul 15 | 1 *syntax.txt* For Vim version 7.0aa. Last change: 2004 Sep 01 |
2 | 2 |
3 | 3 |
4 VIM REFERENCE MANUAL by Bram Moolenaar | 4 VIM REFERENCE MANUAL by Bram Moolenaar |
5 | 5 |
6 | 6 |
662 ~/.vim/after/syntax/c.vim. > | 662 ~/.vim/after/syntax/c.vim. > |
663 syn region myFold start="{" end="}" transparent fold | 663 syn region myFold start="{" end="}" transparent fold |
664 syn sync fromstart | 664 syn sync fromstart |
665 set foldmethod=syntax | 665 set foldmethod=syntax |
666 | 666 |
667 CH *ch.vim* *ch-syntax* | |
668 | |
669 C/C++ interpreter. Ch has similar syntax highlighting to C and builds upon | |
670 the C syntax file. See |c.vim| for all the settings that are available for C. | |
671 | |
672 By setting a variable you can tell Vim to use Ch syntax for *.h files, instead | |
673 of C or C++: > | |
674 :let ch_syntax_for_h = 1 | |
675 | |
667 | 676 |
668 CHILL *chill.vim* *chill-syntax* | 677 CHILL *chill.vim* *chill-syntax* |
669 | 678 |
670 Chill syntax highlighting is similar to C. See |c.vim| for all the settings | 679 Chill syntax highlighting is similar to C. See |c.vim| for all the settings |
671 that are available. Additionally there is: | 680 that are available. Additionally there is: |
672 | 681 |
673 chill_syntax_for_h use Ch syntax for *.h files, instead of C or C++ | |
674 chill_space_errors like c_space_errors | 682 chill_space_errors like c_space_errors |
675 chill_comment_string like c_comment_strings | 683 chill_comment_string like c_comment_strings |
676 chill_minlines like c_minlines | 684 chill_minlines like c_minlines |
677 | 685 |
678 | 686 |
1774 | 1782 |
1775 If you use POD files or POD segments, you might: > | 1783 If you use POD files or POD segments, you might: > |
1776 | 1784 |
1777 :let perl_include_pod = 1 | 1785 :let perl_include_pod = 1 |
1778 | 1786 |
1779 To handle package references in variable and function names differently from | 1787 The reduce the complexity of parsing (and increase performance) you can switch |
1780 the rest of the name (like 'PkgName::' in '$PkgName::VarName'): > | 1788 off two elements in the parsing of variable names and contents. > |
1781 | 1789 |
1782 :let perl_want_scope_in_variables = 1 | 1790 To handle package references in variable and function names not differently |
1783 | 1791 from the rest of the name (like 'PkgName::' in '$PkgName::VarName'): > |
1784 If you want complex things like '@{${"foo"}}' to be parsed: > | 1792 |
1785 | 1793 :let perl_no_scope_in_variables = 1 |
1786 :let perl_extended_vars = 1 | 1794 |
1795 (In Vim 6.x it was the other way around: "perl_want_scope_in_variables" | |
1796 enabled it.) | |
1797 | |
1798 If you do not want complex things like '@{${"foo"}}' to be parsed: > | |
1799 | |
1800 :let perl_no_extended_vars = 1 | |
1801 | |
1802 {In Vim 6.x it was the other way around: "perl_extended_vars" enabled it.) | |
1787 | 1803 |
1788 The coloring strings can be changed. By default strings and qq friends will be | 1804 The coloring strings can be changed. By default strings and qq friends will be |
1789 highlighted like the first line. If you set the variable | 1805 highlighted like the first line. If you set the variable |
1790 perl_string_as_statement, it will be highlighted as in the second line. | 1806 perl_string_as_statement, it will be highlighted as in the second line. |
1791 | 1807 |
1811 | 1827 |
1812 :let perl_sync_dist = 100 | 1828 :let perl_sync_dist = 100 |
1813 | 1829 |
1814 If you want to use folding with perl, set perl_fold: > | 1830 If you want to use folding with perl, set perl_fold: > |
1815 | 1831 |
1816 :let perl_fold = 1 | 1832 :let perl_fold = 1 |
1833 | |
1834 If you want to fold blocks in if statements, etc. as well set the following: > | |
1835 | |
1836 :let perl_fold_blocks = 1 | |
1817 | 1837 |
1818 | 1838 |
1819 PHP3 and PHP4 *php.vim* *php3.vim* *php-syntax* *php3-syntax* | 1839 PHP3 and PHP4 *php.vim* *php3.vim* *php-syntax* *php3-syntax* |
1820 | 1840 |
1821 [note: previously this was called "php3", but since it now also supports php4 | 1841 [note: previously this was called "php3", but since it now also supports php4 |
2260 | 2280 |
2261 Since especially OPERATION sections tend to become very large due to | 2281 Since especially OPERATION sections tend to become very large due to |
2262 PRESETting variables, syncing may be critical. If your computer is | 2282 PRESETting variables, syncing may be critical. If your computer is |
2263 fast enough, you can increase minlines and/or maxlines near the end of | 2283 fast enough, you can increase minlines and/or maxlines near the end of |
2264 the syntax file. | 2284 the syntax file. |
2285 | |
2286 | |
2287 SQL *sql.vim* *sql-syntax* | |
2288 *sqlinformix.vim* *sqlinformix-syntax* | |
2289 | |
2290 While there is an ANSI standard for SQL, most database engines add their | |
2291 own custom extensions. Vim currently supports the Oracle and Informix | |
2292 dialects of SQL. Vim assumes "*.sql" files are Oracle SQL by default. | |
2293 | |
2294 If you want to use the Informix dialect, put this in your startup vimrc: > | |
2295 :let g:filetype_sql = "sqlinformix" | |
2265 | 2296 |
2266 | 2297 |
2267 TCSH *tcsh.vim* *tcsh-syntax* | 2298 TCSH *tcsh.vim* *tcsh-syntax* |
2268 | 2299 |
2269 This covers the shell named "tcsh". It is a superset of csh. See |csh.vim| | 2300 This covers the shell named "tcsh". It is a superset of csh. See |csh.vim| |
3512 :echo g:colors_name | 3543 :echo g:colors_name |
3513 < Doesn't work recursively, thus you can't use | 3544 < Doesn't work recursively, thus you can't use |
3514 ":colorscheme" in a color scheme script. | 3545 ":colorscheme" in a color scheme script. |
3515 After the color scheme has been loaded the | 3546 After the color scheme has been loaded the |
3516 |ColorScheme| autocommand event is triggered. | 3547 |ColorScheme| autocommand event is triggered. |
3548 For info about writing a colorscheme file: > | |
3549 :edit $VIMRUNTIME/colors/README.txt | |
3517 | 3550 |
3518 :hi[ghlight] List all the current highlight groups that have | 3551 :hi[ghlight] List all the current highlight groups that have |
3519 attributes set. | 3552 attributes set. |
3520 | 3553 |
3521 :hi[ghlight] {group-name} | 3554 :hi[ghlight] {group-name} |