Lines Matching refs:highlight
35 13. Highlight command |:highlight|
36 14. Linking groups |:highlight-link|
38 16. Highlighting tags |tag-highlight|
70 This allows using `:highlight` commands to set your preferred colors before or
75 *:hi-normal* *:highlight-normal*
78 :highlight Normal guibg=Black guifg=White
186 highlight cComment ctermfg=Green guifg=Green
213 thing. These are then linked to a highlight group that specifies the color.
216 The name for a highlight or syntax group must consist of ASCII letters, digits
221 be preferred names for highlight groups that are common for many languages.
275 highlighting. You can override these defaults by using ":highlight" commands
278 Note that highlight group names are not case sensitive. "String" and "string"
482 current "DiffDelete" highlight group is used. If "DiffDelete" and "StatusLine"
485 your own highlight colors for the progress bar. Example: >
985 *c_no_bracket_error* don't highlight {}; inside [] as errors
986 *c_no_curly_error* don't highlight {}; inside [] and () as errors;
988 Default is to highlight them, otherwise you
990 *c_curly_error* highlight a missing } by finding all pairs; this
995 *c_no_utf* don't highlight \u and \U in strings
998 *c_no_if0* don't highlight "#if 0" blocks as comments
999 *c_no_cformat* don't highlight %-formats in strings
1000 *c_no_c99* don't highlight C99 standard items
1001 *c_no_c11* don't highlight C11 standard items
1002 *c_no_bsd* don't highlight BSD specific types
1099 this variable intended for use by plugin authors to highlight symbols
1122 Note that this option will not correctly highlight stacked discard macros
1152 cpp_no_cpp11 don't highlight C++11 standard items
1153 cpp_no_cpp14 don't highlight C++14 standard items
1154 cpp_no_cpp17 don't highlight C++17 standard items
1155 cpp_no_cpp20 don't highlight C++20 standard items
1231 Primary goal of this syntax file is to highlight .desktop and .directory files
1234 To highlight nonstandard extensions that does not begin with X-, set >
1236 Note that this may cause wrong highlight.
1237 To highlight KDE-reserved features, set >
1343 There are also some highlight groups worth mentioning as they can be useful in
1360 The DTD syntax file will highlight unknown tags as errors. If
1374 The DTD syntax file is also included by xml.vim to highlight included dtd's.
1381 highlight class names differently. If you want to disable case-sensitive
1695 are redefined to incorporate and highlight inline java code:
1705 group where you will have inline java code where it does not highlight
1726 syntax highlighting will also highlight C preprocessor directives.
1728 If you want to highlight delimiter characters (useful if you have a
1738 If you want to highlight the names of debugging functions, put in
1745 operators, as they may start with #. If you want to highlight those
1751 TeX markup or not, and correspondingly highlight TeX constructs
1757 to force the highlighting to always try to highlight TeX markup.
1815 details), and the syntax coloring scheme will highlight all errors.
1882 This will highlight Glulx opcodes instead, and also adds glk() to the
1932 highlight them use: >
1935 You can also highlight identifiers of most standard Java packages if you
1937 If you prefer to only highlight identifiers of a certain package, say java.io
1943 how you write Java code. The syntax file knows two possible ways to highlight
1955 original one and then adds the code to highlight functions.
1958 only be used for debugging. Therefore it is possible to highlight debugging
1971 creates HTML pages. The standard configuration will highlight this HTML code
1993 In order to highlight nested parens with different colors define colors
2037 To highlight deprecated functions as errors, add in your .vimrc: >
2208 To highlight builtin properties (.name, .location, .programmer etc.): >
2256 If you don't want to highlight these errors, leave it unset.
2559 if you want to highlight brackets "[]" and braces "{}".
2580 - ppwiz_with_html : If the value is 1 (the default), highlight literal
2602 First which version of the PostScript language to highlight. There are
2729 set to highlight commands only available in Quake: >
2732 set to highlight commands only available in Quake 2: >
2735 set to highlight commands only available in Quake 3 Arena: >
2738 Any combination of these three variables is legal, but might highlight more
2744 The parsing of R code for syntax highlight starts 40 lines backwards, but you
2755 and highlight as functions all keywords followed by an opening parenthesis: >
2761 To disable syntax highlight of YAML header, add to your |vimrc|: >
2767 To highlight R code in knitr chunk headers: >
2773 `rmd_fenced_languages`. For example to properly highlight both R and Python,
2780 To highlight R code in knitr chunk headers, add to your |vimrc|: >
2787 few commands and options to the ones already available. To highlight these
2868 This will highlight trailing whitespace and tabs preceded by a space character
3107 speed up displaying. The disadvantage is that highlight errors may appear.
3528 is a difficult language to highlight correctly. A way to suppress error
3651 one highlight group for one syntax item, or put all items into one group.
3656 Note that a syntax group and a highlight group are similar. For a highlight
3657 group you will have given highlight attributes. These attributes will be used
3801 and use one highlight group, and once contained, and use a different
3802 highlight group. Example: >
3806 highlight group is used. When finding "tag" in a syntax item that
3927 contained items to highlight parts of the end pattern, without causing
3951 further, it is only used to highlight the <> items. The htmlScript
3958 highlight it differently. But when the xmlFold region is nested (it
3978 "matchgroup" can be used to highlight the start and/or end pattern
3981 < This will highlight the quotes with the "Quote" group, and the text in
4241 of that item. For example, to highlight a word in a C comment after loading
4268 This will highlight "Foo" and "Bar" differently, and only when there is a
4405 Example (match a comment but don't highlight the /* and */): >
4416 sssrrreee highlight start/region/end ("Foo", "Exa" and "Bar")
4806 13. Highlight command *:highlight* *:hi* *E28* *E411* *E415*
4808 There are three types of highlight groups:
4813 - The ones used for the 'highlight' option.
4817 This will open a new window containing all highlight group names, displayed
4847 |:highlight-link| associations, use another name, e.g.
4862 :hi[ghlight] List all the current highlight groups that have
4866 List one highlight group.
4868 *highlight-clear*
4877 Disable the highlighting for one highlight group. It
4881 Add a highlight group, or change the highlighting for
4885 See |highlight-args| for the {key}={arg} arguments.
4886 See |:highlight-default| for the optional [default]
4889 Normally a highlight group is added once when starting up. This sets the
4891 highlight commands to change the arguments that you want to set to non-default
4896 a file with ":highlight" commands such as this: >
4905 *:highlight-verbose*
4906 When listing a highlight group and 'verbose' is non-zero, the listing will
4915 *highlight-args* *E416* *E417* *E423*
4925 1. highlight arguments for normal terminals
4930 term={attr-list} *attr-list* *highlight-term* *E418*
4949 with |highlight-guisp| or |highlight-ctermul|. You can try these
4955 start={term-list} *highlight-start* *E422*
4956 stop={term-list} *term-list* *highlight-stop*
4963 terminal to highlight this area. The escape sequence
4984 2. highlight arguments for color terminals
4986 cterm={attr-list} *highlight-cterm*
4995 ctermfg={color-nr} *highlight-ctermfg* *E421*
4996 ctermbg={color-nr} *highlight-ctermbg*
4997 ctermul={color-nr} *highlight-ctermul*
5071 :highlight Normal ctermfg=grey ctermbg=darkblue
5075 explicitly. This causes the highlight groups that depend on
5091 :highlight Visual ctermfg=bg ctermbg=fg
5097 3. highlight arguments for the GUI
5099 gui={attr-list} *highlight-gui*
5106 font={font-name} *highlight-font*
5127 guifg={color-name} *highlight-guifg*
5128 guibg={color-name} *highlight-guibg*
5129 guisp={color-name} *highlight-guisp*
5165 :highlight Comment guifg=#11f0c3 guibg=#ff00ff
5174 :highlight Comment guifg=alt_turquoise guibg=magenta
5191 :highlight Comment guifg=css_turquoise
5194 *highlight-groups* *highlight-default*
5196 'highlight' option default. Note that the highlighting depends on the value
5197 of 'background'. You can see the current settings with the ":highlight"
5340 Win32 GUI. Only three highlight arguments have any effect here: font, guibg,
5346 Applicable highlight arguments: font, guibg, guifg.
5356 Applicable highlight arguments: guibg, guifg.
5360 Applicable highlight arguments: font, guibg, guifg.
5368 14. Linking groups *:hi-link* *:highlight-link* *E412* *E413*
5371 can do this more easily by linking the groups into one common highlight
5385 - As soon as you use a ":highlight" command for a linked group, the link is
5387 - If there are already highlight settings for the {from-group}, the link is
5388 not made, unless the '!' is given. For a ":highlight link" command in a
5392 *:hi-default* *:highlight-default*
5399 :highlight default link cComment Comment
5401 :highlight link cComment Question
5405 To have a link survive `:highlight clear`, which is useful if you have
5409 highlight! default link cComment Question
5452 This doesn't change the colors for the 'highlight' option.
5476 highlight comment ctermfg=darkgreen guifg=darkgreen
5478 highlight comment ctermfg=green guifg=green
5504 16. Highlighting tags *tag-highlight*
5506 If you want to highlight all the tags in your file, you can use the following
5509 <F11> -- Generate tags.vim file, and highlight tags.
5510 <F12> -- Just highlight tags based on existing tags.vim file.
5523 # Make a highlight file for types. Requires Exuberant ctags and awk