Lines Matching refs:in
10 get this type of file highlighted. Also see |:syn-define| in the reference
34 finding a syntax file in $VIMRUNTIME/syntax for a language that is similar.
43 This isn't required in the final syntax file, but very useful when
46 There are more simplifications in this chapter. If you are writing a syntax
60 To list the items in a specific syntax group use: >
64 This also can be used to list clusters (explained in |44.8|). Just include
65 the @ in the name.
79 The ":syntax case" commands can appear anywhere in a syntax file and affect
81 case" command in your syntax file; if you work with an unusual language that
119 The characters used in a keyword must be in the 'iskeyword' option. If you
122 The x language uses the '-' character in keywords. This is how it's done:
129 that is not wanted, don't define a keyword but use a match (explained in the
155 used to surround the pattern (like how it's done in a ":substitute" command).
169 In the example x language, strings are enclosed in double quotation marks (").
178 "A string with a double quote (\") in it" ~
180 This creates a problem: The double quotation marks in the middle of the string
182 quotes in the string. Do this with the skip keyword: >
187 special character in search patterns.
194 it is easier to use nested items, as is explained in the next section.
203 You want to highlight TODO in big yellow letters, even though it is in a
220 The x language defines code blocks in curly braces. And a code block may
233 First a xBlock starts at the { in the first line. In the second line another
236 second level xBlock region. Then a } is found in the next line, which matches
238 } is included in the nested region, it is hidden from the first xBlock region.
280 All syntax items will be contained in this one. It also contains itself, but
294 The x language has statements in this form:
299 "then" might also appear in other places, where they get different
308 For example, in this text:
316 appear in between the items. Similar arguments are "skipnl", which allows a
317 line break in between the items, and "skipempty", which allows empty lines.
327 group name specified. To highlight the text enclosed in parentheses () with
335 region with a different highlight group (in this case, the xParen group): >
346 A side effect of using "matchgroup" is that contained items will not match in
354 nested () items, which should be highlighted in the same way. You must make
364 can appear in either of them, but take over the highlighting of the item it is
365 contained in. The "transparent" argument causes this.
368 that contained items are not found in the match with the start item then.
389 result is that in this text:
410 doesn't match in the same line. Without "oneline" Vim does _not_
412 when the end pattern doesn't match in the rest of the file.
418 This starts with a # in the first column and continues until the end of the
427 contained in it (namely xLineContinue) lets it go on for more than one line.
435 pattern. For example, you want to highlight "end" in xPreProc, but only at
490 want to write two syntax files, you can have the C++ syntax file read in the
500 For example, add keywords that are not used in C: >
504 This works just like in any other syntax file.
507 a documentation section in POD format, and a program written in Perl itself.
509 You want to define the POD syntax in one file, and use it from the Perl
510 syntax file. The ":syntax include" command reads in a syntax file and stores
511 the elements it defined in a syntax cluster. For Perl, the statements are as
517 When "=head" is found in a Perl file, the perlPOD region starts. In this
519 items in the pod.vim syntax files will match here. When "=cut" is found, the
520 region ends and we go back to the items defined in the Perl file.
522 command in the included file. And an argument such as "contains=ALL" will
523 only contain items defined in the included file, not in the file that includes
526 expands it to a full path (:p) and then takes the head (:h). This results in
527 the directory name of the file. This causes the pod.vim file in the same
534 straight through. Vim does not have it so easy. It must start in the middle,
551 If it cannot figure out where it is in that space, it starts looking farther
564 If your programming language does not have C-style comments in it, you can try
572 backwards in the file.
597 In this example, the NONE tells Vim that you are not in any special syntax
607 More about synchronizing in the reference manual: |:syn-sync|.
612 When your new syntax file is ready to be used, drop it in a "syntax" directory
613 in 'runtimepath'. For Unix that would be "~/.vim/syntax".
625 be included in the next Vim version!
631 syntax file works, but is missing some items, you can add items in a separate
634 Write syntax commands in your file, possibly using group names from the
640 "c.vim". Place it in a directory near the end of 'runtimepath'. This makes
665 and digits. Don't make it too long, it is used in many places: The name of
670 syntax file, earlier in 'runtimepath' was already loaded: >
681 'expandtab', etc. These belong in a filetype plugin.