1- *starting.txt* For Vim version 7.4. Last change: 2016 Aug 06
1+ *starting.txt* For Vim version 7.4. Last change: 2016 Aug 23
22
33
44 VIM REFERENCE MANUAL by Bram Moolenaar
@@ -923,7 +923,8 @@ accordingly. Vim proceeds in this order:
923923The $MYVIMRC or $MYGVIMRC file will be set to the first found vimrc and/or
924924gvimrc file.
925925
926- Some hints on using initializations:
926+
927+ Some hints on using initializations ~
927928
928929Standard setup:
929930Create a vimrc file to set the default settings and mappings for all your edit
@@ -946,27 +947,37 @@ want to set the defaults for all users. Create a vimrc file with commands
946947for default settings and mappings and put it in the place that is given with
947948the ":version" command.
948949
949- Saving the current state of Vim to a file:
950+
951+ Saving the current state of Vim to a file ~
952+
950953Whenever you have changed values of options or when you have created a
951954mapping, then you may want to save them in a vimrc file for later use. See
952955| save-settings | about saving the current state of settings to a file.
953956
954- Avoiding setup problems for Vi users:
957+
958+ Avoiding setup problems for Vi users ~
959+
955960Vi uses the variable EXINIT and the file "~/.exrc". So if you do not want to
956961interfere with Vi, then use the variable VIMINIT and the file "vimrc" instead.
957962
958- Amiga environment variables:
963+
964+ Amiga environment variables ~
965+
959966On the Amiga, two types of environment variables exist. The ones set with the
960967DOS 1.3 (or later) setenv command are recognized. See the AmigaDos 1.3
961968manual. The environment variables set with the old Manx Set command (before
962969version 5.0) are not recognized.
963970
964- MS-DOS line separators:
971+
972+ MS-DOS line separators ~
973+
965974On MS-DOS-like systems (MS-DOS itself, Win32, and OS/2), Vim assumes that all
966975the vimrc files have <CR> <NL> pairs as line separators. This will give
967976problems if you have a file with only <NL> s and have a line like
968977":map xx yy^M". The trailing ^M will be ignored.
969978
979+
980+ Vi compatible default value ~
970981 *compatible-default*
971982When Vim starts, the 'compatible' option is on. This will be used when Vim
972983starts its initializations. But as soon as:
@@ -999,6 +1010,8 @@ encountered. This makes a difference when using things like "<CR>". If the
9991010mappings depend on a certain value of 'compatible' , set or reset it before
10001011giving the mapping.
10011012
1013+
1014+ Defaults without a .vimrc file ~
10021015 *defaults.vim*
10031016If Vim is started normally and no user vimrc file is found, the
10041017$VIMRUTIME/defaults.vim script is loaded. This will set 'compatible' off,
@@ -1018,7 +1031,8 @@ revert individual settings. See the defaults.vim file for hints on how to
10181031revert each item.
10191032
10201033
1021- Avoiding trojan horses: *trojan-horse*
1034+ Avoiding trojan horses ~
1035+ *trojan-horse*
10221036While reading the "vimrc" or the "exrc" file in the current directory, some
10231037commands can be disabled for security reasons by setting the 'secure' option.
10241038This is always done when executing the command from a tags file. Otherwise it
@@ -1041,6 +1055,8 @@ Be careful!
10411055part of the line in the tags file) is always done in secure mode. This works
10421056just like executing a command from a vimrc/exrc in the current directory.
10431057
1058+
1059+ If Vim startup is slow ~
10441060 *slow-start*
10451061If Vim takes a long time to start up, use the | --startuptime | argument to find
10461062out what happens. There are a few common causes:
@@ -1055,6 +1071,8 @@ out what happens. There are a few common causes:
10551071 moment (use the Vim argument "-i NONE", | -i | ). Try reducing the number of
10561072 lines stored in a register with ":set viminfo='20,<50,s10". | viminfo-file | .
10571073
1074+
1075+ Intro message ~
10581076 *:intro*
10591077When Vim starts without a file name, an introductory message is displayed (for
10601078those who don't know what Vim is). It is removed as soon as the display is
@@ -1613,18 +1631,12 @@ most of the information will be restored).
16131631 file. This list is read on startup and only changes
16141632 afterwards with `:rviminfo ! ` . Also see | v:oldfiles | .
16151633 The number can be used with | c_#< | .
1634+ The output can be filtered with | :filter | , e.g.: >
1635+ filter /\\.vim/ oldfiles
1636+ < The filtering happens on the file name.
16161637 {not in Vi, only when compiled with the | +eval |
16171638 feature}
16181639
1619- :ol[dfiles] {pat}
1620- :ol[dfiles] /{pat} /
1621- Like `:oldfiles ` but only files matching {pat} will
1622- be included. {pat} is a Vim search pattern. Instead
1623- of enclosing it in / any non-ID character (see
1624- | 'isident' | ) can be used, so long as it does not
1625- appear in {pat} . Without the enclosing character the
1626- pattern cannot include the bar character.
1627-
16281640:bro[wse] ol[dfiles][!]
16291641 List file names as with | :oldfiles | , and then prompt
16301642 for a number. When the number is valid that file from
0 commit comments