syntax.txt

MSYS在windows下模拟了一个类unix的终端

However, if you follow the java guidlines about how functions and classes are
supposed to be named (with respect to upper and lower cases), use
>  let java_highlight_functions="style"
If both options do not work for you, but you would still want function
declarations to be highlighted create your own definitions by changing the
definitions in java.vim or by creating your own java.vim which includes the
original one and then adds the code to highlight functions.

In java 1.1 the functions System.out.println() and System.err.println() should
only be used for debugging. Therefor it is possible to highlight debugging
statements differently. To do this you must add the following definition in
your startup file:
>  let java_highlight_debug=1
The result will be that those statements are highlighted as 'Special'
characters. If you prefer to have them highlighted differently you must define
new highlightings for the following groups.:
    Debug, DebugSpecial, DebugString, DebugBoolean, DebugType
which are used for the statement itself, special characters used in debug
strings, strings, boolean constants and types (this, super) respectively. I
have opted to chose another background for those statements.

In order to help you to write code that can be easely ported between
java and C++, all C++ keywords are marked as error in a java program.
However, if you use them regularly, you may want to define the following
variable in your .vimrc file:
>  let java_allow_cpp_keywords=1

Javadoc is a program that takes special comments out of java program files and
creates HTML pages. The standard configuration will highlight this HTML code
similarly to HTML files (see |html.vim|). You can even add javascript
and CSS inside this code (see below). There are four differences however:
  1. The title (all characters up to the first '.' which is followed by
     some white space or up to the first '@') is colored differently (to change
     the color change the group CommentTitle).
  2. The text is colored as 'Comment'.
  3. HTML comments are colored as 'Special'
  4. The special javadoc tags (@see, @param, ...) are highlighted as specials
     and the argument (for @see, @param, @exception) as Function.
To turn this feature off add the following line to your startup file:
>  let java_ignore_javadoc=1

If you use the special javadoc comment highlighting described above you
can also turn on special highlighting for javascript, visual basic
scripts and embedded CSS (stylesheets). This makes only sense if you
actually have javadoc comments that include either javascript or embedded
CSS. The options to use are
>  let java_javascript=1
>  let java_css=1
>  let java_vb=1

If you notice highlighting errors while scrolling backwards, which are fixed
when redrawing with CTRL-L, try setting the "java_minlines" internal variable
to a larger number:
>  let java_minlines = 50
This will make the syntax synchronization start 50 lines before the first
displayed line.  The default value is 10.  The disadvantage of using a larger
number is that redrawing can become slow.


LACE							*lace.vim*

Lace (Language for Assembly of Classes in Eiffel) is case insensitive, but the
style guide lines are not.  If you prefer case insensitive highlighting, just
define the vim variable 'lace_case_insensitive' in your startup file:
>  let lace_case_insensitive=1


LEX							*lex.vim*

Lex uses brute-force synchronizing as the "^%%$" section delimiter
gives no clue as to what section follows.  Consequently, the value for
>syn sync minlines=300
may be changed by the user if s/he is experiencing synchronization
difficulties (such as may happen with large lex files).


LITE							*lite.vim*

There are two options for the lite syntax highlighting.

If you like SQL syntax highligthing inside Strings, use this:

>  let lite_sql_query = 1

For syncing, minlines defaults to 100.  If you prefer another value, you can
set "lite_minlines" to the value you desire.  Example:

>  let lite_minlines = 200


MAPLE							*maple.vim*

Maple V, by Waterloo Maple Inc, supports symbolic algebra.  The language
supports many packages of functions which are selectively loaded by the user.
The standard set of packages' functions as supplied in Maple V release 4 may be
highlighted at the user's discretion.  Users may place in their .vimrc file:

>  let mvpkg_all= 1

to get all package functions highlighted, or users may select any subset by
choosing a variable/package from the table below and setting that variable to
1, also in their .vimrc file (prior to sourcing
$VIMRUNTIME/syntax/syntax.vim).

	Table of Maple V Package Function Selectors ~
>  mv_DEtools	 mv_genfunc	mv_networks	mv_process
>  mv_Galois	 mv_geometry	mv_numapprox	mv_simplex
>  mv_GaussInt	 mv_grobner	mv_numtheory	mv_stats
>  mv_LREtools	 mv_group	mv_orthopoly	mv_student
>  mv_combinat	 mv_inttrans	mv_padic	mv_sumtools
>  mv_combstruct mv_liesymm	mv_plots	mv_tensor
>  mv_difforms	 mv_linalg	mv_plottools	mv_totorder
>  mv_finance	 mv_logic	mv_powseries


MSQL							*msql.vim*

There are two options for the msql syntax highlighting.

If you like SQL syntax highligthing inside Strings, use this:

>  let msql_sql_query = 1

For syncing, minlines defaults to 100.  If you prefer another value, you can
set "msql_minlines" to the value you desire.  Example:

>  let msql_minlines = 200


NCF							*ncf.vim*

There is one option for NCF syntax highlighting.

If you want to have unrecognized (by ncf.vim) statements highlighted as
errors, use this:

>  let ncf_highlight_unknowns = 1

If you don't want to highlight these errors, leave it unset.


NROFF							*nroff.vim*

To mark trailing spaces as an error, use this:

>  let nroff_space_errors = 1


PASCAL                                          	*pascal.vim*

Files matching "*.p" could be Progress or Pascal.  If the automatic detection
doesn't work for you, or you don't edit Progress at all, use this in your
startup vimrc:

