Lines Matching refs:as
195 If you have multiple files, you can use the filetype as the directory name.
204 version, follow the same steps as for |mysyntaxfile| above. Just make sure
248 Macro same as Define
281 The following names are reserved and cannot be used as a group name:
293 located. This is used here as the variable |$VIMRUNTIME|.
339 Upon loading a file, Vim finds the relevant syntax file as follows:
355 | again with checks like "getline(1) =~ pattern" as to whether the
378 colors should be exactly the same as you see them in Vim. With
398 features such as conceal support will not function, and the colors may be
449 is displayed as three lines with the middle line mentioning the total number
451 When 1, always display all inserted lines as if |g:html_diff_one_file| were
468 run interactively, so that too much time is not taken to redraw as the script
481 as the HTML conversion proceeds. By default, the background color as the
493 highlighting as the line number column in Vim (|hl-LineNr|).
531 from |:syn-cchar| or 'listchars' as appropriate, depending on the current
545 the user to expand the fold as in Vim to see the text inside.
574 folded text will open the fold as if |g:html_hover_unfold| were set.
584 affected in this way as follows:
682 tags. Series of whitespace is shown as in Vim without special markup, and tab
700 are included as-is in the generated HTML. This is useful for when you want to
727 the generated HTML, as recommended by W3C:
733 Default: none, uses IANA name for current 'fileencoding' as above.
756 Detect the HTML charset "windows-1252" as the encoding "8bit-cp1252": >
779 way, "monospace" is added as the fallback generic family name and the entire
780 result used as the font family (using CSS) or font face (if not using CSS).
819 abel_cpp_comments_illegal do not interpret '//' as inline comment leader
831 by the function AntSyntaxScript(), which takes the tag name as first argument
832 and the script syntax file name as second argument. Example: >
839 # everything inside is highlighted as perl
884 highlighting regardless of what is specified as asmsyntax).
891 the global variable asmsyntax is used. This can be seen as a default assembly
906 nasm_loose_syntax unofficial parser allowed syntax not as Error
908 nasm_ctx_outside_macro contexts outside macro not as Error
909 nasm_no_warn potentially risky syntax not as ToDo
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,
962 otherwise "vb". Files with the ".frm" extension will always be seen as Visual
985 *c_no_bracket_error* don't highlight {}; inside [] as errors
986 *c_no_curly_error* don't highlight {}; inside [] and () as errors;
998 *c_no_if0* don't highlight "#if 0" blocks as comments
1037 If you see '{' and '}' highlighted as an error where they are OK, reset the
1075 You can change the highlighting used, e.g., to flag the spaces as an error: >
1149 Most things are the same as |ft-c-syntax|.
1176 will be classified as tcsh, UNLESS the "filetype_csh" variable exists. If the
1299 A second option covers whether *.btm files should be detected as type
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
1395 "NONE", to warn against their accidental use as feature or class names.
1399 lowercase letters as well as outdated ways to capitalize keywords).
1430 The following file extensions are auto-detected as Euphoria file type:
1435 To select syntax highlighting file for Euphoria, as well as for
1436 auto-detecting the *.e and *.E file extensions as Euphoria file type,
1446 specifically set as Euphoria with the g:filetype_euphoria variable, or the
1448 filetype will be set as Euphoria. Otherwise, the filetype will default to
1455 the following extensions are recognized as Erlang files: erl, hrl, yaws.
1472 The following file extensions are auto-detected as Elixir file types:
1477 specifically set as Euphoria with the g:filetype_euphoria variable, or the
1479 filetype will be set as Euphoria. Otherwise, the filetype will default to
1491 editing FlexWiki pages more convenient. FlexWiki considers a newline as the
1571 algorithm should work in the vast majority of cases. In some cases, such as a
1580 Therefore, tabs are marked as errors. Nevertheless, some programmers like
1582 variable fortran_have_tabs in your .vimrc with a command such as >
1589 fortran_fold with a command such as >
1594 also set the variable fortran_fold_conditionals with a command such as >
1598 fortran_fold_multilinecomments with a command such as >
1606 units are not folded because they are seen as not belonging to any program
1610 If you set the variable fortran_more_precise with a command such as >
1614 recognized, as will construct names at the end of a do, if, select or forall
1620 deleted or declared obsolescent in the 2008 standard are highlighted as todo
1624 other legacy features excluded from F will be highlighted as todo items and
1658 silently handled as "f08". Users of "elf" may wish to experiment with "F"
1664 or declared obsolescent in the 2008 standard from being highlighted as todo
1685 as Fvwm2 configuration files, add the following: >
1724 The Haskell syntax files support plain Haskell code as well as literate
1731 To treat True and False as keywords as opposed to ordinary identifiers,
1734 To also treat the names of primitive types as keywords: >
1736 And to treat the names of even more relatively common types as keywords: >
1744 directives as erroneous. This interferes with Haskell's syntax for
1745 operators, as they may start with #. If you want to highlight those
1746 as operators as opposed to errors, put in your .vimrc: >
1768 The coloring scheme for tags in the HTML file works as follows.
1775 Known tag names are colored the same way as statements in C. Unknown tag
1776 names are colored with the same color as the <> or </> respectively which
1784 text is shown: <B> <I> <U> <EM> <STRONG> (<EM> is used as an alias for <I>,
1785 while <STRONG> as an alias for <B>), <H1> - <H6>, <HEAD>, <TITLE> and <A>, but
1786 only if used as a link (that is, it must include a href as in
1820 JavaScript and Visual Basic embedded inside HTML documents are highlighted as
1821 'Special' with statements, comments, strings and so on colored as in standard
1841 The coloring scheme for HTML/OS works as follows:
1865 To have *.inc files be recognized as IA64, add this to your .vimrc file: >
1871 Inform highlighting includes symbols provided by the Inform Library, as
1885 The Inform compiler will flag certain obsolete keywords as errors when
1886 it encounters them. These keywords are normally highlighted as errors
1926 flagged as an error. Since Java 1.1 this is possible (with anonymous
1927 classes), and therefore is no longer marked as an error. If you prefer the old
1942 Function names are not highlighted, as the way to find functions depends on
1962 The result will be that those statements are highlighted as 'Special'
1977 2. The text is colored as 'Comment'.
1978 3. HTML comments are colored as 'Special'
1979 4. The special Javadoc tags (@see, @param, ...) are highlighted as specials
1980 and the argument (for @see, @param, @exception) as Function.
2028 Lex uses brute-force synchronizing as the "^%%$" section delimiter
2029 gives no clue as to what section follows. Consequently, the value for >
2032 difficulties (such as may happen with large lex files).
2037 To highlight deprecated functions as errors, add in your .vimrc: >
2047 as if the contents of the string were lisp.
2078 file name of LPC is usually *.c. Recognizing these files as LPC would bother
2089 For a C file that is recognized as LPC:
2135 as quoted text. However Vim highlights headers and signatures in quoted text
2158 The standard set of packages' functions as supplied in Maple V release 4 may be
2204 Unmatched double quotes can be recognized and highlighted as errors: >
2212 Unknown builtin functions can be recognized and highlighted as errors. If you
2251 If you want to have unrecognized (by ncf.vim) statements highlighted as
2265 For example, Linux and BSD distributions use groff as their default text
2267 features for groff, arrange for files to be recognized as groff (see
2275 you access the year as a 2-digit number with the request \(yr. In groff you
2298 vertical space input will be output as is.
2305 spaces and two or more spaces after a punctuation as an error, use: >
2318 If you want to navigate preprocessor entries in your source file as easily as
2338 you can switch from standard OCaml-syntax to revised syntax as supported
2343 prevents highlighting of "end" as error, which is useful when sources
2351 as the top-level file format. By default everything inside phtml or pxml
2352 sections is treated as a string with embedded preprocessor commands. If
2382 To switch on Delphi specific constructions (such as one-line comments,
2388 The option pascal_symbol_operator controls whether symbol operators such as +,
2414 will be highlighted as Error. >
2449 perl_string_as_statement, it will be highlighted as in the second line.
2477 If you want to fold blocks in if statements, etc. as well set the following: >
2552 variant of TeX. If you never want your *.tex files recognized as plain TeX,
2608 highlighted by defining the postscr_level variable as follows: >
2620 Display PS language features by defining the postscr_display variable as
2627 postscr_ghostscript as follows: >
2646 or the other. By default they are treated as logical operators. They can be
2647 highlighted as binary operators by defining the variable
2648 postscr_andornot_binary as follows: >
2664 For example, to make Vim identify all files in /etc/termcaps/ as termcap
2713 If you want all possible Python highlighting (the same as setting the
2755 and highlight as functions all keywords followed by an opening parenthesis: >
2788 items as well you can add the following to your |vimrc| or just type it in the
2798 Rego is a query language developed by Styra. It is mostly used as a policy
2800 the following extensions are recognized as rego files: .rego.
2813 `rst_syntax_code_list` as a mapping: >
2869 as errors. This can be refined by defining "ruby_no_trail_space_error" and
2991 command. This means that, as far as this syntax file is concerned,
2992 transform accepts the same flags as substitute, which is wrong.
3000 The coloring scheme for tags in the SGML file works as follows.
3007 Known tag names are colored the same way as statements in C. Unknown tag
3043 shells such as bash, dash, posix, and the Korn shells.
3063 < posix: (using this is nearly the same as setting g:is_kornshell to 1) >
3073 default sh.vim syntax setting as just shown, then syntax/sh.vim will assume
3109 syntax/sh.vim tries to flag certain problems as errors; usually things like
3121 Lorance Stinson on how to do this with awk as an example. Put the following
3148 sections and subsections will be highlighted as statements but not
3152 like temperature or pressure to be highlighted as Type, not as a
3163 oneline_comments = 2 : show code starting with the second # as
3166 oneline_comments = 3 : show the whole line as error if it contains
3280 as there's no difference between start and end patterns. Consequently, a
3308 price: you will no longer have as much highlighting or any syntax-based
3361 code shows you an example as to how you might do so: >
3378 such use of @ as an error. To solve this: >
3394 In fact, only a few characters are supported as subscripts.
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
3600 and nothing else) as a value of the other type: null, boolean, floating-point,
3609 but there are some differences in what is recognized as
3763 {group-name} Is a syntax group name such as "Comment".
3793 Note that when you have a keyword that is the same as an option (even
3820 {group-name} A syntax group name such as "Comment".
3853 {group-name} A syntax group name such as "Comment".
3913 repeats that with "\{-}" (repeat as few as possible).
4033 When the "conceal" argument is given, the item is marked as concealable.
4043 the region, but not the contents of the region, are marked as concealable.
4054 a control character such as Tab. Example: >
4112 argument makes the "myVim" match use the same highlighting as "myString". But
4115 "myWord" to be contained, which will be highlighted as a Comment. This
4153 pattern must be found in the same line as where the start pattern ends. 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.
4248 appear. A "contains" argument may also be added as usual. Don't forget that
4275 Note the use of ".\{-}" to skip as little as possible until the next Bar.
4344 Try to avoid patterns that can match an empty string, such as "[a-z]*".
4428 used as leading context for this match. This can be used, for instance, to
4440 The "ms" offset is automatically set to the same value as the "lc" offset,
4446 The patterns can include "\n" to match an end-of-line. Mostly this works as
4471 \z(\) Marks the sub-expression as "external", meaning that it can be
4483 items, which marks a sub-expression as "external", in the sense that it can be
4489 it marks the "\(\I\i*\)" sub-expression as external; in the end pattern, it
4498 Note also that external sub-expressions cannot be accessed as back-references
4500 sub-expression as both a normal and an external sub-expression, you can nest
4501 the two, as in "\(\z(...\)\)".
4759 inside a string. That's left as an exercise to the reader...).
4822 This is basically the same as >
4846 For further customization, such as changing
4896 a file with ":highlight" commands such as this: >
4938 inverse same as reverse
5017 set -as terminal-overrides ",*-256color:Tc"
5088 "fg", "bg" and "ul" can be used as color names. This only works after
5107 font-name is the name of a font, as it is used on the system Vim
5120 character size as the default font! Otherwise redrawing problems will
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
5350 empty, and as such it is tied to the current |:language| when
5364 empty, and as such it is tied to the current |:language| when
5385 - As soon as you use a ":highlight" command for a linked group, the link is
5545 highlighted differently (so as to hide control sequences and indicate bold,
5719 as 'relativenumber' and |folding|.
5758 include as much literal text as possible to reduce the number of ways a