Mercurial > vim
comparison runtime/doc/syntax.txt @ 8876:47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Apr 12 21:07:15 2016 +0200
Updated runtime files.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Tue, 12 Apr 2016 21:15:06 +0200 |
parents | ed7251c3e2d3 |
children | ecb621205ed1 |
comparison
equal
deleted
inserted
replaced
8875:31a3f0c0f011 | 8876:47f17f66da3d |
---|---|
1 *syntax.txt* For Vim version 7.4. Last change: 2016 Mar 12 | 1 *syntax.txt* For Vim version 7.4. Last change: 2016 Apr 10 |
2 | 2 |
3 | 3 |
4 VIM REFERENCE MANUAL by Bram Moolenaar | 4 VIM REFERENCE MANUAL by Bram Moolenaar |
5 | 5 |
6 | 6 |
939 :let c_comment_strings = 1 | 939 :let c_comment_strings = 1 |
940 To disable them use ":unlet". Example: > | 940 To disable them use ":unlet". Example: > |
941 :unlet c_comment_strings | 941 :unlet c_comment_strings |
942 | 942 |
943 Variable Highlight ~ | 943 Variable Highlight ~ |
944 c_gnu GNU gcc specific items | 944 *c_gnu* GNU gcc specific items |
945 c_comment_strings strings and numbers inside a comment | 945 *c_comment_strings* strings and numbers inside a comment |
946 c_space_errors trailing white space and spaces before a <Tab> | 946 *c_space_errors* trailing white space and spaces before a <Tab> |
947 c_no_trail_space_error ... but no trailing spaces | 947 *c_no_trail_space_error* ... but no trailing spaces |
948 c_no_tab_space_error ... but no spaces before a <Tab> | 948 *c_no_tab_space_error* ... but no spaces before a <Tab> |
949 c_no_bracket_error don't highlight {}; inside [] as errors | 949 *c_no_bracket_error* don't highlight {}; inside [] as errors |
950 c_no_curly_error don't highlight {}; inside [] and () as errors; | 950 *c_no_curly_error* don't highlight {}; inside [] and () as errors; |
951 except { and } in first column | 951 except { and } in first column |
952 c_curly_error highlight a missing }; this forces syncing from the | 952 *c_curly_error* highlight a missing }; this forces syncing from the |
953 start of the file, can be slow | 953 start of the file, can be slow |
954 c_no_ansi don't do standard ANSI types and constants | 954 *c_no_ansi* don't do standard ANSI types and constants |
955 c_ansi_typedefs ... but do standard ANSI types | 955 *c_ansi_typedefs* ... but do standard ANSI types |
956 c_ansi_constants ... but do standard ANSI constants | 956 *c_ansi_constants* ... but do standard ANSI constants |
957 c_no_utf don't highlight \u and \U in strings | 957 *c_no_utf* don't highlight \u and \U in strings |
958 c_syntax_for_h for *.h files use C syntax instead of C++ and use objc | 958 *c_syntax_for_h* for *.h files use C syntax instead of C++ and use objc |
959 syntax instead of objcpp | 959 syntax instead of objcpp |
960 c_no_if0 don't highlight "#if 0" blocks as comments | 960 *c_no_if0* don't highlight "#if 0" blocks as comments |
961 c_no_cformat don't highlight %-formats in strings | 961 *c_no_cformat* don't highlight %-formats in strings |
962 c_no_c99 don't highlight C99 standard items | 962 *c_no_c99* don't highlight C99 standard items |
963 c_no_c11 don't highlight C11 standard items | 963 *c_no_c11* don't highlight C11 standard items |
964 *c_no_bsd* don't highlight BSD specific types | |
964 | 965 |
965 When 'foldmethod' is set to "syntax" then /* */ comments and { } blocks will | 966 When 'foldmethod' is set to "syntax" then /* */ comments and { } blocks will |
966 become a fold. If you don't want comments to become a fold use: > | 967 become a fold. If you don't want comments to become a fold use: > |
967 :let c_no_comment_fold = 1 | 968 :let c_no_comment_fold = 1 |
968 "#if 0" blocks are also folded, unless: > | 969 "#if 0" blocks are also folded, unless: > |
5045 If you have changed the colors and messed them up, use this command to get the | 5046 If you have changed the colors and messed them up, use this command to get the |
5046 defaults back: > | 5047 defaults back: > |
5047 | 5048 |
5048 :syntax reset | 5049 :syntax reset |
5049 | 5050 |
5051 It is a bit of a wrong name, since it does not reset any syntax items, it only | |
5052 affects the highlighting. | |
5053 | |
5050 This doesn't change the colors for the 'highlight' option. | 5054 This doesn't change the colors for the 'highlight' option. |
5051 | 5055 |
5052 Note that the syntax colors that you set in your vimrc file will also be reset | 5056 Note that the syntax colors that you set in your vimrc file will also be reset |
5053 back to their Vim default. | 5057 back to their Vim default. |
5054 Note that if you are using a color scheme, the colors defined by the color | 5058 Note that if you are using a color scheme, the colors defined by the color |