>   :let filetype_p = "pascal"  

The Pascal syntax file has been extended to take into account some extensions
provided by Turbo Pascal, Free Pascal Compiler and GNU Pascal Compiler.
Delphi keywords are also supported. By default, Turbo Pascal 7.0 features are
enabled.  If you prefer to stick with the standard Pascal keywords, add the
following line to your startup file:

>   :let pascal_traditional=1

To switch on Delphi specific constructions (such as one-line comments,
keywords, etc):

>   :let pascal_delphi=1


The option pascal_symbol_operator controls whether symbol operators such as +,
*, .., etc. are displayed using the Operator color or not.  To colorize symbol
operators, add the following line to your startup file:

>   :let pascal_symbol_operator=1

Some functions are highlighted by default.  To switch it off:

>   :let pascal_no_functions=1

Furthermore, there are specific variable for some compiler.  Besides
pascal_delphi, there are pascal_gpc and pascal_fpc.  Default extensions try to
match Turbo Pascal.

>   :let pascal_gpc=1

or

>   :let pascal_fpc=1

To ensure that strings are defined on a single line, you can define the
pascal_one_line_string variable.

>   :let pascal_one_line_string=1

If you dislike <Tab> chars, you can set the pascal_no_tabs variable.  Tabs
will be highlighted as Error.

>   :let pascal_no_tabs=1


PERL							*perl.vim*

There are a number of possible options to the perl syntax highlighting.

If you use POD files or POD segments, you might:

> let perl_include_POD = 1

To handle package references in variable and function names differently from
the rest of the name (like 'PkgName::' in '$PkgName::VarName'):

> let perl_want_scope_in_variables = 1

If you want complex things like '@{${"foo"}}' to be parsed:

> let perl_extended_vars = 1

The coloring strings can be changed. By default strings and qq friends will be
highlighted like the first line. If you set the variable
perl_string_as_statement, it will be highlighted as in the second line.

   "hello world!"; qq|hello world|;
   ^^^^^^^^^^^^^^NN^^^^^^^^^^^^^^^N       (unlet perl_string_as_statement)
   S^^^^^^^^^^^^SNNSSS^^^^^^^^^^^^N       (let perl_string_as_statement)

(^ = perlString, S = perlStatement, N = None at all)

The syncing has 3 options. The first two switch off some triggering of
synchronization and should only be needed in case it fails to work properly.
If while scrolling all of a sudden the whole screen changes color completely
then you should try and switch off one of those. Let me know if you can figure
out the line that causes the mistake.

One triggers on "^\s*sub\s*" and the other on "^[$@%]" more or less.

> let perl_no_sync_on_sub
> let perl_no_sync_on_global_var

Below you can set the maximum distance VIM should look for starting points for
its attempts in syntax highlighting.

> let perl_sync_dist = 100

For the "<<xxx" construct (here Documents), Vim can't check for any value of
"xxx".  If you have a choice use "<<EOF ... EOF", then the highlighting will
work.


PHP3 and PHP4					*php.vim* *php3.vim*

[note: previously this was called "php3", but since it now also supports php4
it has been renamed to "php"]

There are the following options to the php syntax highlighting.

If you like SQL syntax hightligthing inside Strings:

>  let php_sql_query = 1

For highligthing the Baselib methods:

>  let php_baselib = 1

Enable HTML syntax highligthing inside strings:

>  let php_htmlInStrings = 1

For syncing minlines is being set default to 100. If you
prefer another value, please make use of something like:

>  let php_minlines = 200

Using the old colorstyle:

>  let php_oldStyle = 1

Enable parent error highlighting:

>  let_parentError = 1

Enable highlighting ASP-style short tags:

>  let php_asp_tags = 1

Disable short tags:

>  let php_noShortTags = 1


PPWIZARD (preprocessor for HTML and OS/2 INF files)		*ppwiz.vim* 

This syntax file has the options:

- ppwiz_highlight_defs : determines highlighting mode for PPWizard's
  definitions. Possible values are

  ppwiz_highlight_defs = 1 : PPWizard #define statements retain the
    colors of their contents (e. g. PPWizard macros and variables)

  ppwiz_highlight_defs = 2 : preprocessor #define and #evaluate
    statements are shown in a single color with the exception of line
    continuation symbols

  The default setting for ppwiz_highlight_defs is 1.

- ppwiz_with_html : If the value is 1 (the default), highlight literal
  HTML code; if 0, treat HTML code like ordinary text.


PHTML							*phtml.vim*

There are two options for the phtml syntax highlighting.

If you like SQL syntax highligthing inside Strings, use this:

>  let phtml_sql_query = 1

For syncing, minlines defaults to 100.  If you prefer another value, you can
set "phtml_minlines" to the value you desire.  Example:

>  let phtml_minlines = 200


POSTSCRIPT						*postscr.vim*

There are several options when it comes to highlighting PostScript.

First which version of the PostScript language to highlight.  There are
currently three defined language versions, or levels.  Level 1 is the original
and base version, and includes all extensions prior to the release of level 2.
Level 2 is the most common version around, and includes its own set of
extensions prior to the release of level 3.  Level 3 is currently the highest
level supported.  You select which level of the PostScript language you want
highlighted by defining the postscr_level variable as follows:

>  let postscr_level=2

If this variable is not defined it defaults to 2 (level 2) since this is