Lines Matching refs:be
10 color. Those parts can be specific keywords or text matching a pattern. Vim
12 limitations. Lexical highlighting might be a better name, but since everybody
88 of 'background' will not be set until the GUI window is opened, which is after
89 reading the |gvimrc|. This will cause the wrong default highlighting to be
192 That's it. The next time you edit a C file the Comment color will be
196 All the "*.vim" files in this directory will be used, for example:
212 A syntax group name is to be used for syntax items that match the same kind of
220 To be able to allow each user to pick their favorite set of colors, there must
221 be preferred names for highlight groups that are common for many languages.
279 can be used for the same group.
281 The following names are reserved and cannot be used as a group name:
356 | file type can be recognized, and set 'filetype'.
368 triggered. This can be used to change the highlighting for a specific
378 colors should be exactly the same as you see them in Vim. With
390 options listed below can be enabled or disabled by setting them explicitly to
398 features such as conceal support will not function, and the colors may be
408 and last line to be converted. Example, using the last set Visual area: >
583 line numbers are shown in the generated content. Specify regions to be
616 Internet Explorer, will either copy the text intended not to be copyable, or
618 standards-based method, and there will be much less markup.
628 <input> elements may be pasted into some applications and can be difficult to
642 they will not be openable without a foldcolumn.
650 longer guaranteed to be unique. Set g:html_id_expr to an expression Vim can
652 so that the full IDs will be unique even when combined with other content in a
661 Note, when converting a diff view to HTML, the expression will only be
683 characters can be included literally (see |g:html_expand_tabs|).
708 Force tabs to be expanded: >
713 |g:html_use_encoding| for any content which will be placed on a web server.
717 'encoding' is always used for certain 'buftype' values. 'fileencoding' will be
723 encodings that may not be automatically detected by default (see options
735 name of the charset to be used. It is recommended to set this variable to
736 something widely supported, like UTF-8, for anything you will be hosting on a
776 g:html_font. If this option is set to a string, then the value will be
830 by default. Syntax highlighting for other script languages can be installed
855 Files matching "*.i" could be Progress or Assembly. If the automatic detection
878 Replace "nasm" with the name of the real assembly syntax. This line must be
879 one of the first five lines in the file. No non-white text must be
886 The syntax type can always be overruled for a specific buffer by setting the
891 the global variable asmsyntax is used. This can be seen as a default assembly
914 *.asp and *.asa files could be either Perl or Visual Basic script. Since it's
930 Some special violation of coding standards will be signalled when one specify
936 Syntax folding can be enabled at various levels through the variables
938 source blocks and SQL can be CPU intensive.
942 Folding can be enabled at source block level as if, while, for ,... The
946 Folding can be enabled for embedded SQL blocks as SELECT, SELECTDO,
960 which one should be used, Vim checks for the string "VB_Name" in the first
961 five lines of the file. If it is not found, filetype will be "basic",
962 otherwise "vb". Files with the ".frm" extension will always be seen as Visual
991 forces syncing from the start of the file, can be slow
1020 you have a long "#if 0" construct it will not be highlighted correctly.
1031 ANSI constants will be highlighted with the "cConstant" group. This includes
1041 in the "after" directory in 'runtimepath'. For Unix this would be
1087 but additional symbols can be highlighted by adding them to the
1088 |g:clojure_syntax_keywords| variable. The value should be a |Dictionary| of
1103 "clojure.core" will not be highlighted by default. This is useful for
1110 list, vector or map that extends over more than one line can be folded using
1176 will be classified as tcsh, UNLESS the "filetype_csh" variable exists. If the
1177 "filetype_csh" variable exists, the filetype will be set to the value of the
1203 Files matching "*.w" could be Progress or cweb. If the automatic detection
1244 The diff highlighting normally finds translated headers. This can be slow if
1268 are using the "b:docbk_type" variable should be set. Vim does this for you
1291 this should have the value 1, and for Windows 2000 it should be 2.
1299 A second option covers whether *.btm files should be detected as type
1314 There are a few of ways to turn on doxygen formatting. It can be done
1321 It can also be done automatically for C, C++, C#, IDL and PHP files by setting
1343 There are also some highlight groups worth mentioning as they can be useful in
1361 this is annoying, it can be turned off by setting: >
1370 delimiters % and ;. This can be turned off by setting: >
1409 experimentally handled by some compilers can be enabled by: >
1447 file is determined to be Euphoria based on keywords in the file, then the
1448 filetype will be set as Euphoria. Otherwise, the filetype will default to
1478 file is determined to be Euphoria based on keywords in the file, then the
1479 filetype will be set as Euphoria. Otherwise, the filetype will default to
1540 should be appropriate for most users most of the time because Fortran 2008 is
1544 Fortran code can be in either fixed or free source form. Note that the
1545 syntax highlighting will not be correct if the form is incorrectly set.
1570 are detected, then the file is assumed to be in fixed source form. The
1585 mean that the syntax file will not be able to detect incorrect margins.
1596 then fold regions will also be defined for do loops, if blocks, and select
1600 then fold regions will also be defined for three or more consecutive comment
1601 lines. Note that defining fold regions can be slow for large files.
1612 then the syntax coloring will be more precise but slower. In particular,
1613 statement labels used in do, goto and arithmetic if statements will be
1624 other legacy features excluded from F will be highlighted as todo items and
1625 that free source form will be assumed.
1627 The dialect can be selected in various ways. If all your fortran files use
1651 files may be legacy code but your newer ones may be F codes, and you would
1657 now-obsolete values "f77", "f90", "f95", or "elf". Such settings will be
1669 strings are not recognized. Some keywords may be highlighted incorrectly
1761 will force TeX highlighting for a particular buffer. It has to be
1828 written such that it should be trivial to include it. To do so add the
1845 this (which is recommended if you want function names to be recognizable in a
1849 Of course, the ctermfg can be a different color if you choose.
1856 Lastly, it should be noted that the opening and closing characters to begin a
1857 block of HTML/OS code can either be << or [[ and >> or ]], respectively.
1865 To have *.inc files be recognized as IA64, add this to your .vimrc file: >
1873 to be highlighted add this to your vim startup: >
1878 you intend your program to be targeted to a Glulx/Glk environment you
1916 idlsyntax_showerror Show IDL errors (can be rather intrusive, but
1950 supposed to be named (with respect to upper and lowercase), use >
1953 declarations to be highlighted create your own definitions by changing the
1958 only be used for debugging. Therefore it is possible to highlight debugging
1962 The result will be that those statements are highlighted as 'Special'
2031 may be changed by the user if s/he is experiencing synchronization
2098 assert the new efuns after v22 to be invalid, don't set this variable when
2113 instead, and the name of your source file should be *.pike
2118 The Lua syntax file can be used for versions 4.0, 5.0, 5.1 and 5.2 (5.2 is
2148 errors. However, this may be too much coloring for you. You can turn this
2158 The standard set of packages' functions as supplied in Maple V release 4 may be
2181 Empty *.m files will automatically be presumed to be Matlab files unless you
2204 Unmatched double quotes can be recognized and highlighted as errors: >
2212 Unknown builtin functions can be recognized and highlighted as errors. If you
2267 features for groff, arrange for files to be recognized as groff (see
2273 Solaris. Groff macro and request names can be longer than 2 characters and
2278 \[year]. Macro requests can be longer than 2 characters, for example, GNU mm
2294 algorithm that can be easily upset if you don't follow the rules given above.
2298 vertical space input will be output as is.
2300 Therefore, you should be careful about not using more space between sentences
2327 Finally, there is a |groff.vim| syntax file that can be used for enabling
2358 sections, but this is relatively slow and much too colourful to be able to
2361 The newest version of the papp.vim syntax file can usually be found at
2367 Files matching "*.p" could be Progress or Pascal and those matching "*.pp"
2368 could be Puppet or Pascal. If the automatic detection doesn't work for you,
2414 will be highlighted as Error. >
2441 If you do not want complex things like '@{${"foo"}}' to be parsed: >
2447 The coloring strings can be changed. By default strings and qq friends will be
2449 perl_string_as_statement, it will be highlighted as in the second line.
2458 synchronization and should only be needed in case it fails to work properly.
2633 cause Vim to slow down. In an attempt to be machine friendly font names and
2635 explicitly with either of these this should be ok. If you want them to be
2645 operators can be highlighted differently they have to be highlighted one way
2646 or the other. By default they are treated as logical operators. They can be
2681 Files matching "*.w" could be Progress or cweb. If the automatic detection
2685 The same happens for "*.i", which could be assembly, and "*.p", which could be
2727 be set for the following effects:
2770 By default, chunks of R code will be highlighted following the rules of R
2799 language for kubernetes, but can be applied to almost anything. Files with
2839 Vim tries to guess what type a ".r" file is. If it can't be detected (from
2857 Operators can be highlighted by defining "ruby_operators": >
2864 Whitespace errors can be highlighted by defining "ruby_space_errors": >
2869 as errors. This can be refined by defining "ruby_no_trail_space_error" and
2876 Folding can be enabled by defining "ruby_fold": >
2919 of the block it closes. While useful, this feature can be expensive; if you
2925 In this case the same color will be used for all control keywords.
2935 Ideally, this value should be a number of lines large enough to embrace your
2961 case-sensitive (which was not so before), and that all keywords can be
3054 that shelltype is used. However some files (ex. .profile) are known to be
3101 If you don't have much to synchronize on, displaying can be very slow. To
3102 reduce this, the "sh_maxlines" internal variable can be set. Example: >
3138 be highlighted using the awk highlighting syntax. Clearly this may be
3148 sections and subsections will be highlighted as statements but not
3152 like temperature or pressure to be highlighted as Type, not as a
3170 PRESETting variables, syncing may be critical. If your computer is
3259 prefer that spell checking be disabled in comments in LaTeX files. To do
3279 terminate properly, zones delineated by $..$ and $$..$$ cannot be synchronized
3294 if any, is the text at the top of the screen supposed to be in?).
3307 synchronization. The result will be much faster syntax highlighting; the
3309 folding, and you will be missing syntax-based error checking.
3352 errors where none actually are. If this proves to be a problem for you,
3355 and all error checking by <syntax/tex.vim> will be suppressed.
3390 number of character sequences can be translated into appropriate utf-8 glyphs,
3392 superscripts and subscripts in MathZones. Not all characters can be made into
3414 substitution will not be made.
3424 then the file will be treated as a "sty" file, so the "_"
3425 will be allowed as part of keywords
3428 then the file will be treated as a "sty" file, so the "_"
3429 will be allowed as part of keywords
3432 * If g:tex_isk exists, then it will be used for the local 'iskeyword'
3433 * Else the local 'iskeyword' will be set to 48-57,a-z,A-Z,192-255
3467 want [] and () to be checked for mismatches, try using >
3487 g:vimsyn_minlines variable. The g:vimsyn_maxlines variable may be used to
3527 Not all error highlighting that syntax/vim.vim does may be correct; Vim script
3552 Xml namespaces are highlighted by default. This can be inhibited by
3559 start and end tags. This can be turned on by >
3599 plain scalar contents, treat plain scalar (which can actually be only string
3602 will be highlighted specially. Supported schemas are
3644 "skip" regexp pattern can be used to avoid matching the "end" pattern.
3646 Several syntax ITEMs can be put into one syntax GROUP. For a syntax group
3650 "Comment" will be in bold font and have a blue color. You are free to make
3657 group you will have given highlight attributes. These attributes will be used
3712 This defines where spell checking is to be done for text that is not
3723 To activate spell checking the 'spell' option must be set.
3747 If no argument is given, the current value will be output.
3750 and also determines where |:syn-keyword| will be checked for a new
3770 The {options} can be given anywhere in the line. They will apply to
3782 Don't forget that a keyword can only be recognized if all the
3784 isn't, the keyword will never be recognized.
3785 Multi-byte characters can also be used. These do not have to be in
3799 The same keyword can be defined multiple times, when its containment
3823 extend a containing match or region. Must be
3868 useful for end patterns. Must be given before
3881 The start/skip/end patterns and the options can be given in any order.
3882 There can be zero or one skip pattern. There must be one or more
3939 The "keepend" behavior can be changed by using the "extend" argument.
3941 "keepend", the "keepend" is ignored and the containing region will be
3943 This can be used to have some contained items extend a region while
3956 < This defines a region with "keepend", so that its end cannot be
3970 contained matches from extending the match or region. It can be
3973 from extending the containing match or region. It can be used if
3975 "excludenl" must be given before the pattern it applies to.
3978 "matchgroup" can be used to highlight the start and/or end pattern
3988 contained items of the region are not used. This can be used to avoid
4009 The common ones are explained here. The arguments may be given in any order
4010 and may be mixed with patterns.
4013 can not be used for all commands:
4020 These arguments can be used for all three commands:
4036 concealable items in the current line are displayed unconcealed to be able to
4045 'conceallevel' option. The ends of a region can only be concealed separately
4053 character defined in the 'listchars' option is used. The character cannot be
4060 When the "contained" argument is given, this item will not be recognized at
4069 If the "display" argument is given, this item will be skipped when the
4070 detected highlighting will not be displayed. This will speed up highlighting,
4072 to be displayed.
4089 Examples, for the C language, where "display" can be used:
4096 If the "transparent" argument is given, this item will not be highlighted
4113 it does not contain anything. If the "contains=NONE" argument would be left
4115 "myWord" to be contained, which will be highlighted as a Comment. This
4148 the next line anyway. A contained item can be used to recognize a line
4153 pattern must be found in the same line as where the start pattern ends. The
4156 be within one line. This can't be changed by a skip pattern that matches a
4181 groups will be allowed to begin inside the item (they may extend past the
4183 regions. If there is no "contains" argument, no groups will be contained in
4184 this item. The group names do not need to be defined before they can be used
4189 groups will be accepted inside the item.
4193 groups will be accepted inside the item, except the ones that
4199 groups will be accepted that don't have the "contained"
4206 all groups will be accepted that have the "contained"
4213 The {group-name} in the "contains" list can be a pattern. All group names
4214 that match the pattern will be included (or excluded, if "ALLBUT" is used).
4217 The matching will be done at moment the syntax command is executed. Groups
4218 that are defined later will not be matched. Also, if the current syntax
4225 region. If this is not wanted, the "matchgroup" argument can be used
4226 |:syn-matchgroup|. The "ms=" and "me=" offsets can be used to change the
4234 item will be allowed to begin inside these groups. This works as if the
4237 The {group-name}... can be used just like for "contains", as explained above.
4239 This is useful when adding a syntax item afterwards. An item can be told to
4240 be included inside an already existing item, without changing the definition
4248 appear. A "contains" argument may also be added as usual. Don't forget that
4258 If the "nextgroup" argument is given, the mentioned syntax groups will be
4261 will be used, even when it is not mentioned in the "contains" field of the
4276 when ".*" would be used, the "asdf" in between "Bar" and "Foo" would be
4285 These arguments are only used in combination with "nextgroup". They can be
4294 When "skipnl" is present, the match with nextgroup may be found in the next
4296 line! When "skipnl" is not present, the nextgroup will only be found after
4322 off" returns to the normal state where the "conceal" flag must be
4331 In the syntax commands, a pattern must be surrounded by two identical
4348 The pattern can be followed by a character offset. This can be used to
4352 pattern can be used to tell where to continue looking for an end pattern.
4355 The {what} can be one of seven strings:
4365 The {offset} can be:
4386 Offsets can be concatenated, with a ',' in between. Example: >
4393 - There must be no white space between the pattern and the character
4395 - The highlighted area will never be outside of the matched text.
4397 pattern may be detected when the highlighting should already have stopped.
4401 - The start of a match cannot be in a line other than where the pattern
4425 be present, but is not considered part of the match. An offset of "lc=n" will
4427 characters which have already been matched in previous patterns to also be
4428 used as leading context for this match. This can be used, for instance, to
4471 \z(\) Marks the sub-expression as "external", meaning that it can be
4482 shells. This effect can be achieved with the "\z" special regular expression
4483 items, which marks a sub-expression as "external", in the sense that it can be
4485 example, for instance, can be done like this: >
4488 As can be seen here, the \z actually does double duty. In the start pattern,
4492 also be used in skip patterns: >
4498 Note also that external sub-expressions cannot be accessed as back-references
4503 Note that only matches within a single line can be used. Multi-line matches
4504 cannot be referred to.
4523 A cluster so defined may be referred to in a contains=.., containedin=..,
4556 a related language. Depending on the exact relationship, this can be done in
4559 - If top-level syntax items in the included syntax file are to be
4567 < - If top-level syntax items in the included syntax file are to be
4575 all top-level syntax items in the included file will be added to
4596 Vim wants to be able to start redrawing in any position in the document. To
4618 that many lines backwards. This can be used if the parsing may take a few
4630 start above where the change was made. How many lines can be specified with
4643 The file will be parsed from the start. This makes syntax highlighting
4644 accurate, but can be slow for long files. Vim caches previously parsed text,
4646 when making changes some part of the text needs to be parsed again (worst
4654 For the second method, only the "ccomment" argument needs to be given.
4659 comment, the last region syntax item with the group-name "Comment" will be
4661 An alternate group name can be specified, for example: >
4663 This means that the last item specified with "syn region javaComment" will be
4667 The "maxlines" argument can be used to restrict the search to a number of
4668 lines. The "minlines" argument can be used to at least start a number of
4681 For the third method, only the "minlines={N}" argument needs to be given.
4683 means {N} extra lines need to be parsed, which makes this method a bit slower.
4694 region, we might be able to know in which syntax item we are. The search
4700 - Keywords cannot be used.
4705 - A line continuation pattern can be given. It is used to decide which group
4706 of lines need to be searched like they were one line. This means that the
4712 continued lines). Otherwise the end is assumed to be at the end of the
4719 There are two ways how a match with a sync pattern can be used:
4722 to be valid there must be specified. This works well when the regions
4725 that is expected to be present just after the match must be specified.
4726 This can be used when the previous method doesn't work well. It's much
4727 slower, because more text needs to be parsed.
4728 Both types of sync patterns can be used at the same time.
4730 Besides the sync patterns, other matches and regions can be specified, to
4734 search for the sync point can be much simpler than figuring out the
4744 must exist for this {group-name}. The first one defined will be used.
4745 "NONE" can be used for when there is no syntax group after the match.
4751 is to be used at the start of the line where searching for the sync
4772 consider the lines to be concatenated.
4802 Note that the ":syntax" command can be abbreviated to ":sy", although ":syn"
4853 < Before the color scheme will be loaded all default
4855 be executed and then the |ColorSchemePre| autocommand
4884 |'runtimepath'| will be loaded.
4892 values. The value "NONE" can be used to switch the value off or go back to
4912 When ":hi clear" is used then the script where this command is used will be
4922 For each type the highlighting can be given. This makes it possible to use
4944 Note that "bold" can be used here and by using a bold font. They
4957 These lists of terminal codes can be used to get
4962 area. It can be anything that you want to send to the
4978 the termcap entry. The codes have to be separated with commas.
4988 The "cterm" argument is likely to be different from "term", when
4990 be underlined, in a color terminal they can be made Blue.
4992 with coloring. To be portable, use only one of "cterm=" OR "ctermfg="
5010 colors for a color-xterm can be changed from the .Xdefaults file.
5073 'background' option will be adjusted automatically, under the
5079 be reloaded, which may reset all colors (including Normal). First
5088 "fg", "bg" and "ul" can be used as color names. This only works after
5094 "fg" and "bg" colors will not be adjusted.
5102 Note that "bold" can be used here and by using a bold font. They
5111 The font-name "NONE" can be used to revert to the default font.
5116 When setting the font for the "Menu" group, the menus will be changed.
5117 When setting the font for the "Tooltip" group, the tooltips will be
5119 All fonts used, except for Menu and Tooltip, should be of the same
5123 put it in single quotes. The single quote cannot be used then.
5140 put it in single quotes. The single quote cannot be used then.
5184 If you want to develop a color list that can be relied on by others,
5187 '$VIMRUNTIME/colors/lists/csscolors.vim'. This list would be sourced
5291 This will be combined with the highlighting used otherwise.
5294 This will be combined with the highlighting used otherwise.
5298 This will be combined with the highlighting used otherwise.
5302 This will be combined with the highlighting used otherwise.
5389 sourced file, you don't get an error message. This can be used to skip
5395 will be ignored. Also when there is an existing link.
5402 Without the "default" in the C syntax file, the highlighting would be
5418 This command should be used when you want to switch off syntax highlighting,
5441 $VIMRUNTIME must be valid. See |$VIMRUNTIME|.
5454 Note that the syntax colors that you set in your vimrc file will also be reset
5457 scheme for syntax highlighting will be lost.
5470 the default colors. This way these colors will be used after the ":syntax
5486 Note that when a color scheme is used, there might be some confusion whether
5487 your defined colors are to be used or the colors from the scheme. This
5515 WARNING: The longer the tags file, the slower this will be, and the more
5518 Only highlighting typedefs, unions and structs can be done too. For this you
5543 private syntax setting. A possible example would be to edit LaTeX source
5590 be wrong.
5608 To get 16 colors or more, get the newest xterm version (which should be
5717 If your syntax causes redrawing to be slow, here are a few hints on making it