starting.txt

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

Standard setup:
Create a vimrc file to set the default settings and mappings for all your edit
sessions.  Put it in a place so that it will be found by 3b:
	~/.vimrc	(Unix and OS/2)
	s:.vimrc	(Amiga)
	$VIM\_vimrc	(MS-DOS and Win32)
Note that creating a vimrc file will cause the 'compatible' option to be off
by default.  See |compatible-default|.

Local setup:
Put all commands that you need for editing a specific directory only into a
vimrc file and place it in that directory under the name ".vimrc" ("_vimrc"
for MS-DOS and Win32).  NOTE: To make Vim look for these special files you
have to turn on the option 'exrc'.  See |trojan-horse| too.

System setup:
This only applies if you are managing a Unix system with several users and
want to set the defaults for all users.  Create a vimrc file with commands
for default settings and mappings and put it in the place that is given with
the ":version" command.

Saving the current state of Vim to a file:
Whenever you have changed values of options or when you have created a
mapping, then you may want to save them in a vimrc file for later use.  See
|save-settings| about saving the current state of settings to a file.

Avoiding setup problems for Vi users:
Vi uses the variable EXINIT and the file "~/.exrc".  So if you do not want to
interfere with Vi, then use the variable VIMINIT and the file "vimrc" instead.

Amiga environment variables:
On the Amiga, two types of environment variables exist.  The ones set with the
DOS 1.3 (or later) setenv command are recognized.  See the AmigaDos 1.3
manual.  The environment variables set with the old Manx Set command (before
version 5.0) are not recognized.

MS-DOS line separators:
On MS-DOS-like systems (MS-DOS itself, Win32, and OS/2), Vim assumes that all
the vimrc files have <CR> <NL> pairs as line separators.  This will give
problems if you have a file with only <NL>s and have a line like
":map xx yy^M".  The trailing ^M will be ignored.

						     *compatible-default*
When Vim starts, the 'compatible' option is on.  This will be used when Vim
starts its initializations.  But as soon as a user vimrc file is found, or a
vimrc file in the current directory, or the "VIMINIT" environment variable is
set, it will be set to 'nocompatible'.  This has the side effect of setting or
resetting other options (see 'compatible').  But only the options that have
not been set or reset will be changed.  This has the same effect like the
value of 'compatible' had this value when starting Vim.  Note that this
doesn't happen for the system-wide vimrc file.

But there is a side effect of setting or resetting 'compatible' at the moment
a .vimrc file is found: Mappings are interpreted the moment they are
encountered.  This makes a difference when using things like "<CR>".  If the
mappings depend on a certain value of 'compatible', set or reset it before
giving the mapping.

The above behavior can be overridden in these ways:
- If the "-N" command line argument is given, 'nocompatible' will be used,
  even when no vimrc file exists.
- If the "-C" command line argument is given, 'compatible' will be used, even
  when a vimrc file exists.
- If the "-u {vimrc}" argument is used, 'compatible' will be used.
- When the name of the executable ends in "ex", then this works like the "-C"
  argument was given: 'compatible' will be used, even when a vimrc file
  exists.  This has been done to make Vim behave like "ex", when it is started
  as "ex".

Avoiding trojan horses:					*trojan-horse*
While reading the "vimrc" or the "exrc" file in the current directory, some
commands can be disabled for security reasons by setting the 'secure' option.
This is always done when executing the command from a tags file.  Otherwise it
would be possible that you accidentally use a vimrc or tags file that somebody
else created and contains nasty commands.  The disabled commands are the ones
that start a shell, the ones that write to a file, and ":autocmd".  The ":map"
commands are echoed, so you can see which keys are being mapped.
	If you want Vim to execute all commands in a local vimrc file, you
can reset the 'secure' option in the EXINIT or VIMINIT environment variable or
in the global "exrc" or "vimrc" file.  This is not possible in "vimrc" or
"exrc" in the current directory, for obvious reasons.
	On Unix systems, this only happens if you are not the owner of the
