Lines Matching refs:that
13 calls it syntax highlighting we'll stick with that.
66 will start soon. See |'go-M'| about avoiding that.
82 NOTE: The syntax files on MS-Windows have lines that end in <CR><NL>.
96 NOTE: Using ":gui" in the |gvimrc| means that "gvim -f" won't start in the
136 the idea is that only commands for a specific language are included. When a
184 3. Write a Vim script that contains the commands you want to use. For
188 4. Write that file in the "after/syntax" directory. Use the name of the
205 that you write the syntax file in a directory that is early in 'runtimepath'.
206 Vim will only load the first syntax file found, assuming that it sets
212 A syntax group name is to be used for syntax items that match the same kind of
213 thing. These are then linked to a highlight group that specifies the color.
221 be preferred names for highlight groups that are common for many languages.
259 Delimiter character that needs attention
263 *Underlined text that stands out, HTML links
269 *Todo anything that needs extra attention; mostly the
278 Note that highlight group names are not case sensitive. "String" and "string"
291 This explains the details that happen when the command ":syntax enable" is
306 | | existing colors, ":syntax enable" only sets groups that weren't
374 2html is not a syntax file itself, but a script that converts the current
381 |g:html_dynamic_folds| enabled, you can show or hide the text that is folded
468 run interactively, so that too much time is not taken to redraw as the script
473 Note that the -s flag prevents loading your .vimrc and any plugins, so you
474 need to explicitly source/enable anything that will affect the HTML
504 inserted for that purpose if no line numbers are shown. This ID attribute
536 Either of the following commands will ensure that all text in the buffer is
549 Either of these commands will ensure that all text in the buffer is included
615 generated-content method is used. This means that old browsers, notably
639 Note that old browsers (notably Internet Explorer 6) will not support this
641 normal CSS1 styling so that the folds show up correctly for this browser, but
652 so that the full IDs will be unique even when combined with other content in a
702 the source document. Note that this can easily break text alignment and
723 encodings that may not be automatically detected by default (see options
739 You can also use this option to omit the line that specifies the charset
753 This is a dictionary of charset-encoding pairs that will replace existing
770 Note that documents encoded in either UTF-32 or UTF-16 have known
800 Vim stores the name of the syntax that has been loaded in the
861 There are many types of assembly languages that all use the same file name
863 line in the assembly file that Vim will recognize. Currently these syntax
880 immediately before or after this text. Note that specifying asmsyntax=foo is
881 equivalent to setting ft=foo in a |modeline|, and that in case of a conflict
1016 disadvantage of using a larger number is that redrawing can become slow.
1018 When using the "#if 0" / "#endif" comment highlighting, notice that this only
1049 the C syntax file. See |c.vim| for all the settings that are available for C.
1059 that are available. Additionally there is:
1104 namespaces that have set `(:refer-clojure :only [])`
1110 list, vector or map that extends over more than one line can be folded using
1122 Note that this option will not correctly highlight stacked discard macros
1160 This covers the shell named "csh". Note that on some systems tcsh is actually
1183 Cynlib files are C++ files that use the Cynlib class library to enable
1234 To highlight nonstandard extensions that does not begin with X-, set >
1236 Note that this may cause wrong highlight.
1256 the command. It adds a few keywords that are generally ignored by most
1326 There are a couple of variables that have an effect on syntax highlighting, and
1408 Support for ISE's proposed new creation syntax that is already
1486 NOTE: this site currently doesn't work, on Wikipedia is mentioned that
1495 and so on. It also includes some keymaps that are disabled by default.
1497 If you want to enable the keymaps that make "j" and "k" and the cursor keys
1522 Note that the form.vim syntax file implements FORM preprocessor commands and
1544 Fortran code can be in either fixed or free source form. Note that the
1557 file. For more information on ftplugin files, see |ftplugin|. Note that this
1572 file that begins with 500 or more full-line comments, the script may
1573 incorrectly decide that the fortran code is in fixed form. If that happens,
1585 mean that the syntax file will not be able to detect incorrect margins.
1591 to instruct the syntax script to define fold regions for program units, that
1601 lines. Note that defining fold regions can be slow for large files.
1623 If you use F, the advantage of setting the dialect appropriately is that
1625 that free source form will be assumed.
1644 Note that this will work only if the "filetype plugin indent on" command
1661 The syntax/fortran.vim script contains embedded comments that tell you how to
1678 In order for Vim to recognize Fvwm configuration files that do not match
1716 under that heading for examples of use and configuration. The purpose
1743 directives, and flags lines that start with # but are not valid
1779 Note that the same is true for argument (or attribute) names. Known attribute
1786 only if used as a link (that is, it must include a href as in
1822 programming languages. Note that only JavaScript and Visual Basic are currently
1828 written such that it should be trivial to include it. To do so add the
1829 following two lines to the syntax coloring file for that language
1835 Now you just need to make sure that you add all regions that contain
1851 Another issues that HTML/OS runs into is that there is no special filetype to
1852 signify that it is a file with HTML/OS coding. You can change this by opening
1856 Lastly, it should be noted that the opening and closing characters to begin a
1876 By default it is assumed that Inform programs are Z-machine targeted,
1906 There are some Microsoft extensions to idl files that are here. Some of them
1940 Check the javaid.vim file for a list of all the packages that are supported.
1946 If you write function declarations that are always indented by either
1962 The result will be that those statements are highlighted as 'Special'
1970 Javadoc is a program that takes special comments out of Java program files and
1987 actually have Javadoc comments that include either Javascript or embedded
2005 number is that redrawing can become slow.
2089 For a C file that is recognized as LPC:
2164 choosing a variable/package from the table below and setting that variable to
2244 many dialects, like COLUMN or CHAR, that don't exist in N1QL.
2272 Groff is different from the old AT&T n/troff that you may still find in
2293 The reason behind these unusual tips is that g/n/troff have a line breaking
2294 algorithm that can be easily upset if you don't follow the rules given above.
2309 Another technique to detect extra spacing and other errors that will interfere
2327 Finally, there is a |groff.vim| syntax file that can be used for enabling
2344 contain very long structures that Vim does not synchronize anymore.
2408 To ensure that strings are defined on a single line, you can define the
2461 out the line that causes the mistake.
2658 In order for Vim to recognize printcap/termcap files that do not match
2792 This will add highlighting for the commands that BASH (version 2.05a and
2826 Note that folding can cause performance issues on some platforms.
2837 number is that redrawing can become slow.
2960 The new standard, SDL-2000, specifies that all identifiers are
2961 case-sensitive (which was not so before), and that all keywords can be
2985 also a good idea to set the tab width to one character; by doing that,
2991 command. This means that, as far as this syntax file is concerned,
3010 Note that the same is true for argument (or attribute) names. Known attribute
3045 Vim attempts to determine which shell type is in use by specifying that
3054 that shelltype is used. However some files (ex. .profile) are known to be
3099 number is that redrawing can become slow.
3107 speed up displaying. The disadvantage is that highlight errors may appear.
3153 plain Identifier. Included are the types that are usually found in
3197 is set. If you want VIM to assume that no backslash quote constructs exist add
3211 tcsh_minlines is 100. The disadvantage of using a larger number is that
3259 prefer that spell checking be disabled in comments in LaTeX files. To do
3311 You may decide that some syntax is acceptable; you may use the following table
3334 package you'll often wish that the distributed syntax/tex.vim would support
3337 by syntax/tex.vim. Please consider uploading any extensions that you write,
3369 The "starform" variable, if true, implies that your new math group
3508 By default, g:vimsyn_embed is a string supporting interpreters that your vim
3527 Not all error highlighting that syntax/vim.vim does may be correct; Vim script
3545 Note that spaces and underscores in option names are not supported. Use
3587 It will work with XPM files that have one character per pixel only and you
3598 non-specific tags. For user this means that YAML parser may, depending on
3615 Note that schemas are not actually limited to plain scalars, but this is the
3648 to define a "/* .. */" comment and another one that defines a "// .." comment,
3649 and put them both in the "Comment" group. You can then specify that a
3656 Note that a syntax group and a highlight group are similar. For a highlight
3660 In case more than one item matches at the same position, the one that was
3662 using an item that matches the same text. But a keyword always goes before a
3674 3. An item that starts in an earlier position has priority over items that
3683 "ignore". Note that any items before this are not affected, and all
3700 for the lowest level contained on the line that is followed by a
3712 This defines where spell checking is to be done for text that is not
3771 all keywords given, also for options that come after a keyword.
3782 Don't forget that a keyword can only be recognized if all the
3793 Note that when you have a keyword that is the same as an option (even
3794 one that isn't allowed here), you can not use it. Use a match
3806 highlight group is used. When finding "tag" in a syntax item that
3828 {pattern} The search pattern that defines the match.
3830 Note that the pattern may match more than one
3870 start={start-pattern} The search pattern that defines the start of
3872 skip={skip-pattern} The search pattern that defines text inside
3875 end={end-pattern} The search pattern that defines the end of
3883 start and end patterns. This means that you can omit the skip
3890 patterns. The last one that matches is used. The same is true for
3894 Offsets are not used for this. This implies that the match for the
3913 repeats that with "\{-}" (repeat as few as possible).
3917 This is useful for nesting. For example, a region that starts with
3928 that to skip the match with the end pattern. Example: >
3940 When an item with "extend" is contained in an item that uses
3956 < This defines a region with "keepend", so that its end cannot be
3959 includes itself), the "extend" applies, so that the "</a>" of a nested
3960 region only ends that region, and not the one it is contained in.
3964 to match the end-of-line, it will make a region item that it is
3967 that would normally stop at the end of the line. This is the default
3972 2. Use "excludenl" in the contained item. This will keep that match
3983 The "matchgroup" is used for all start and end patterns that follow,
3987 In a start or end pattern that is highlighted with "matchgroup" the
3989 that a contained item matches in the start or end pattern match. When
3991 match that is highlighted with "matchgroup".
4008 The :syntax commands that define syntax items take a number of arguments.
4071 by skipping this item when only finding the syntax state for the text that is
4074 Generally, you can use "display" for match and region items that meet these
4079 - The item does not contain items that continue past the end of the line or
4083 because it may make that preprocessor match shorter.
4084 - The item does not allow other items to match that didn't match otherwise,
4085 and that item may extend the match too far. Example for C: A match for a
4086 "//" comment can't use "display", because a "/*" inside that comment would
4098 is useful for syntax items that don't need any highlighting but are used
4103 avoid that unwanted items are contained, use "contains=NONE". Example, which
4145 The "oneline" argument indicates that the region does not cross a line
4147 region has a contained item that does cross a line boundary, it continues on
4155 means that the end of the start pattern and the start of the end pattern must
4156 be within one line. This can't be changed by a skip pattern that matches a
4193 groups will be accepted inside the item, except the ones that
4199 groups will be accepted that don't have the "contained"
4202 Like "TOP", but excluding the groups that are listed.
4206 all groups will be accepted that have the "contained"
4209 Like "CONTAINED", but excluding the groups that are
4214 that match the pattern will be included (or excluded, if "ALLBUT" is used).
4218 that are defined later will not be matched. Also, if the current syntax
4227 region where contained items do match. Note that this may also limit the
4228 area that is highlighted
4235 containing item has a "contains=" argument that includes this item.
4241 of that item. For example, to highlight a word in a C comment after loading
4244 Note that "contained" is also used, to avoid that the item matches at the top
4248 appear. A "contains" argument may also be added as usual. Don't forget that
4292 next group that matches the white space.
4301 for a match again. This means that matching a next group and skipping white
4308 Note that the "[^ \t].*" match matches all non-white text. Thus it would also
4309 match "endif". Therefore the "endif" match is put last, so that it takes
4311 Note that this example doesn't work for nested "if"s. You need to add
4312 "contains" arguments to make that work (omitted for simplicity of the
4334 use another character that is not used in the pattern. Examples: >
4344 Try to avoid patterns that can match an empty string, such as "[a-z]*".
4424 The "lc" offset specifies leading context -- a part of the pattern that must
4429 specify that an "escaping" character must not precede the match: >
4451 following line though. Using the "\zs" item also requires that the start of
4455 continue in the first character of the next line, also when that character is
4462 Generally this means that the skip pattern should not match any characters
4471 \z(\) Marks the sub-expression as "external", meaning that it can be
4477 Matches the same string that was matched by the corresponding
4483 items, which marks a sub-expression as "external", in the sense that it can be
4495 Note that normal and external sub-expressions are completely orthogonal and
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
4576 that list. >
4583 or "<sfile>") that file is sourced. When it is a relative path
4587 with their own version, without replacing the file that does the
4618 that many lines backwards. This can be used if the parsing may take a few
4621 If the "maxlines={N}" argument is given, the number of lines that are searched
4628 When using a pattern that matches multiple lines, a change in one line may
4634 The result is that redrawing always starts at least one line before where a
4645 so that it's only slow when parsing the text for the first time. However,
4658 When Vim finds that the line where displaying starts is inside a C-style
4660 used. This requires that there is a region with the group-name "Comment"!
4663 This means that the last item specified with "syn region javaComment" will be
4664 used for the detected C comment region. This only works properly if that
4669 lines back (e.g., for when there is some construct that only takes a few
4673 that cross a line and contain a "*/". Since letting strings cross a line
4706 of lines need to be searched like they were one line. This means that the
4708 consecutive lines that contain the continuation pattern.
4721 search for the sync pattern started). The syntax group that is expected
4723 that cross lines cannot contain other regions.
4725 that is expected to be present just after the match must be specified.
4733 [The reason that the sync patterns are given separately, is that mostly the
4741 Define a match that is used for syncing. {group-name} is the
4742 name of a syntax group that follows just after the match. Parsing
4750 Like "grouphere", but {group-name} is the name of a syntax group that
4755 "/*" is found first, you know that you are inside a comment, so the
4756 "groupthere" is "cComment". If "*/" is found first, you know that you
4764 Without a "groupthere" argument. Define a region or match that is
4771 the next line. This means that the search for a sync point will
4774 If the "maxlines={N}" argument is given too, the number of lines that are
4802 Note that the ":syntax" command can be abbreviated to ":sy", although ":syn"
4829 for the file "colors/{name}.vim". The first one that
4862 :hi[ghlight] List all the current highlight groups that have
4890 default values for the highlighting. After that, you can use additional
4891 highlight commands to change the arguments that you want to set to non-default
4900 Note that all settings that are not included remain the same, only the
4944 Note that "bold" can be used here and by using a bold font. They
4962 area. It can be anything that you want to send to the
4971 This is any string of characters, except that it can't start with
5011 Unfortunately this means that it's not possible to get the same colors
5049 8-color terminals ('t_Co' less than 16). The '*' indicates that the
5058 Note that for 16 color ansi style terminals (including xterms), the
5059 numbers in the NR-8 column is used. Here '*' means 'add 8' so that Blue
5062 Note that for some color terminals these names may result in the wrong
5074 condition that the color is recognized and 'background' was not set
5075 explicitly. This causes the highlight groups that depend on
5092 < Note that the colors are used that are valid at the moment this
5102 Note that "bold" can be used here and by using a bold font. They
5104 Note that the attributes are ignored for the "Normal" group.
5176 If you are using a color scheme that relies on named colors and you
5184 If you want to develop a color list that can be relied on by others,
5196 'highlight' option default. Note that the highlighting depends on the value
5211 CursorColumn the screen column that the cursor is in when 'cursorcolumn' is
5214 CursorLine the screen line that the cursor is in when 'cursorline' is
5264 and other characters that do not really exist in the text
5283 Also used for similar items that need to stand out.
5287 Generally: text that is displayed differently from what it
5290 SpellBad Word that is not recognized by the spellchecker. |spell|
5293 SpellCap Word that should start with a capital. |spell|
5296 SpellLocal Word that is recognized by the spellchecker as one that is
5300 SpellRare Word that is recognized by the spellchecker as one that is
5312 StatusLineTermNC status lines of not-current windows that is a |terminal|
5372 group, and give the color attributes only for that group.
5390 links for groups that already have settings.
5420 in a syntax file itself, because syntax is cleared by the autocommands that
5435 the autocommands that load the syntax files: >
5440 See the "nosyntax.vim" file for details. Note that for this to work
5454 Note that the syntax colors that you set in your vimrc file will also be reset
5456 Note that if you are using a color scheme, the colors defined by the color
5464 Note that this uses the 'runtimepath' option.
5469 'runtimepath' which comes after $VIMRUNTIME, so that your settings overrule
5486 Note that when a color scheme is used, there might be some confusion whether
5495 "enable" ":syntax enable" command. Only define colors for groups that
5561 syntax commands executed from that window do not affect other windows on the
5565 is loaded into that window or the file is reloaded.
5641 and try if that works.
5695 emulator, or Eterm. They might work for all xterm-like terminals that use the
5708 that Setup / Font / Enable Bold is NOT enabled.
5718 faster. To see slowness switch on some features that usually interfere, such
5730 This will display a list of syntax patterns that were used, sorted by the time
5753 NAME Name of the syntax item. Note that
5763 literal text specify the size of that text (in bytes):