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
@@ -924,7 +924,8 @@ accordingly. Vim proceeds in this order:
924924The $MYVIMRC or $MYGVIMRC file will be set to the first found vimrc and/or
925925gvimrc file.
926926
927- Some hints on using initializations:
927+
928+ Some hints on using initializations ~
928929
929930Standard setup:
930931Create a vimrc file to set the default settings and mappings for all your edit
@@ -947,27 +948,37 @@ want to set the defaults for all users. Create a vimrc file with commands
947948for default settings and mappings and put it in the place that is given with
948949the ":version" command.
949950
950- Saving the current state of Vim to a file:
951+
952+ Saving the current state of Vim to a file ~
953+
951954Whenever you have changed values of options or when you have created a
952955mapping, then you may want to save them in a vimrc file for later use. See
953956| save-settings | about saving the current state of settings to a file.
954957
955- Avoiding setup problems for Vi users:
958+
959+ Avoiding setup problems for Vi users ~
960+
956961Vi uses the variable EXINIT and the file "~/.exrc". So if you do not want to
957962interfere with Vi, then use the variable VIMINIT and the file "vimrc" instead.
958963
959- Amiga environment variables:
964+
965+ Amiga environment variables ~
966+
960967On the Amiga, two types of environment variables exist. The ones set with the
961968DOS 1.3 (or later) setenv command are recognized. See the AmigaDos 1.3
962969manual. The environment variables set with the old Manx Set command (before
963970version 5.0) are not recognized.
964971
965- MS-DOS line separators:
972+
973+ MS-DOS line separators ~
974+
966975On MS-DOS-like systems (MS-DOS itself, Win32, and OS/2), Vim assumes that all
967976the vimrc files have <CR> <NL> pairs as line separators. This will give
968977problems if you have a file with only <NL> s and have a line like
969978":map xx yy^M". The trailing ^M will be ignored.
970979
980+
981+ Vi compatible default value ~
971982 *compatible-default*
972983When Vim starts, the 'compatible' option is on. This will be used when Vim
973984starts its initializations. But as soon as:
@@ -1000,6 +1011,8 @@ encountered. This makes a difference when using things like "<CR>". If the
10001011mappings depend on a certain value of 'compatible' , set or reset it before
10011012giving the mapping.
10021013
1014+
1015+ Defaults without a .vimrc file ~
10031016 *defaults.vim*
10041017If Vim is started normally and no user vimrc file is found, the
10051018$VIMRUTIME/defaults.vim script is loaded. This will set 'compatible' off,
@@ -1019,7 +1032,8 @@ revert individual settings. See the defaults.vim file for hints on how to
10191032revert each item.
10201033
10211034
1022- Avoiding trojan horses: *trojan-horse*
1035+ Avoiding trojan horses ~
1036+ *trojan-horse*
10231037While reading the "vimrc" or the "exrc" file in the current directory, some
10241038commands can be disabled for security reasons by setting the 'secure' option.
10251039This is always done when executing the command from a tags file. Otherwise it
@@ -1042,6 +1056,8 @@ Be careful!
10421056part of the line in the tags file) is always done in secure mode. This works
10431057just like executing a command from a vimrc/exrc in the current directory.
10441058
1059+
1060+ If Vim startup is slow ~
10451061 *slow-start*
10461062If Vim takes a long time to start up, use the | --startuptime | argument to find
10471063out what happens. There are a few common causes:
@@ -1056,6 +1072,8 @@ out what happens. There are a few common causes:
10561072 moment (use the Vim argument "-i NONE", | -i | ). Try reducing the number of
10571073 lines stored in a register with ":set viminfo='20,<50,s10". | viminfo-file | .
10581074
1075+
1076+ Intro message ~
10591077 *:intro*
10601078When Vim starts without a file name, an introductory message is displayed (for
10611079those who don't know what Vim is). It is removed as soon as the display is
@@ -1614,18 +1632,12 @@ most of the information will be restored).
16141632 file. This list is read on startup and only changes
16151633 afterwards with `:rviminfo ! ` . Also see | v:oldfiles | .
16161634 The number can be used with | c_#< | .
1635+ The output can be filtered with | :filter | , e.g.: >
1636+ filter /\\.vim/ oldfiles
1637+ < The filtering happens on the file name.
16171638 {not in Vi, only when compiled with the | +eval |
16181639 feature}
16191640
1620- :ol[dfiles] {pat}
1621- :ol[dfiles] /{pat} /
1622- Like `:oldfiles ` but only files matching {pat} will
1623- be included. {pat} is a Vim search pattern. Instead
1624- of enclosing it in / any non-ID character (see
1625- | 'isident' | ) can be used, so long as it does not
1626- appear in {pat} . Without the enclosing character the
1627- pattern cannot include the bar character.
1628-
16291641:bro[wse] ol[dfiles][!]
16301642 List file names as with | :oldfiles | , and then prompt
16311643 for a number. When the number is valid that file from
0 commit comments