vimrc file.  Warning: If you unpack an archive that contains a vimrc or exrc
file, it will be owned by you.  You won't have the security protection.  Check
the vimrc file before you start Vim in that directory, or reset the 'exrc'
option.  Some Unix systems allow a user to do "chown" on a file.  This makes
it possible for another user to create a nasty vimrc and make you the owner.
Be careful!
	When using tag search commands, executing the search command (the last
part of the line in the tags file) is always done in secure mode.  This works
just like executing a command from a vimrc/exrc in the current directory.

							*slow-start*
If Vim takes a long time to start up, there may be a few causes:
- If the Unix version was compiled with the GUI and/or X11 (check the output
  of ":version" for "+GUI" and "+X11"), it may need to load shared libraries
  and connect to the X11 server.  Try compiling a version with GUI and X11
  disabled.  This also should make the executable smaller.
- If you have "viminfo" enabled, the loading of the viminfo file may take a
  while.  You can find out if this is the problem by disabling viminfo for a
  moment (use the Vim argument "-i NONE", |-i|).  Try reducing the number of
  lines stored in a register with ":set viminfo='20\"50".
							|viminfo-file|.

							*:intro*
When Vim starts without a file name, an introductory message is displayed (for
those who don't know what Vim is).  It is removed as soon as the display is
redrawn in any way.  To see the message again, use the ":intro" command.
To avoid the intro message on startup, add the 'I' flag to 'shortmess'.

==============================================================================
5. Suspending						*suspend*

						*iconise* *CTRL-Z* *v_CTRL-Z*
CTRL-Z			Suspend Vim, like ":stop".
			Works in Normal and in Visual mode.  In Insert and
			Command-line mode, the CTRL-Z is inserted as a normal
			character.


:sus[pend][!]	or			*:sus* *:suspend* *:st* *:stop*
:st[op][!]		Suspend Vim.
			If the '!' is not given and 'autowrite' is set, every
			buffer with changes and a file name is written out.
			If the '!' is given or 'autowrite' is not set, changed
			buffers are not written, don't forget to bring Vim
			back to the foreground later!

In the GUI, suspending is implemented as iconising gvim.  In Windows 95/NT,
gvim is minimized.

On many Unix systems, it is possible to suspend Vim with CTRL-Z.  This is only
possible in Normal and Visual mode (see next chapter, |vim-modes|).  Vim will
continue if you make it the foreground job again.  On other systems, CTRL-Z
will start a new shell.  This is the same as the ":sh" command.  Vim will
continue if you exit from the shell.

==============================================================================
6. The vimrc file			*vimrc-intro* *vim-script-intro*

A vimrc file can be used for settings you intend to use more-or-less for every
of your Vim sessions.  Normally the file is called $HOME/.vimrc, but other
files can also be used, see |vimrc|.  Vim will read it (them) when starting
and interpret the commands in them.

You can also use Vim script files for other purposes.  The files used for
syntax highlighting are an example.  There are enough commands in Vim to
accomplish just about any task.

						*vimrc_example.vim*
You should be able to find an example vimrc file at
$VIMRUNTIME/vimrc_example.vim.  You could use this as a start for your own
vimrc file.  You can also find a lot of examples in vimrc files made by
others.  Have a look at http://www.vim.org/user.html.


USING EX COMMANDS ~

The vimrc file can contain anything that can be typed on the Vim command line.
The recommended practice is not to include the preceding colon sign ":", thus
if one would type
>	:set number
on the Vim command line, the same can appear in the vimrc file simply as
>	set number

The end-of-line character depends on the system.  For Unix a single <NL>
character is used.  For MS-DOS, Windows, OS/2 and the like, <CR><LF> is used.
This is important when using mappings that end in a <CR>.  See |:source_crnl|.

Long lines can be split up by inserting a "\" (backslash) at the start of
the next line where the line has been broken, see |line-continuation|.
Example:
>	iabbr Http  Hyper Text Transfer
>		\ Protocol
Note that this only works in a Vim script file.


WHITE SPACE ~

Blank lines are allowed and ignored.

Leading whitespace characters (blanks and TABs) are always ignored.  The
whitespaces between parameters (e.g. between the 'set' and the 'number' in the
example above) are reduced to one blank character and plays the role of a
separator, the whitespaces after the last (visible) character may or may not
be ignored depending on the situation, see below.

For a ":set" command involving the "=" (equal) sign, such as in
>	set cpoptions    =aABceFst
the whitespace immediately before the "=" sign is ignored.  But there can be
no whitespace after the "=" sign!

To include a whitespace character in the value of an option, it must be
escaped by a "\" (backslash)  as in the following example:
>	set tags=my\ nice\ file
The same example written as
>	set tags=my nice file
will issue an error, because it is interpreted as:
>	set tags=my
>	set nice
>	set file


COMMENTS ~

The character " (the double quote mark) starts a comment.  Everything after
and including this character until the end-of-line is considered a comment and
is ignored, except for commands that don't consider comments, as shown in
examples below.  A comment can start on any character position on the line.

There is a little "catch" with comments for some commands.  Examples:
>	abbrev dev development		" shorthand
>	map <F3> o#include		" insert include
>	execute cmd			" do it
>	!ls *.c				" list C files
The abbreviation 'dev' will be expanded to 'development     " shorthand'.  The
mapping of <F3> will actually be the whole line after the 'o# ....' including
the '" insert include'.  The "execute" command will give an error.  The "!"
command will send everything after it to the shell, causing an error for an
unmatched '"' character.
There can be no comment after ":map", ":abbreviate", ":execute" and "!"
commands (there are a few more commands with this restriction).  For the
"map", ":abbreviate" and "execute" commands there is a trick:
>	abbrev dev development|" shorthand
>	map <F3> o#include|" insert include
>	execute cmd			|" do it
With the '|' character the command is separated from the next one.  And that
next command is only a comment.

Note that there is no white space before the '|' in the abbreviation and
mapping.  For these commands, any character until the end-of-line or '|' is
included.  As a consequence of this behavior, you don't always see that
trailing whitespace is included:
>	map <F4> o#include  
To avoid these problems, you can set the 'list' option when editing vimrc
files.


PITFALLS ~

Even bigger problem arises in the following example:
>	map ,ab o#include
>	unmap ,ab
Here the mapping of ,ab will be ',ab', no trailing whitespaces is included.
However, the "unmap" does not end directly with the end-of-line, Vim will try
to unmap ',ab ', which does not exist as a mapped sequence.  An error will be
issued, which is very hard to identify, because the ending whitespace
character on the 'unmap ,ab ' are not visible.

And this is exactly the same what happens when one uses a comment after an
'unmap' command:
>	unmap ,ab     " comment
Here the comment part will be ignored.  However, Vim will try to unmap
',ab     ', which does not exist,  Deleting the comment as well as all the
whitespaces up the ending 'b' character will cure the problem.

Except for the situations as above, it is legal to put a comment on the same
line as the Vim definitions, such as
>	set number	" display line numbers


NORMAL MODE COMMANDS ~

To execute normal mode commands, the |:normal| command can be used.  To avoid
trouble with special characters, use the |:execute| command.  Its argument is
an expression (more about that further down).  Example:
>	exe "normal mxGOA test.\<Esc>`x"
This appends "A test." below the last line in the file and returns the cursor
to where it was.  Note the use of "\<Esc>", which is translated into the
escape character.  To use a backslash or double quote here you have to put a
backslash before it:
>	exe "normal \"aYgg\"aP"
This yanks the current line and puts it above the first line in the file.  To
do this without changing the cursor position and the text displayed in the
window, this has to be extended a bit:
>	exe "normal ma\"aYHmbgg\"aP`bzt`a"
What this does:
	ma		set mark a at cursor position
	"aY		yank current line into register a
	Hmb		go to top line in window and set mark b there
	gg		go to first line in file
	"aP		put the yanked line above it
	`b		go back to top line in display
	zt		position the text in the window as it was before
	`a		go back to saved cursor position


IF - ELSE - ENDIF ~

Sometimes you will want to execute a command only under a certain condition.
The |:if| command can be used for this.  Example:
>	if &term == "xterm"
>	  echo "this is an xterm"
>	endif
The argument for the "if" command is an expression.  If this expression
evaluates to true (non-zero), the statements until the "endif" are executed.