Mercurial > vim
annotate runtime/doc/starting.txt @ 9737:35ce559b8553
commit https://github.com/vim/vim/commit/bc8801c9317eb721a2ee91322669f2dd5d136380
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Aug 2 21:04:33 2016 +0200
Updated runtime files.
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Tue, 02 Aug 2016 21:15:06 +0200 |
| parents | 284b4eb307fc |
| children | 4360b2b46125 |
| rev | line source |
|---|---|
|
9737
35ce559b8553
commit https://github.com/vim/vim/commit/bc8801c9317eb721a2ee91322669f2dd5d136380
Christian Brabandt <cb@256bit.org>
parents:
9669
diff
changeset
|
1 *starting.txt* For Vim version 7.4. Last change: 2016 Jul 29 |
| 7 | 2 |
| 3 | |
| 4 VIM REFERENCE MANUAL by Bram Moolenaar | |
| 5 | |
| 6 | |
| 7 Starting Vim *starting* | |
| 8 | |
| 9 1. Vim arguments |vim-arguments| | |
| 10 2. Vim on the Amiga |starting-amiga| | |
| 11 3. Running eVim |evim-keys| | |
| 12 4. Initialization |initialization| | |
| 13 5. $VIM and $VIMRUNTIME |$VIM| | |
| 14 6. Suspending |suspend| | |
|
8148
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
15 7. Exiting |exiting| |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
16 8. Saving settings |save-settings| |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
17 9. Views and Sessions |views-sessions| |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
18 10. The viminfo file |viminfo-file| |
| 7 | 19 |
| 20 ============================================================================== | |
| 21 1. Vim arguments *vim-arguments* | |
| 22 | |
| 23 Most often, Vim is started to edit a single file with the command | |
| 24 | |
| 25 vim filename *-vim* | |
| 26 | |
| 27 More generally, Vim is started with: | |
| 28 | |
| 29 vim [option | filename] .. | |
| 30 | |
| 31 Option arguments and file name arguments can be mixed, and any number of them | |
| 32 can be given. However, watch out for options that take an argument. | |
| 33 | |
| 34 For compatibility with various Vi versions, see |cmdline-arguments|. | |
| 35 | |
| 36 Exactly one out of the following five items may be used to choose how to | |
| 37 start editing: | |
| 38 | |
| 39 *-file* *---* | |
| 40 filename One or more file names. The first one will be the current | |
| 41 file and read into the buffer. The cursor will be positioned | |
| 42 on the first line of the buffer. | |
| 43 To avoid a file name starting with a '-' being interpreted as | |
| 44 an option, precede the arglist with "--", e.g.: > | |
| 45 vim -- -filename | |
| 46 < All arguments after the "--" will be interpreted as file names, | |
| 47 no other options or "+command" argument can follow. | |
|
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8392
diff
changeset
|
48 For behavior of quotes on MS-Windows, see |win32-quotes|. |
| 7 | 49 |
| 50 *--* | |
| 51 - This argument can mean two things, depending on whether Ex | |
| 52 mode is to be used. | |
| 53 | |
| 54 Starting in Normal mode: > | |
| 55 vim - | |
| 56 ex -v - | |
| 57 < Start editing a new buffer, which is filled with text | |
| 58 that is read from stdin. The commands that would normally be | |
| 59 read from stdin will now be read from stderr. Example: > | |
| 60 find . -name "*.c" -print | vim - | |
| 61 < The buffer will be marked modified, because it contains text | |
| 62 that needs to be saved. Except when in readonly mode, then | |
| 63 the buffer is not marked modified. Example: > | |
| 64 ls | view - | |
| 65 < | |
| 66 Starting in Ex mode: > | |
| 67 ex - | |
| 68 vim -e - | |
| 69 exim - | |
| 70 vim -E | |
| 71 < Start editing in silent mode. See |-s-ex|. | |
| 72 | |
| 73 *-t* *-tag* | |
| 74 -t {tag} A tag. "tag" is looked up in the tags file, the associated | |
| 75 file becomes the current file, and the associated command is | |
| 76 executed. Mostly this is used for C programs, in which case | |
| 77 "tag" often is a function name. The effect is that the file | |
| 78 containing that function becomes the current file and the | |
| 79 cursor is positioned on the start of the function (see | |
| 80 |tags|). | |
| 81 | |
| 82 *-q* *-qf* | |
| 83 -q [errorfile] QuickFix mode. The file with the name [errorfile] is read | |
| 84 and the first error is displayed. See |quickfix|. | |
| 85 If [errorfile] is not given, the 'errorfile' option is used | |
| 86 for the file name. See 'errorfile' for the default value. | |
| 87 {not in Vi} | |
| 88 | |
| 89 (nothing) Without one of the four items above, Vim will start editing a | |
| 90 new buffer. It's empty and doesn't have a file name. | |
| 91 | |
| 92 | |
| 93 The startup mode can be changed by using another name instead of "vim", which | |
| 94 is equal to giving options: | |
| 95 ex vim -e Start in Ex mode (see |Ex-mode|). *ex* | |
| 96 exim vim -E Start in improved Ex mode (see |Ex-mode|). *exim* | |
| 97 (normally not installed) | |
| 98 view vim -R Start in read-only mode (see |-R|). *view* | |
| 99 gvim vim -g Start the GUI (see |gui|). *gvim* | |
| 2581 | 100 gex vim -eg Start the GUI in Ex mode. *gex* |
| 101 gview vim -Rg Start the GUI in read-only mode. *gview* | |
| 7 | 102 rvim vim -Z Like "vim", but in restricted mode (see |-Z|) *rvim* |
| 2581 | 103 rview vim -RZ Like "view", but in restricted mode. *rview* |
| 104 rgvim vim -gZ Like "gvim", but in restricted mode. *rgvim* | |
| 105 rgview vim -RgZ Like "gview", but in restricted mode. *rgview* | |
| 7 | 106 evim vim -y Easy Vim: set 'insertmode' (see |-y|) *evim* |
| 2581 | 107 eview vim -yR Like "evim" in read-only mode *eview* |
| 7 | 108 vimdiff vim -d Start in diff mode |diff-mode| |
| 109 gvimdiff vim -gd Start in diff mode |diff-mode| | |
| 110 | |
| 111 Additional characters may follow, they are ignored. For example, you can have | |
| 112 "gvim-5" to start the GUI. You must have an executable by that name then, of | |
| 113 course. | |
| 114 | |
| 115 On Unix, you would normally have one executable called Vim, and links from the | |
| 116 different startup-names to that executable. If your system does not support | |
| 117 links and you do not want to have several copies of the executable, you could | |
| 118 use an alias instead. For example: > | |
| 119 alias view vim -R | |
| 120 alias gvim vim -g | |
| 121 < | |
| 122 *startup-options* | |
| 123 The option arguments may be given in any order. Single-letter options can be | |
| 124 combined after one dash. There can be no option arguments after the "--" | |
| 125 argument. | |
| 126 | |
| 127 On VMS all option arguments are assumed to be lowercase, unless preceded with | |
| 128 a slash. Thus "-R" means recovery and "-/R" readonly. | |
| 129 | |
| 130 --help *-h* *--help* | |
| 131 -h Give usage (help) message and exit. {not in Vi} | |
| 132 See |info-message| about capturing the text. | |
| 133 | |
| 134 *--version* | |
| 135 --version Print version information and exit. Same output as for | |
| 136 |:version| command. {not in Vi} | |
| 137 See |info-message| about capturing the text. | |
| 138 | |
| 139 *--noplugin* | |
| 140 --noplugin Skip loading plugins. Resets the 'loadplugins' option. | |
| 141 {not in Vi} | |
| 142 Note that the |-u| argument may also disable loading plugins: | |
| 143 argument load vimrc files load plugins ~ | |
| 144 (nothing) yes yes | |
| 145 -u NONE no no | |
| 146 -u NORC no yes | |
| 147 --noplugin yes no | |
| 148 | |
| 1989 | 149 --startuptime {fname} *--startuptime* |
| 1972 | 150 During startup write timing messages to the file {fname}. |
| 151 This can be used to find out where time is spent while loading | |
| 1989 | 152 your .vimrc, plugins and opening the first file. |
| 1972 | 153 When {fname} already exists new messages are appended. |
| 1989 | 154 (Only available when compiled with the |+startuptime| |
| 155 feature). | |
| 1972 | 156 |
| 7 | 157 *--literal* |
| 158 --literal Take file names literally, don't expand wildcards. Not needed | |
| 159 for Unix, because Vim always takes file names literally (the | |
| 160 shell expands wildcards). | |
| 161 Applies to all the names, also the ones that come before this | |
| 162 argument. | |
| 163 | |
| 164 *-+* | |
| 165 +[num] The cursor will be positioned on line "num" for the first | |
| 166 file being edited. If "num" is missing, the cursor will be | |
| 167 positioned on the last line. | |
| 168 | |
| 169 *-+/* | |
| 170 +/{pat} The cursor will be positioned on the first line containing | |
| 171 "pat" in the first file being edited (see |pattern| for the | |
| 6009 | 172 available search patterns). The search starts at the cursor |
| 173 position, which can be the first line or the cursor position | |
| 174 last used from |viminfo|. To force a search from the first | |
| 175 line use "+1 +/pat". | |
| 7 | 176 |
| 177 +{command} *-+c* *-c* | |
| 178 -c {command} {command} will be executed after the first file has been | |
| 179 read (and after autocommands and modelines for that file have | |
| 180 been processed). "command" is interpreted as an Ex command. | |
| 181 If the "command" contains spaces, it must be enclosed in | |
| 182 double quotes (this depends on the shell that is used). | |
| 183 Example: > | |
| 184 vim "+set si" main.c | |
| 185 vim "+find stdio.h" | |
| 186 vim -c "set ff=dos" -c wq mine.mak | |
| 187 < | |
| 188 Note: You can use up to 10 "+" or "-c" arguments in a Vim | |
| 189 command. They are executed in the order given. A "-S" | |
| 190 argument counts as a "-c" argument as well. | |
| 191 {Vi only allows one command} | |
| 192 | |
| 193 --cmd {command} *--cmd* | |
| 194 {command} will be executed before processing any vimrc file. | |
| 195 Otherwise it acts like -c {command}. You can use up to 10 of | |
| 196 these commands, independently from "-c" commands. | |
| 197 {not in Vi} | |
| 198 | |
| 199 *-S* | |
| 200 -S {file} The {file} will be sourced after the first file has been read. | |
| 201 This is an easy way to do the equivalent of: > | |
| 202 -c "source {file}" | |
| 203 < It can be mixed with "-c" arguments and repeated like "-c". | |
| 204 The limit of 10 "-c" arguments applies here as well. | |
| 205 {file} cannot start with a "-". | |
| 206 {not in Vi} | |
| 207 | |
| 208 -S Works like "-S Session.vim". Only when used as the last | |
| 209 argument or when another "-" option follows. | |
| 210 | |
| 211 *-r* | |
| 212 -r Recovery mode. Without a file name argument, a list of | |
| 213 existing swap files is given. With a file name, a swap file | |
| 214 is read to recover a crashed editing session. See | |
| 215 |crash-recovery|. | |
| 216 | |
| 217 *-L* | |
| 218 -L Same as -r. {only in some versions of Vi: "List recoverable | |
| 219 edit sessions"} | |
| 220 | |
| 221 *-R* | |
| 222 -R Readonly mode. The 'readonly' option will be set for all the | |
| 223 files being edited. You can still edit the buffer, but will | |
| 224 be prevented from accidentally overwriting a file. If you | |
| 225 forgot that you are in View mode and did make some changes, | |
| 226 you can overwrite a file by adding an exclamation mark to | |
| 227 the Ex command, as in ":w!". The 'readonly' option can be | |
| 228 reset with ":set noro" (see the options chapter, |options|). | |
| 229 Subsequent edits will not be done in readonly mode. Calling | |
| 230 the executable "view" has the same effect as the -R argument. | |
| 231 The 'updatecount' option will be set to 10000, meaning that | |
| 232 the swap file will not be updated automatically very often. | |
| 233 | |
| 234 *-m* | |
| 235 -m Modifications not allowed to be written. The 'write' option | |
| 236 will be reset, so that writing files is disabled. However, | |
| 237 the 'write' option can be set to enable writing again. | |
| 238 {not in Vi} | |
| 239 | |
| 240 *-M* | |
| 241 -M Modifications not allowed. The 'modifiable' option will be | |
| 242 reset, so that changes are not allowed. The 'write' option | |
| 243 will be reset, so that writing files is disabled. However, | |
| 244 the 'modifiable' and 'write' options can be set to enable | |
| 245 changes and writing. | |
| 246 {not in Vi} | |
| 247 | |
| 248 *-Z* *restricted-mode* *E145* | |
| 249 -Z Restricted mode. All commands that make use of an external | |
| 250 shell are disabled. This includes suspending with CTRL-Z, | |
| 251 ":sh", filtering, the system() function, backtick expansion, | |
|
9041
34c45ee4210d
commit https://github.com/vim/vim/commit/06481427005a9dae39721087df94855f7d4d1feb
Christian Brabandt <cb@256bit.org>
parents:
8876
diff
changeset
|
252 delete(), rename(), mkdir(), writefile(), libcall(), |
|
34c45ee4210d
commit https://github.com/vim/vim/commit/06481427005a9dae39721087df94855f7d4d1feb
Christian Brabandt <cb@256bit.org>
parents:
8876
diff
changeset
|
253 job_start(), etc. |
| 7 | 254 {not in Vi} |
| 255 | |
| 256 *-g* | |
| 3445 | 257 -g Start Vim in GUI mode. See |gui|. For the opposite see |-v|. |
| 258 {not in Vi} | |
| 7 | 259 |
| 260 *-v* | |
| 261 -v Start Ex in Vi mode. Only makes a difference when the | |
| 262 executable is called "ex" or "gvim". For gvim the GUI is not | |
| 263 started if possible. | |
| 264 | |
| 265 *-e* | |
| 266 -e Start Vim in Ex mode |Q|. Only makes a difference when the | |
| 267 executable is not called "ex". | |
| 268 | |
| 269 *-E* | |
| 270 -E Start Vim in improved Ex mode |gQ|. Only makes a difference | |
| 271 when the executable is not called "exim". | |
| 272 {not in Vi} | |
| 273 | |
| 274 *-s-ex* | |
| 275 -s Silent or batch mode. Only when Vim was started as "ex" or | |
| 276 when preceded with the "-e" argument. Otherwise see |-s|, | |
| 277 which does take an argument while this use of "-s" doesn't. | |
| 278 To be used when Vim is used to execute Ex commands from a file | |
| 279 instead of a terminal. Switches off most prompts and | |
| 280 informative messages. Also warnings and error messages. | |
| 168 | 281 The output of these commands is displayed (to stdout): |
| 282 :print | |
| 283 :list | |
| 284 :number | |
| 285 :set to display option values. | |
| 286 When 'verbose' is non-zero messages are printed (for | |
| 287 debugging, to stderr). | |
| 288 'term' and $TERM are not used. | |
| 7 | 289 If Vim appears to be stuck try typing "qa!<Enter>". You don't |
| 290 get a prompt thus you can't see Vim is waiting for you to type | |
| 291 something. | |
| 292 Initializations are skipped (except the ones given with the | |
| 293 "-u" argument). | |
| 294 Example: > | |
| 295 vim -e -s < thefilter thefile | |
| 296 < | |
| 297 *-b* | |
| 298 -b Binary mode. File I/O will only recognize <NL> to separate | |
| 237 | 299 lines. The 'expandtab' option will be reset. The 'textwidth' |
| 7 | 300 option is set to 0. 'modeline' is reset. The 'binary' option |
| 301 is set. This is done after reading the vimrc/exrc files but | |
| 302 before reading any file in the arglist. See also | |
| 303 |edit-binary|. {not in Vi} | |
| 304 | |
| 305 *-l* | |
| 306 -l Lisp mode. Sets the 'lisp' and 'showmatch' options on. | |
| 307 | |
| 308 *-A* | |
| 309 -A Arabic mode. Sets the 'arabic' option on. (Only when | |
| 310 compiled with the |+arabic| features (which include | |
| 311 |+rightleft|), otherwise Vim gives an error message | |
| 237 | 312 and exits.) {not in Vi} |
| 7 | 313 |
| 314 *-F* | |
| 315 -F Farsi mode. Sets the 'fkmap' and 'rightleft' options on. | |
| 316 (Only when compiled with |+rightleft| and |+farsi| features, | |
| 237 | 317 otherwise Vim gives an error message and exits.) {not in Vi} |
| 7 | 318 |
| 319 *-H* | |
| 320 -H Hebrew mode. Sets the 'hkmap' and 'rightleft' options on. | |
| 321 (Only when compiled with the |+rightleft| feature, otherwise | |
| 237 | 322 Vim gives an error message and exits.) {not in Vi} |
| 7 | 323 |
| 324 *-V* *verbose* | |
| 325 -V[N] Verbose. Sets the 'verbose' option to [N] (default: 10). | |
| 326 Messages will be given for each file that is ":source"d and | |
| 327 for reading or writing a viminfo file. Can be used to find | |
| 328 out what is happening upon startup and exit. {not in Vi} | |
| 1125 | 329 Example: > |
| 330 vim -V8 foobar | |
| 7 | 331 |
| 294 | 332 -V[N]{filename} |
| 333 Like -V and set 'verbosefile' to {filename}. The result is | |
| 334 that messages are not displayed but written to the file | |
| 335 {filename}. {filename} must not start with a digit. | |
| 1125 | 336 Example: > |
| 337 vim -V20vimlog foobar | |
| 338 < | |
| 7 | 339 *-D* |
| 340 -D Debugging. Go to debugging mode when executing the first | |
| 341 command from a script. |debug-mode| | |
| 342 {not available when compiled without the |+eval| feature} | |
| 343 {not in Vi} | |
| 344 | |
| 345 *-C* | |
| 346 -C Compatible mode. Sets the 'compatible' option. You can use | |
| 347 this to get 'compatible', even though a .vimrc file exists. | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
348 Keep in mind that the command ":set nocompatible" in some |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
349 plugin or startup script overrules this, so you may end up |
| 2072 | 350 with 'nocompatible' anyway. To find out, use: > |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
351 :verbose set compatible? |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
352 < Several plugins won't work with 'compatible' set. You may |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
353 want to set it after startup this way: > |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
354 vim "+set cp" filename |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
355 < Also see |compatible-default|. {not in Vi} |
| 7 | 356 |
| 357 *-N* | |
| 358 -N Not compatible mode. Resets the 'compatible' option. You can | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
359 use this to get 'nocompatible', when there is no .vimrc file |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
360 or when using "-u NONE". |
| 7 | 361 Also see |compatible-default|. {not in Vi} |
| 362 | |
| 363 *-y* *easy* | |
| 364 -y Easy mode. Implied for |evim| and |eview|. Starts with | |
| 365 'insertmode' set and behaves like a click-and-type editor. | |
| 366 This sources the script $VIMRUNTIME/evim.vim. Mappings are | |
| 367 set up to work like most click-and-type editors, see | |
| 368 |evim-keys|. The GUI is started when available. | |
| 369 {not in Vi} | |
| 370 | |
| 371 *-n* | |
| 372 -n No swap file will be used. Recovery after a crash will be | |
| 373 impossible. Handy if you want to view or edit a file on a | |
| 374 very slow medium (e.g., a floppy). | |
| 375 Can also be done with ":set updatecount=0". You can switch it | |
| 376 on again by setting the 'updatecount' option to some value, | |
| 377 e.g., ":set uc=100". | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
378 NOTE: Don't combine -n with -b, making -nb, because that has a |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
379 different meaning: |-nb|. |
| 7 | 380 'updatecount' is set to 0 AFTER executing commands from a |
| 381 vimrc file, but before the GUI initializations. Thus it | |
| 382 overrides a setting for 'updatecount' in a vimrc file, but not | |
| 383 in a gvimrc file. See |startup|. | |
| 384 When you want to reduce accesses to the disk (e.g., for a | |
| 385 laptop), don't use "-n", but set 'updatetime' and | |
| 386 'updatecount' to very big numbers, and type ":preserve" when | |
| 387 you want to save your work. This way you keep the possibility | |
| 388 for crash recovery. | |
| 389 {not in Vi} | |
| 390 | |
| 391 *-o* | |
| 392 -o[N] Open N windows, split horizontally. If [N] is not given, | |
| 393 one window is opened for every file given as argument. If | |
| 394 there is not enough room, only the first few files get a | |
| 395 window. If there are more windows than arguments, the last | |
| 396 few windows will be editing an empty file. | |
| 397 {not in Vi} | |
| 398 | |
| 399 *-O* | |
| 400 -O[N] Open N windows, split vertically. Otherwise it's like -o. | |
| 401 If both the -o and the -O option are given, the last one on | |
| 402 the command line determines how the windows will be split. | |
| 403 {not in Vi} | |
| 404 | |
| 674 | 405 *-p* |
| 406 -p[N] Open N tab pages. If [N] is not given, one tab page is opened | |
| 699 | 407 for every file given as argument. The maximum is set with |
| 408 'tabpagemax' pages (default 10). If there are more tab pages | |
| 409 than arguments, the last few tab pages will be editing an | |
| 805 | 410 empty file. Also see |tabpage|. |
| 674 | 411 {not in Vi} |
| 412 | |
| 7 | 413 *-T* |
| 414 -T {terminal} Set the terminal type to "terminal". This influences the | |
| 415 codes that Vim will send to your terminal. This is normally | |
| 416 not needed, because Vim will be able to find out what type | |
| 237 | 417 of terminal you are using. (See |terminal-info|.) {not in Vi} |
| 7 | 418 |
|
8303
88207f4b861a
commit https://github.com/vim/vim/commit/dae8d21dd291df6a6679a00be64e18bca0156576
Christian Brabandt <cb@256bit.org>
parents:
8253
diff
changeset
|
419 *--not-a-term* |
|
8253
1b6a589a0efc
commit https://github.com/vim/vim/commit/49c39ff678e2ba9f7dc280b25368e12084a610cf
Christian Brabandt <cb@256bit.org>
parents:
8182
diff
changeset
|
420 --not-a-term Tells Vim that the user knows that the input and/or output is |
|
1b6a589a0efc
commit https://github.com/vim/vim/commit/49c39ff678e2ba9f7dc280b25368e12084a610cf
Christian Brabandt <cb@256bit.org>
parents:
8182
diff
changeset
|
421 not connected to a terminal. This will avoid the warning and |
|
8303
88207f4b861a
commit https://github.com/vim/vim/commit/dae8d21dd291df6a6679a00be64e18bca0156576
Christian Brabandt <cb@256bit.org>
parents:
8253
diff
changeset
|
422 the two second delay that would happen. {not in Vi} |
|
8253
1b6a589a0efc
commit https://github.com/vim/vim/commit/49c39ff678e2ba9f7dc280b25368e12084a610cf
Christian Brabandt <cb@256bit.org>
parents:
8182
diff
changeset
|
423 |
| 7 | 424 *-d* |
| 425 -d Start in diff mode, like |vimdiff|. | |
| 426 {not in Vi} {not available when compiled without the |+diff| | |
| 427 feature} | |
| 428 | |
| 429 -d {device} Only on the Amiga and when not compiled with the |+diff| | |
| 430 feature. Works like "-dev". | |
| 431 *-dev* | |
| 432 -dev {device} Only on the Amiga: The {device} is opened to be used for | |
| 433 editing. | |
| 434 Normally you would use this to set the window position and | |
| 435 size: "-d con:x/y/width/height", e.g., | |
| 436 "-d con:30/10/600/150". But you can also use it to start | |
| 437 editing on another device, e.g., AUX:. {not in Vi} | |
| 438 *-f* | |
| 3082 | 439 -f GUI: Do not disconnect from the program that started Vim. |
| 7 | 440 'f' stands for "foreground". If omitted, the GUI forks a new |
| 441 process and exits the current one. "-f" should be used when | |
| 442 gvim is started by a program that will wait for the edit | |
| 443 session to finish (e.g., mail or readnews). If you want gvim | |
| 819 | 444 never to fork, include 'f' in 'guioptions' in your |gvimrc|. |
| 7 | 445 Careful: You can use "-gf" to start the GUI in the foreground, |
| 446 but "-fg" is used to specify the foreground color. |gui-fork| | |
| 3082 | 447 |
| 448 Amiga: Do not restart Vim to open a new window. This | |
| 449 option should be used when Vim is started by a program that | |
| 450 will wait for the edit session to finish (e.g., mail or | |
| 451 readnews). See |amiga-window|. | |
|
4502
605c9ce57ec3
Updated runtime files, language files and translations.
Bram Moolenaar <bram@vim.org>
parents:
3445
diff
changeset
|
452 |
|
4681
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4502
diff
changeset
|
453 MS-Windows: This option is not supported. However, when |
|
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4502
diff
changeset
|
454 running Vim with an installed vim.bat or gvim.bat file it |
|
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
4502
diff
changeset
|
455 works. |
| 7 | 456 {not in Vi} |
| 457 | |
| 3082 | 458 |
| 7 | 459 *--nofork* |
| 460 --nofork GUI: Do not fork. Same as |-f|. | |
| 461 *-u* *E282* | |
| 462 -u {vimrc} The file {vimrc} is read for initializations. Most other | |
| 463 initializations are skipped; see |initialization|. This can | |
| 464 be used to start Vim in a special mode, with special | |
| 465 mappings and settings. A shell alias can be used to make | |
| 466 this easy to use. For example: > | |
| 467 alias vimc vim -u ~/.c_vimrc !* | |
| 468 < Also consider using autocommands; see |autocommand|. | |
| 469 When {vimrc} is equal to "NONE" (all uppercase), all | |
| 470 initializations from files and environment variables are | |
| 819 | 471 skipped, including reading the |gvimrc| file when the GUI |
| 7 | 472 starts. Loading plugins is also skipped. |
| 473 When {vimrc} is equal to "NORC" (all uppercase), this has the | |
| 474 same effect as "NONE", but loading plugins is not skipped. | |
| 475 Using the "-u" argument has the side effect that the | |
| 476 'compatible' option will be on by default. This can have | |
| 477 unexpected effects. See |'compatible'|. | |
| 478 {not in Vi} | |
| 479 | |
| 480 *-U* *E230* | |
| 819 | 481 -U {gvimrc} The file {gvimrc} is read for initializations when the GUI |
| 237 | 482 starts. Other GUI initializations are skipped. When {gvimrc} |
| 43 | 483 is equal to "NONE", no file is read for GUI initializations at |
| 484 all. |gui-init| | |
| 7 | 485 Exception: Reading the system-wide menu file is always done. |
| 486 {not in Vi} | |
| 487 | |
| 488 *-i* | |
| 489 -i {viminfo} The file "viminfo" is used instead of the default viminfo | |
| 490 file. If the name "NONE" is used (all uppercase), no viminfo | |
| 491 file is read or written, even if 'viminfo' is set or when | |
| 492 ":rv" or ":wv" are used. See also |viminfo-file|. | |
| 493 {not in Vi} | |
| 494 | |
| 495 *-x* | |
| 496 -x Use encryption to read/write files. Will prompt for a key, | |
| 497 which is then stored in the 'key' option. All writes will | |
| 498 then use this key to encrypt the text. The '-x' argument is | |
| 499 not needed when reading a file, because there is a check if | |
| 500 the file that is being read has been encrypted, and Vim asks | |
| 501 for a key automatically. |encryption| | |
| 502 | |
| 503 *-X* | |
| 504 -X Do not try connecting to the X server to get the current | |
| 505 window title and copy/paste using the X clipboard. This | |
| 506 avoids a long startup time when running Vim in a terminal | |
| 507 emulator and the connection to the X server is slow. | |
| 1972 | 508 See |--startuptime| to find out if affects you. |
| 7 | 509 Only makes a difference on Unix or VMS, when compiled with the |
| 510 |+X11| feature. Otherwise it's ignored. | |
| 511 To disable the connection only for specific terminals, see the | |
| 512 'clipboard' option. | |
| 513 When the X11 Session Management Protocol (XSMP) handler has | |
| 514 been built in, the -X option also disables that connection as | |
| 515 it, too, may have undesirable delays. | |
| 516 When the connection is desired later anyway (e.g., for | |
| 517 client-server messages), call the |serverlist()| function. | |
| 518 This does not enable the XSMP handler though. | |
| 519 {not in Vi} | |
| 520 | |
| 521 *-s* | |
| 522 -s {scriptin} The script file "scriptin" is read. The characters in the | |
| 523 file are interpreted as if you had typed them. The same can | |
| 524 be done with the command ":source! {scriptin}". If the end | |
| 525 of the file is reached before the editor exits, further | |
| 526 characters are read from the keyboard. Only works when not | |
| 527 started in Ex mode, see |-s-ex|. See also |complex-repeat|. | |
| 528 {not in Vi} | |
| 529 | |
| 164 | 530 *-w_nr* |
| 531 -w {number} | |
| 532 -w{number} Set the 'window' option to {number}. | |
| 533 | |
| 7 | 534 *-w* |
| 535 -w {scriptout} All the characters that you type are recorded in the file | |
| 536 "scriptout", until you exit Vim. This is useful if you want | |
| 537 to create a script file to be used with "vim -s" or | |
| 538 ":source!". When the "scriptout" file already exists, new | |
| 539 characters are appended. See also |complex-repeat|. | |
| 164 | 540 {scriptout} cannot start with a digit. |
| 7 | 541 {not in Vi} |
| 542 | |
| 543 *-W* | |
| 544 -W {scriptout} Like -w, but do not append, overwrite an existing file. | |
| 545 {not in Vi} | |
| 546 | |
| 547 --remote [+{cmd}] {file} ... | |
| 548 Open the {file} in another Vim that functions as a server. | |
| 549 Any non-file arguments must come before this. | |
| 550 See |--remote|. {not in Vi} | |
| 551 | |
| 552 --remote-silent [+{cmd}] {file} ... | |
| 553 Like --remote, but don't complain if there is no server. | |
| 554 See |--remote-silent|. {not in Vi} | |
| 555 | |
| 556 --remote-wait [+{cmd}] {file} ... | |
| 557 Like --remote, but wait for the server to finish editing the | |
| 558 file(s). | |
| 559 See |--remote-wait|. {not in Vi} | |
| 560 | |
| 561 --remote-wait-silent [+{cmd}] {file} ... | |
| 562 Like --remote-wait, but don't complain if there is no server. | |
| 563 See |--remote-wait-silent|. {not in Vi} | |
| 564 | |
| 565 --servername {name} | |
| 566 Specify the name of the Vim server to send to or to become. | |
| 567 See |--servername|. {not in Vi} | |
| 568 | |
| 569 --remote-send {keys} | |
| 570 Send {keys} to a Vim server and exit. | |
| 571 See |--remote-send|. {not in Vi} | |
| 572 | |
| 573 --remote-expr {expr} | |
| 574 Evaluate {expr} in another Vim that functions as a server. | |
| 575 The result is printed on stdout. | |
| 576 See |--remote-expr|. {not in Vi} | |
| 577 | |
| 578 --serverlist Output a list of Vim server names and exit. See | |
| 1125 | 579 |--serverlist|. {not in Vi} |
| 7 | 580 |
| 581 --socketid {id} *--socketid* | |
| 582 GTK+ GUI Vim only. Make gvim try to use GtkPlug mechanism, so | |
| 583 that it runs inside another window. See |gui-gtk-socketid| | |
| 584 for details. {not in Vi} | |
| 585 | |
| 1376 | 586 --windowid {id} *--windowid* |
| 587 Win32 GUI Vim only. Make gvim try to use the window {id} as a | |
| 588 parent, so that it runs inside that window. See | |
| 589 |gui-w32-windowid| for details. {not in Vi} | |
| 590 | |
| 7 | 591 --echo-wid *--echo-wid* |
| 592 GTK+ GUI Vim only. Make gvim echo the Window ID on stdout, | |
| 593 which can be used to run gvim in a kpart widget. The format | |
| 594 of the output is: > | |
| 595 WID: 12345\n | |
| 596 < {not in Vi} | |
| 597 | |
| 598 --role {role} *--role* | |
| 599 GTK+ 2 GUI only. Set the role of the main window to {role}. | |
| 600 The window role can be used by a window manager to uniquely | |
| 601 identify a window, in order to restore window placement and | |
| 602 such. The --role argument is passed automatically when | |
| 603 restoring the session on login. See |gui-gnome-session| | |
| 604 {not in Vi} | |
| 605 | |
| 606 -P {parent-title} *-P* *MDI* *E671* *E672* | |
| 607 Win32 only: Specify the title of the parent application. When | |
| 608 possible, Vim will run in an MDI window inside the | |
| 609 application. | |
| 610 {parent-title} must appear in the window title of the parent | |
| 611 application. Make sure that it is specific enough. | |
| 612 Note that the implementation is still primitive. It won't | |
| 613 work with all applications and the menu doesn't work. | |
| 614 | |
| 615 -nb *-nb* | |
| 616 -nb={fname} | |
| 617 -nb:{hostname}:{addr}:{password} | |
| 618 Attempt connecting to Netbeans and become an editor server for | |
| 619 it. The second form specifies a file to read connection info | |
| 620 from. The third form specifies the hostname, address and | |
| 621 password for connecting to Netbeans. |netbeans-run| | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
622 {only available when compiled with the |+netbeans_intg| |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
623 feature; if not then -nb will make Vim exit} |
| 7 | 624 |
| 625 If the executable is called "view", Vim will start in Readonly mode. This is | |
| 626 useful if you can make a hard or symbolic link from "view" to "vim". | |
| 627 Starting in Readonly mode can also be done with "vim -R". | |
| 628 | |
| 629 If the executable is called "ex", Vim will start in "Ex" mode. This means it | |
| 630 will accept only ":" commands. But when the "-v" argument is given, Vim will | |
| 631 start in Normal mode anyway. | |
| 632 | |
| 633 Additional arguments are available on unix like systems when compiled with | |
| 634 X11 GUI support. See |gui-resources|. | |
| 635 | |
| 636 ============================================================================== | |
| 637 2. Vim on the Amiga *starting-amiga* | |
| 638 | |
| 639 Starting Vim from the Workbench *workbench* | |
| 640 ------------------------------- | |
| 641 | |
| 642 Vim can be started from the Workbench by clicking on its icon twice. It will | |
| 643 then start with an empty buffer. | |
| 644 | |
| 645 Vim can be started to edit one or more files by using a "Project" icon. The | |
| 646 "Default Tool" of the icon must be the full pathname of the Vim executable. | |
| 647 The name of the ".info" file must be the same as the name of the text file. | |
| 648 By clicking on this icon twice, Vim will be started with the file name as | |
| 649 current file name, which will be read into the buffer (if it exists). You can | |
| 650 edit multiple files by pressing the shift key while clicking on icons, and | |
| 651 clicking twice on the last one. The "Default Tool" for all these icons must | |
| 652 be the same. | |
| 653 | |
| 654 It is not possible to give arguments to Vim, other than file names, from the | |
| 655 workbench. | |
| 656 | |
| 657 Vim window *amiga-window* | |
| 658 ---------- | |
| 659 | |
| 660 Vim will run in the CLI window where it was started. If Vim was started with | |
| 661 the "run" or "runback" command, or if Vim was started from the workbench, it | |
| 662 will open a window of its own. | |
| 663 | |
| 664 Technical detail: | |
| 665 To open the new window a little trick is used. As soon as Vim | |
| 666 recognizes that it does not run in a normal CLI window, it will | |
| 667 create a script file in "t:". This script file contains the same | |
| 668 command as the one Vim was started with, and an "endcli" command. | |
| 669 This script file is then executed with a "newcli" command (the "c:run" | |
| 670 and "c:newcli" commands are required for this to work). The script | |
| 671 file will hang around until reboot, or until you delete it. This | |
| 672 method is required to get the ":sh" and ":!" commands to work | |
| 673 correctly. But when Vim was started with the -f option (foreground | |
| 674 mode), this method is not used. The reason for this is that | |
| 675 when a program starts Vim with the -f option it will wait for Vim to | |
| 676 exit. With the script trick, the calling program does not know when | |
| 677 Vim exits. The -f option can be used when Vim is started by a mail | |
| 678 program which also waits for the edit session to finish. As a | |
| 679 consequence, the ":sh" and ":!" commands are not available when the | |
| 680 -f option is used. | |
| 681 | |
| 682 Vim will automatically recognize the window size and react to window | |
| 683 resizing. Under Amiga DOS 1.3, it is advised to use the fastfonts program, | |
| 684 "FF", to speed up display redrawing. | |
| 685 | |
| 686 ============================================================================== | |
| 687 3. Running eVim *evim-keys* | |
| 688 | |
| 689 EVim runs Vim as click-and-type editor. This is very unlike the original Vi | |
| 690 idea. But it helps for people that don't use Vim often enough to learn the | |
| 691 commands. Hopefully they will find out that learning to use Normal mode | |
| 692 commands will make their editing much more effective. | |
| 693 | |
| 694 In Evim these options are changed from their default value: | |
| 695 | |
| 696 :set nocompatible Use Vim improvements | |
| 697 :set insertmode Remain in Insert mode most of the time | |
| 698 :set hidden Keep invisible buffers loaded | |
| 699 :set backup Keep backup files (not for VMS) | |
| 700 :set backspace=2 Backspace over everything | |
| 701 :set autoindent auto-indent new lines | |
| 702 :set history=50 keep 50 lines of Ex commands | |
| 703 :set ruler show the cursor position | |
| 704 :set incsearch show matches halfway typing a pattern | |
| 705 :set mouse=a use the mouse in all modes | |
| 706 :set hlsearch highlight all matches for a search pattern | |
| 707 :set whichwrap+=<,>,[,] <Left> and <Right> wrap around line breaks | |
| 708 :set guioptions-=a non-Unix only: don't do auto-select | |
| 709 | |
| 710 Key mappings: | |
| 711 <Down> moves by screen lines rather than file lines | |
| 712 <Up> idem | |
| 713 Q does "gq", formatting, instead of Ex mode | |
| 714 <BS> in Visual mode: deletes the selection | |
| 715 CTRL-X in Visual mode: Cut to clipboard | |
| 716 <S-Del> idem | |
| 717 CTRL-C in Visual mode: Copy to clipboard | |
| 718 <C-Insert> idem | |
| 719 CTRL-V Pastes from the clipboard (in any mode) | |
| 720 <S-Insert> idem | |
| 721 CTRL-Q do what CTRL-V used to do | |
| 722 CTRL-Z undo | |
| 723 CTRL-Y redo | |
| 724 <M-Space> system menu | |
| 725 CTRL-A select all | |
| 726 <C-Tab> next window, CTRL-W w | |
| 727 <C-F4> close window, CTRL-W c | |
| 728 | |
| 729 Additionally: | |
| 730 - ":behave mswin" is used |:behave| | |
| 731 - syntax highlighting is enabled | |
| 732 - filetype detection is enabled, filetype plugins and indenting is enabled | |
| 733 - in a text file 'textwidth' is set to 78 | |
| 734 | |
| 735 One hint: If you want to go to Normal mode to be able to type a sequence of | |
| 736 commands, use CTRL-L. |i_CTRL-L| | |
| 737 | |
| 738 ============================================================================== | |
| 739 4. Initialization *initialization* *startup* | |
| 740 | |
| 741 This section is about the non-GUI version of Vim. See |gui-fork| for | |
| 742 additional initialization when starting the GUI. | |
| 743 | |
| 744 At startup, Vim checks environment variables and files and sets values | |
| 745 accordingly. Vim proceeds in this order: | |
| 746 | |
| 747 1. Set the 'shell' and 'term' option *SHELL* *COMSPEC* *TERM* | |
| 748 The environment variable SHELL, if it exists, is used to set the | |
| 749 'shell' option. On MS-DOS and Win32, the COMSPEC variable is used | |
| 750 if SHELL is not set. | |
| 751 The environment variable TERM, if it exists, is used to set the 'term' | |
| 667 | 752 option. However, 'term' will change later when starting the GUI (step |
| 753 8 below). | |
| 7 | 754 |
| 755 2. Process the arguments | |
| 756 The options and file names from the command that start Vim are | |
| 757 inspected. Buffers are created for all files (but not loaded yet). | |
| 294 | 758 The |-V| argument can be used to display or log what happens next, |
| 759 useful for debugging the initializations. | |
| 7 | 760 |
| 761 3. Execute Ex commands, from environment variables and/or files | |
| 762 An environment variable is read as one Ex command line, where multiple | |
| 763 commands must be separated with '|' or "<NL>". | |
| 764 *vimrc* *exrc* | |
| 765 A file that contains initialization commands is called a "vimrc" file. | |
| 766 Each line in a vimrc file is executed as an Ex command line. It is | |
| 767 sometimes also referred to as "exrc" file. They are the same type of | |
| 768 file, but "exrc" is what Vi always used, "vimrc" is a Vim specific | |
| 769 name. Also see |vimrc-intro|. | |
| 770 | |
| 4869 | 771 Places for your personal initializations: |
| 772 Unix $HOME/.vimrc or $HOME/.vim/vimrc | |
| 773 OS/2 $HOME/.vimrc, $HOME/vimfiles/vimrc | |
| 774 or $VIM/.vimrc (or _vimrc) | |
| 775 MS-Windows $HOME/_vimrc, $HOME/vimfiles/vimrc | |
| 776 or $VIM/_vimrc | |
| 777 Amiga s:.vimrc, home:.vimrc, home:vimfiles:vimrc | |
| 778 or $VIM/.vimrc | |
| 779 | |
| 780 The files are searched in the order specified above and only the first | |
| 781 one that is found is read. | |
| 782 | |
| 783 RECOMMENDATION: Put all your Vim configuration stuff in the | |
| 784 $HOME/.vim/ directory ($HOME/vimfiles/ for MS-Windows). That makes it | |
| 785 easy to copy it to another system. | |
| 7 | 786 |
| 787 If Vim was started with "-u filename", the file "filename" is used. | |
| 5239 | 788 All following initializations until 4. are skipped. $MYVIMRC is not |
| 789 set. | |
| 7 | 790 "vim -u NORC" can be used to skip these initializations without |
| 791 reading a file. "vim -u NONE" also skips loading plugins. |-u| | |
| 792 | |
| 793 If Vim was started in Ex mode with the "-s" argument, all following | |
| 794 initializations until 4. are skipped. Only the "-u" option is | |
| 795 interpreted. | |
| 796 *evim.vim* | |
| 797 a. If vim was started as |evim| or |eview| or with the |-y| argument, the | |
| 798 script $VIMRUNTIME/evim.vim will be loaded. | |
| 799 *system-vimrc* | |
| 800 b. For Unix, MS-DOS, MS-Windows, OS/2, VMS, Macintosh, RISC-OS and Amiga | |
| 801 the system vimrc file is read for initializations. The path of this | |
| 802 file is shown with the ":version" command. Mostly it's "$VIM/vimrc". | |
| 803 Note that this file is ALWAYS read in 'compatible' mode, since the | |
| 804 automatic resetting of 'compatible' is only done later. Add a ":set | |
| 805 nocp" command if you like. | |
| 810 | 806 For the Macintosh the $VIMRUNTIME/macmap.vim is read. |
| 7 | 807 |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
808 *VIMINIT* *.vimrc* *_vimrc* *EXINIT* *.exrc* *_exrc* *$MYVIMRC* |
|
9669
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
809 c. Five places are searched for initializations. The first that exists |
| 819 | 810 is used, the others are ignored. The $MYVIMRC environment variable is |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
811 set to the file that was first found, unless $MYVIMRC was already set |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
812 and when using VIMINIT. |
|
9669
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
813 I The environment variable VIMINIT (see also |compatible-default|) (*) |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
814 The value of $VIMINIT is used as an Ex command line. |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
815 II The user vimrc file(s): |
| 4869 | 816 "$HOME/.vimrc" (for Unix and OS/2) (*) |
| 817 "$HOME/.vim/vimrc" (for Unix and OS/2) (*) | |
| 818 "s:.vimrc" (for Amiga) (*) | |
| 819 "home:.vimrc" (for Amiga) (*) | |
| 820 "home:vimfiles:vimrc" (for Amiga) (*) | |
| 821 "$VIM/.vimrc" (for OS/2 and Amiga) (*) | |
| 822 "$HOME/_vimrc" (for MS-DOS and Win32) (*) | |
| 823 "$HOME/vimfiles/vimrc" (for MS-DOS and Win32) (*) | |
| 824 "$VIM/_vimrc" (for MS-DOS and Win32) (*) | |
| 7 | 825 Note: For Unix, OS/2 and Amiga, when ".vimrc" does not exist, |
| 826 "_vimrc" is also tried, in case an MS-DOS compatible file | |
| 827 system is used. For MS-DOS and Win32 ".vimrc" is checked | |
| 828 after "_vimrc", in case long file names are used. | |
| 829 Note: For MS-DOS and Win32, "$HOME" is checked first. If no | |
| 830 "_vimrc" or ".vimrc" is found there, "$VIM" is tried. | |
| 831 See |$VIM| for when $VIM is not set. | |
|
9669
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
832 III The environment variable EXINIT. |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
833 The value of $EXINIT is used as an Ex command line. |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
834 IV The user exrc file(s). Same as for the user vimrc file, but with |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
835 "vimrc" replaced by "exrc". But only one of ".exrc" and "_exrc" is |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
836 used, depending on the system. And without the (*)! |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
837 V The default vimrc file, $VIMRUNTIME/defaults.vim. This sets up |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
838 options values and has "syntax on" and "filetype on" commands, |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
839 which is what most new users will want. See |defaults.vim|. |
| 7 | 840 |
| 841 d. If the 'exrc' option is on (which is not the default), the current | |
| 247 | 842 directory is searched for three files. The first that exists is used, |
| 7 | 843 the others are ignored. |
| 844 - The file ".vimrc" (for Unix, Amiga and OS/2) (*) | |
| 845 "_vimrc" (for MS-DOS and Win32) (*) | |
| 846 - The file "_vimrc" (for Unix, Amiga and OS/2) (*) | |
| 847 ".vimrc" (for MS-DOS and Win32) (*) | |
| 848 - The file ".exrc" (for Unix, Amiga and OS/2) | |
| 849 "_exrc" (for MS-DOS and Win32) | |
| 850 | |
| 851 (*) Using this file or environment variable will cause 'compatible' to be | |
| 852 off by default. See |compatible-default|. | |
| 853 | |
| 854 4. Load the plugin scripts. *load-plugins* | |
| 855 This does the same as the command: > | |
| 540 | 856 :runtime! plugin/**/*.vim |
| 7 | 857 < The result is that all directories in the 'runtimepath' option will be |
| 858 searched for the "plugin" sub-directory and all files ending in ".vim" | |
| 540 | 859 will be sourced (in alphabetical order per directory), also in |
| 860 subdirectories. | |
| 7 | 861 Loading plugins won't be done when: |
| 862 - The 'loadplugins' option was reset in a vimrc file. | |
| 863 - The |--noplugin| command line argument is used. | |
| 864 - The "-u NONE" command line argument is used |-u|. | |
| 865 - When Vim was compiled without the |+eval| feature. | |
| 632 | 866 Note that using "-c 'set noloadplugins'" doesn't work, because the |
| 867 commands from the command line have not been executed yet. You can | |
| 868 use "--cmd 'set noloadplugins'" |--cmd|. | |
| 7 | 869 |
|
8876
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8748
diff
changeset
|
870 Packages are loaded. These are plugins, as above, but found in the |
|
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8748
diff
changeset
|
871 "start" directory of each entry in 'packpath'. Every plugin directory |
|
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8748
diff
changeset
|
872 found is added in 'runtimepath' and then the plugins are sourced. See |
|
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8748
diff
changeset
|
873 |packages|. |
|
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8148
diff
changeset
|
874 |
| 7 | 875 5. Set 'shellpipe' and 'shellredir' |
| 876 The 'shellpipe' and 'shellredir' options are set according to the | |
| 877 value of the 'shell' option, unless they have been set before. | |
| 878 This means that Vim will figure out the values of 'shellpipe' and | |
| 879 'shellredir' for you, unless you have set them yourself. | |
| 880 | |
| 881 6. Set 'updatecount' to zero, if "-n" command argument used | |
| 882 | |
| 883 7. Set binary options | |
| 884 If the "-b" flag was given to Vim, the options for binary editing will | |
| 885 be set now. See |-b|. | |
| 886 | |
| 887 8. Perform GUI initializations | |
| 888 Only when starting "gvim", the GUI initializations will be done. See | |
| 889 |gui-init|. | |
| 890 | |
| 891 9. Read the viminfo file | |
| 892 If the 'viminfo' option is not empty, the viminfo file is read. See | |
| 893 |viminfo-file|. | |
| 894 | |
| 895 10. Read the quickfix file | |
| 896 If the "-q" flag was given to Vim, the quickfix file is read. If this | |
| 897 fails, Vim exits. | |
| 898 | |
| 899 11. Open all windows | |
| 900 When the |-o| flag was given, windows will be opened (but not | |
| 901 displayed yet). | |
| 674 | 902 When the |-p| flag was given, tab pages will be created (but not |
| 903 displayed yet). | |
| 7 | 904 When switching screens, it happens now. Redrawing starts. |
| 905 If the "-q" flag was given to Vim, the first error is jumped to. | |
| 906 Buffers for all windows will be loaded. | |
| 907 | |
| 908 12. Execute startup commands | |
| 909 If a "-t" flag was given to Vim, the tag is jumped to. | |
| 910 The commands given with the |-c| and |+cmd| arguments are executed. | |
|
8748
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8440
diff
changeset
|
911 If the 'insertmode' option is set, Insert mode is entered. |
| 2581 | 912 The starting flag is reset, has("vim_starting") will now return zero. |
|
8748
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8440
diff
changeset
|
913 The |v:vim_did_enter| variable is set to 1. |
| 7 | 914 The |VimEnter| autocommands are executed. |
| 915 | |
|
9669
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
916 The $MYVIMRC or $MYGVIMRC file will be set to the first found vimrc and/or |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
917 gvimrc file. |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
918 |
| 7 | 919 Some hints on using initializations: |
| 920 | |
| 921 Standard setup: | |
| 922 Create a vimrc file to set the default settings and mappings for all your edit | |
| 923 sessions. Put it in a place so that it will be found by 3b: | |
| 924 ~/.vimrc (Unix and OS/2) | |
| 925 s:.vimrc (Amiga) | |
| 926 $VIM\_vimrc (MS-DOS and Win32) | |
| 927 Note that creating a vimrc file will cause the 'compatible' option to be off | |
| 928 by default. See |compatible-default|. | |
| 929 | |
| 930 Local setup: | |
| 931 Put all commands that you need for editing a specific directory only into a | |
| 932 vimrc file and place it in that directory under the name ".vimrc" ("_vimrc" | |
| 933 for MS-DOS and Win32). NOTE: To make Vim look for these special files you | |
| 934 have to turn on the option 'exrc'. See |trojan-horse| too. | |
| 935 | |
| 936 System setup: | |
| 937 This only applies if you are managing a Unix system with several users and | |
| 938 want to set the defaults for all users. Create a vimrc file with commands | |
| 939 for default settings and mappings and put it in the place that is given with | |
| 940 the ":version" command. | |
| 941 | |
| 942 Saving the current state of Vim to a file: | |
| 943 Whenever you have changed values of options or when you have created a | |
| 944 mapping, then you may want to save them in a vimrc file for later use. See | |
| 945 |save-settings| about saving the current state of settings to a file. | |
| 946 | |
| 947 Avoiding setup problems for Vi users: | |
| 948 Vi uses the variable EXINIT and the file "~/.exrc". So if you do not want to | |
| 949 interfere with Vi, then use the variable VIMINIT and the file "vimrc" instead. | |
| 950 | |
| 951 Amiga environment variables: | |
| 952 On the Amiga, two types of environment variables exist. The ones set with the | |
| 953 DOS 1.3 (or later) setenv command are recognized. See the AmigaDos 1.3 | |
| 954 manual. The environment variables set with the old Manx Set command (before | |
| 955 version 5.0) are not recognized. | |
| 956 | |
| 957 MS-DOS line separators: | |
| 958 On MS-DOS-like systems (MS-DOS itself, Win32, and OS/2), Vim assumes that all | |
| 959 the vimrc files have <CR> <NL> pairs as line separators. This will give | |
| 960 problems if you have a file with only <NL>s and have a line like | |
| 961 ":map xx yy^M". The trailing ^M will be ignored. | |
| 962 | |
| 963 *compatible-default* | |
| 964 When Vim starts, the 'compatible' option is on. This will be used when Vim | |
|
9669
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
965 starts its initializations. But as soon as: |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
966 - a user vimrc file is found, or |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
967 - a vimrc file in the current directory, or |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
968 - the "VIMINIT" environment variable is set, or |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
969 - the "-N" command line argument is given, or |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
970 even when no vimrc file exists. |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
971 - the |defaults.vim| script is loaded, or |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
972 - gvimrc file was found, |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
973 then it will be set to 'nocompatible'. |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
974 |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
975 Note that this does NOT happen when a system-wide vimrc file was found. |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
976 |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
977 This has the side effect of setting or resetting other options (see |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
978 'compatible'). But only the options that have not been set or reset will be |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
979 changed. This has the same effect like the value of 'compatible' had this |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
980 value when starting Vim. |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
981 |
|
9737
35ce559b8553
commit https://github.com/vim/vim/commit/bc8801c9317eb721a2ee91322669f2dd5d136380
Christian Brabandt <cb@256bit.org>
parents:
9669
diff
changeset
|
982 'compatible' is NOT reset, and |defaults.vim| is not loaded: |
|
9669
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
983 - when Vim was started with the |-u| command line argument, especially with |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
984 "-u NONE", or |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
985 - when started with the |-C| command line argument, or |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
986 - when the name of the executable ends in "ex". (This has been done to make |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
987 Vim behave like "ex", when it is started as "ex") |
| 7 | 988 |
| 989 But there is a side effect of setting or resetting 'compatible' at the moment | |
| 990 a .vimrc file is found: Mappings are interpreted the moment they are | |
| 991 encountered. This makes a difference when using things like "<CR>". If the | |
| 992 mappings depend on a certain value of 'compatible', set or reset it before | |
| 993 giving the mapping. | |
| 994 | |
|
9669
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
995 *defaults.vim* |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
996 If Vim is started normally and no user vimrc file is found, the |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
997 $VIMRUTIME/defaults.vim script is loaded. This will set 'compatible' off, |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
998 switch on syntax highlighting and a few more things. See the script for |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
999 details. NOTE: this is done since Vim 8.0, not in Vim 7.4. (it was added in |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1000 patch 7.4.2111 to be exact). |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1001 |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1002 This should work well for new Vim users. If you create your own .vimrc, it is |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1003 recommended to add this line somewhere near the top: > |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1004 source $VIMRUNTIME/defaults.vim |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1005 Then Vim works like before you had a .vimrc. Copying $VIMRUNTIME/vimrc_example |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1006 is way to do this. Alternatively, you can copy defaults.vim to your .vimrc |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1007 and modify it. |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1008 |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1009 If you don't like some of the defaults, you can still source defaults.vim and |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1010 revert individual settings. See the defaults.vim file for hints on how to |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1011 revert each item. |
|
284b4eb307fc
commit https://github.com/vim/vim/commit/8c08b5b569e2a9e9f63dea514591ecfa2d3bb392
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1012 |
| 7 | 1013 |
| 1014 Avoiding trojan horses: *trojan-horse* | |
| 1015 While reading the "vimrc" or the "exrc" file in the current directory, some | |
| 1016 commands can be disabled for security reasons by setting the 'secure' option. | |
| 1017 This is always done when executing the command from a tags file. Otherwise it | |
| 1018 would be possible that you accidentally use a vimrc or tags file that somebody | |
| 1019 else created and contains nasty commands. The disabled commands are the ones | |
| 1020 that start a shell, the ones that write to a file, and ":autocmd". The ":map" | |
| 1021 commands are echoed, so you can see which keys are being mapped. | |
| 1022 If you want Vim to execute all commands in a local vimrc file, you | |
| 1023 can reset the 'secure' option in the EXINIT or VIMINIT environment variable or | |
| 1024 in the global "exrc" or "vimrc" file. This is not possible in "vimrc" or | |
| 1025 "exrc" in the current directory, for obvious reasons. | |
| 1026 On Unix systems, this only happens if you are not the owner of the | |
| 1027 vimrc file. Warning: If you unpack an archive that contains a vimrc or exrc | |
| 1028 file, it will be owned by you. You won't have the security protection. Check | |
| 1029 the vimrc file before you start Vim in that directory, or reset the 'exrc' | |
| 1030 option. Some Unix systems allow a user to do "chown" on a file. This makes | |
| 1031 it possible for another user to create a nasty vimrc and make you the owner. | |
| 1032 Be careful! | |
| 1033 When using tag search commands, executing the search command (the last | |
| 1034 part of the line in the tags file) is always done in secure mode. This works | |
| 1035 just like executing a command from a vimrc/exrc in the current directory. | |
| 1036 | |
| 1037 *slow-start* | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
1038 If Vim takes a long time to start up, use the |--startuptime| argument to find |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
1039 out what happens. There are a few common causes: |
| 7 | 1040 - If the Unix version was compiled with the GUI and/or X11 (check the output |
| 1041 of ":version" for "+GUI" and "+X11"), it may need to load shared libraries | |
| 1042 and connect to the X11 server. Try compiling a version with GUI and X11 | |
| 1043 disabled. This also should make the executable smaller. | |
| 1044 Use the |-X| command line argument to avoid connecting to the X server when | |
| 1045 running in a terminal. | |
| 1046 - If you have "viminfo" enabled, the loading of the viminfo file may take a | |
| 1047 while. You can find out if this is the problem by disabling viminfo for a | |
| 1048 moment (use the Vim argument "-i NONE", |-i|). Try reducing the number of | |
| 1049 lines stored in a register with ":set viminfo='20,<50,s10". |viminfo-file|. | |
| 1050 | |
| 1051 *:intro* | |
| 1052 When Vim starts without a file name, an introductory message is displayed (for | |
| 1053 those who don't know what Vim is). It is removed as soon as the display is | |
| 1054 redrawn in any way. To see the message again, use the ":intro" command (if | |
| 1055 there is not enough room, you will see only part of it). | |
| 1056 To avoid the intro message on startup, add the 'I' flag to 'shortmess'. | |
| 1057 | |
| 1058 *info-message* | |
| 1059 The |--help| and |--version| arguments cause Vim to print a message and then | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
1060 exit. Normally the message is sent to stdout, thus can be redirected to a |
| 7 | 1061 file with: > |
| 1062 | |
| 1063 vim --help >file | |
| 1064 | |
| 1065 From inside Vim: > | |
| 1066 | |
| 1067 :read !vim --help | |
| 1068 | |
| 1069 When using gvim, it detects that it might have been started from the desktop, | |
| 1070 without a terminal to show messages on. This is detected when both stdout and | |
| 1071 stderr are not a tty. This breaks the ":read" command, as used in the example | |
| 1072 above. To make it work again, set 'shellredir' to ">" instead of the default | |
| 1073 ">&": > | |
| 1074 | |
| 1075 :set shellredir=> | |
| 1076 :read !gvim --help | |
| 1077 | |
| 1078 This still won't work for systems where gvim does not use stdout at all | |
| 1079 though. | |
| 1080 | |
| 1081 ============================================================================== | |
| 1082 5. $VIM and $VIMRUNTIME | |
| 1083 *$VIM* | |
| 1084 The environment variable "$VIM" is used to locate various user files for Vim, | |
| 1085 such as the user startup script ".vimrc". This depends on the system, see | |
| 1086 |startup|. | |
| 1087 | |
| 1088 To avoid the need for every user to set the $VIM environment variable, Vim | |
| 1089 will try to get the value for $VIM in this order: | |
| 1090 1. The value defined by the $VIM environment variable. You can use this to | |
| 1091 make Vim look in a specific directory for its support files. Example: > | |
| 1092 setenv VIM /home/paul/vim | |
| 1093 2. The path from 'helpfile' is used, unless it contains some environment | |
| 1094 variable too (the default is "$VIMRUNTIME/doc/help.txt": chicken-egg | |
| 1095 problem). The file name ("help.txt" or any other) is removed. Then | |
| 1096 trailing directory names are removed, in this order: "doc", "runtime" and | |
| 1097 "vim{version}" (e.g., "vim54"). | |
| 1098 3. For MSDOS, Win32 and OS/2 Vim tries to use the directory name of the | |
| 1099 executable. If it ends in "/src", this is removed. This is useful if you | |
| 1100 unpacked the .zip file in some directory, and adjusted the search path to | |
| 1101 find the vim executable. Trailing directory names are removed, in this | |
| 1102 order: "runtime" and "vim{version}" (e.g., "vim54"). | |
| 1103 4. For Unix the compile-time defined installation directory is used (see the | |
| 1104 output of ":version"). | |
| 1105 | |
| 1106 Once Vim has done this once, it will set the $VIM environment variable. To | |
| 1107 change it later, use a ":let" command like this: > | |
| 1108 :let $VIM = "/home/paul/vim/" | |
| 1109 < | |
| 1110 *$VIMRUNTIME* | |
| 1111 The environment variable "$VIMRUNTIME" is used to locate various support | |
| 1112 files, such as the on-line documentation and files used for syntax | |
| 1113 highlighting. For example, the main help file is normally | |
| 1114 "$VIMRUNTIME/doc/help.txt". | |
| 1115 You don't normally set $VIMRUNTIME yourself, but let Vim figure it out. This | |
| 1116 is the order used to find the value of $VIMRUNTIME: | |
| 1117 1. If the environment variable $VIMRUNTIME is set, it is used. You can use | |
| 1118 this when the runtime files are in an unusual location. | |
| 1119 2. If "$VIM/vim{version}" exists, it is used. {version} is the version | |
| 1120 number of Vim, without any '-' or '.'. For example: "$VIM/vim54". This is | |
| 1121 the normal value for $VIMRUNTIME. | |
| 1122 3. If "$VIM/runtime" exists, it is used. | |
| 1123 4. The value of $VIM is used. This is for backwards compatibility with older | |
| 1124 versions. | |
| 1125 5. When the 'helpfile' option is set and doesn't contain a '$', its value is | |
| 1126 used, with "doc/help.txt" removed from the end. | |
| 1127 | |
| 1128 For Unix, when there is a compiled-in default for $VIMRUNTIME (check the | |
| 1129 output of ":version"), steps 2, 3 and 4 are skipped, and the compiled-in | |
| 1130 default is used after step 5. This means that the compiled-in default | |
| 1131 overrules the value of $VIM. This is useful if $VIM is "/etc" and the runtime | |
| 1132 files are in "/usr/share/vim/vim54". | |
| 1133 | |
| 1134 Once Vim has done this once, it will set the $VIMRUNTIME environment variable. | |
| 1135 To change it later, use a ":let" command like this: > | |
| 1136 :let $VIMRUNTIME = "/home/piet/vim/vim54" | |
| 1137 | |
| 8 | 1138 In case you need the value of $VIMRUNTIME in a shell (e.g., for a script that |
| 1139 greps in the help files) you might be able to use this: > | |
| 1140 | |
| 1141 VIMRUNTIME=`vim -e -T dumb --cmd 'exe "set t_cm=\<C-M>"|echo $VIMRUNTIME|quit' | tr -d '\015' ` | |
| 1142 | |
| 7 | 1143 ============================================================================== |
| 1144 6. Suspending *suspend* | |
| 1145 | |
| 1146 *iconize* *iconise* *CTRL-Z* *v_CTRL-Z* | |
| 1147 CTRL-Z Suspend Vim, like ":stop". | |
| 1148 Works in Normal and in Visual mode. In Insert and | |
| 1149 Command-line mode, the CTRL-Z is inserted as a normal | |
| 1150 character. In Visual mode Vim goes back to Normal | |
| 1151 mode. | |
| 83 | 1152 Note: if CTRL-Z undoes a change see |mswin.vim|. |
| 7 | 1153 |
| 1154 | |
| 1155 :sus[pend][!] or *:sus* *:suspend* *:st* *:stop* | |
| 1156 :st[op][!] Suspend Vim. | |
| 1157 If the '!' is not given and 'autowrite' is set, every | |
| 1158 buffer with changes and a file name is written out. | |
| 1159 If the '!' is given or 'autowrite' is not set, changed | |
| 1160 buffers are not written, don't forget to bring Vim | |
| 1161 back to the foreground later! | |
| 1162 | |
| 1163 In the GUI, suspending is implemented as iconising gvim. In Windows 95/NT, | |
| 1164 gvim is minimized. | |
| 1165 | |
| 1166 On many Unix systems, it is possible to suspend Vim with CTRL-Z. This is only | |
| 1167 possible in Normal and Visual mode (see next chapter, |vim-modes|). Vim will | |
| 1168 continue if you make it the foreground job again. On other systems, CTRL-Z | |
| 1169 will start a new shell. This is the same as the ":sh" command. Vim will | |
| 1170 continue if you exit from the shell. | |
| 1171 | |
| 1172 In X-windows the selection is disowned when Vim suspends. this means you | |
| 1173 can't paste it in another application (since Vim is going to sleep an attempt | |
| 1174 to get the selection would make the program hang). | |
| 1175 | |
| 1176 ============================================================================== | |
|
8148
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1177 7. Exiting *exiting* |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1178 |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1179 There are several ways to exit Vim: |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1180 - Close the last window with `:quit`. Only when there are no changes. |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1181 - Close the last window with `:quit!`. Also when there are changes. |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1182 - Close all windows with `:qall`. Only when there are no changes. |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1183 - Close all windows with `:qall!`. Also when there are changes. |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1184 - Use `:cquit`. Also when there are changes. |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1185 |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1186 When using `:cquit` or when there was an error message Vim exits with exit |
|
8303
88207f4b861a
commit https://github.com/vim/vim/commit/dae8d21dd291df6a6679a00be64e18bca0156576
Christian Brabandt <cb@256bit.org>
parents:
8253
diff
changeset
|
1187 code 1. Errors can be avoided by using `:silent!`. |
|
8148
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1188 |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1189 ============================================================================== |
|
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1190 8. Saving settings *save-settings* |
| 7 | 1191 |
| 1192 Mostly you will edit your vimrc files manually. This gives you the greatest | |
| 1193 flexibility. There are a few commands to generate a vimrc file automatically. | |
| 1194 You can use these files as they are, or copy/paste lines to include in another | |
| 1195 vimrc file. | |
| 1196 | |
| 1197 *:mk* *:mkexrc* | |
| 1198 :mk[exrc] [file] Write current key mappings and changed options to | |
| 1199 [file] (default ".exrc" in the current directory), | |
| 1200 unless it already exists. {not in Vi} | |
| 1201 | |
| 1202 :mk[exrc]! [file] Always write current key mappings and changed | |
| 1203 options to [file] (default ".exrc" in the current | |
| 1204 directory). {not in Vi} | |
| 1205 | |
| 1206 *:mkv* *:mkvimrc* | |
| 1207 :mkv[imrc][!] [file] Like ":mkexrc", but the default is ".vimrc" in the | |
| 1208 current directory. The ":version" command is also | |
| 1209 written to the file. {not in Vi} | |
| 1210 | |
| 1211 These commands will write ":map" and ":set" commands to a file, in such a way | |
| 1212 that when these commands are executed, the current key mappings and options | |
| 1213 will be set to the same values. The options 'columns', 'endofline', | |
| 1214 'fileformat', 'key', 'lines', 'modified', 'scroll', 'term', 'textmode', | |
| 1215 'ttyfast' and 'ttymouse' are not included, because these are terminal or file | |
| 1216 dependent. Note that the options 'binary', 'paste' and 'readonly' are | |
| 1217 included, this might not always be what you want. | |
| 1218 | |
| 1219 When special keys are used in mappings, The 'cpoptions' option will be | |
| 1220 temporarily set to its Vim default, to avoid the mappings to be | |
| 1221 misinterpreted. This makes the file incompatible with Vi, but makes sure it | |
| 1222 can be used with different terminals. | |
| 1223 | |
| 1224 Only global mappings are stored, not mappings local to a buffer. | |
| 1225 | |
| 1226 A common method is to use a default ".vimrc" file, make some modifications | |
| 1227 with ":map" and ":set" commands and write the modified file. First read the | |
| 1228 default ".vimrc" in with a command like ":source ~piet/.vimrc.Cprogs", change | |
| 1229 the settings and then save them in the current directory with ":mkvimrc!". If | |
| 1230 you want to make this file your default .vimrc, move it to your home directory | |
| 1231 (on Unix), s: (Amiga) or $VIM directory (MS-DOS). You could also use | |
| 1232 autocommands |autocommand| and/or modelines |modeline|. | |
| 1233 | |
| 714 | 1234 *vimrc-option-example* |
| 7 | 1235 If you only want to add a single option setting to your vimrc, you can use |
| 1236 these steps: | |
| 1237 1. Edit your vimrc file with Vim. | |
| 1238 2. Play with the option until it's right. E.g., try out different values for | |
| 1239 'guifont'. | |
| 1240 3. Append a line to set the value of the option, using the expression register | |
| 1241 '=' to enter the value. E.g., for the 'guifont' option: > | |
| 1242 o:set guifont=<C-R>=&guifont<CR><Esc> | |
| 1243 < [<C-R> is a CTRL-R, <CR> is a return, <Esc> is the escape key] | |
| 714 | 1244 You need to escape special characters, esp. spaces. |
| 7 | 1245 |
| 1246 Note that when you create a .vimrc file, this can influence the 'compatible' | |
| 1247 option, which has several side effects. See |'compatible'|. | |
| 1248 ":mkvimrc", ":mkexrc" and ":mksession" write the command to set or reset the | |
| 1249 'compatible' option to the output file first, because of these side effects. | |
| 1250 | |
| 1251 ============================================================================== | |
|
8148
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1252 9. Views and Sessions *views-sessions* |
| 7 | 1253 |
| 1254 This is introduced in sections |21.4| and |21.5| of the user manual. | |
| 1255 | |
| 1256 *View* *view-file* | |
| 1257 A View is a collection of settings that apply to one window. You can save a | |
| 1258 View and when you restore it later, the text is displayed in the same way. | |
| 1259 The options and mappings in this window will also be restored, so that you can | |
| 1260 continue editing like when the View was saved. | |
| 1261 | |
| 1262 *Session* *session-file* | |
| 1263 A Session keeps the Views for all windows, plus the global settings. You can | |
| 1264 save a Session and when you restore it later the window layout looks the same. | |
| 1265 You can use a Session to quickly switch between different projects, | |
| 1266 automatically loading the files you were last working on in that project. | |
| 1267 | |
| 1268 Views and Sessions are a nice addition to viminfo-files, which are used to | |
| 1269 remember information for all Views and Sessions together |viminfo-file|. | |
| 1270 | |
| 1271 You can quickly start editing with a previously saved View or Session with the | |
| 1272 |-S| argument: > | |
| 1273 vim -S Session.vim | |
| 1274 < | |
| 1275 All this is {not in Vi} and {not available when compiled without the | |
| 1276 |+mksession| feature}. | |
| 1277 | |
| 1278 *:mks* *:mksession* | |
| 1279 :mks[ession][!] [file] Write a Vim script that restores the current editing | |
| 1280 session. | |
| 1281 When [!] is included an existing file is overwritten. | |
| 1282 When [file] is omitted "Session.vim" is used. | |
| 1283 | |
| 1284 The output of ":mksession" is like ":mkvimrc", but additional commands are | |
| 1285 added to the file. Which ones depends on the 'sessionoptions' option. The | |
| 1286 resulting file, when executed with a ":source" command: | |
| 1287 1. Restores global mappings and options, if 'sessionoptions' contains | |
| 1288 "options". Script-local mappings will not be written. | |
| 1289 2. Restores global variables that start with an uppercase letter and contain | |
| 1290 at least one lowercase letter, if 'sessionoptions' contains "globals". | |
| 1291 3. Unloads all currently loaded buffers. | |
| 1292 4. Restores the current directory if 'sessionoptions' contains "curdir", or | |
| 1293 sets the current directory to where the Session file is if 'sessionoptions' | |
| 1294 contains "sesdir". | |
| 1295 5. Restores GUI Vim window position, if 'sessionoptions' contains "winpos". | |
| 1296 6. Restores screen size, if 'sessionoptions' contains "resize". | |
| 1297 7. Reloads the buffer list, with the last cursor positions. If | |
| 1298 'sessionoptions' contains "buffers" then all buffers are restored, | |
| 1299 including hidden and unloaded buffers. Otherwise only buffers in windows | |
| 1300 are restored. | |
| 1301 8. Restores all windows with the same layout. If 'sessionoptions' contains | |
| 1125 | 1302 "help", help windows are restored. If 'sessionoptions' contains "blank", |
| 1303 windows editing a buffer without a name will be restored. | |
| 7 | 1304 If 'sessionoptions' contains "winsize" and no (help/blank) windows were |
| 1305 left out, the window sizes are restored (relative to the screen size). | |
| 1306 Otherwise, the windows are just given sensible sizes. | |
| 1307 9. Restores the Views for all the windows, as with |:mkview|. But | |
| 1308 'sessionoptions' is used instead of 'viewoptions'. | |
| 1309 10. If a file exists with the same name as the Session file, but ending in | |
| 1310 "x.vim" (for eXtra), executes that as well. You can use *x.vim files to | |
| 1311 specify additional settings and actions associated with a given Session, | |
| 1312 such as creating menu items in the GUI version. | |
| 1313 | |
| 1314 After restoring the Session, the full filename of your current Session is | |
| 1315 available in the internal variable "v:this_session" |this_session-variable|. | |
| 1316 An example mapping: > | |
| 1317 :nmap <F2> :wa<Bar>exe "mksession! " . v:this_session<CR>:so ~/sessions/ | |
| 1318 This saves the current Session, and starts off the command to load another. | |
| 1319 | |
| 841 | 1320 A session includes all tab pages, unless "tabpages" was removed from |
| 1321 'sessionoptions'. |tab-page| | |
| 674 | 1322 |
| 574 | 1323 The |SessionLoadPost| autocmd event is triggered after a session file is |
| 1324 loaded/sourced. | |
| 1325 *SessionLoad-variable* | |
| 1326 While the session file is loading the SessionLoad global variable is set to 1. | |
| 1327 Plugins can use this to postpone some work until the SessionLoadPost event is | |
| 1328 triggered. | |
| 1329 | |
| 7 | 1330 *:mkvie* *:mkview* |
| 1331 :mkvie[w][!] [file] Write a Vim script that restores the contents of the | |
| 1332 current window. | |
| 1333 When [!] is included an existing file is overwritten. | |
| 1334 When [file] is omitted or is a number from 1 to 9, a | |
| 843 | 1335 name is generated and 'viewdir' prepended. When the |
| 5814 | 1336 last path part of 'viewdir' does not exist, this |
| 1337 directory is created. E.g., when 'viewdir' is | |
| 1338 "$VIM/vimfiles/view" then "view" is created in | |
| 1339 "$VIM/vimfiles". | |
| 7 | 1340 An existing file is always overwritten then. Use |
| 1341 |:loadview| to load this view again. | |
| 1342 When [file] is the name of a file ('viewdir' is not | |
| 1343 used), a command to edit the file is added to the | |
| 1344 generated file. | |
| 1345 | |
| 1346 The output of ":mkview" contains these items: | |
| 1347 1. The argument list used in the window. When the global argument list is | |
| 1348 used it is reset to the global list. | |
| 1349 The index in the argument list is also restored. | |
| 1350 2. The file being edited in the window. If there is no file, the window is | |
| 1351 made empty. | |
| 1352 3. Restore mappings, abbreviations and options local to the window if | |
| 1353 'viewoptions' contains "options" or "localoptions". For the options it | |
| 1354 restores only values that are local to the current buffer and values local | |
| 1355 to the window. | |
| 1356 When storing the view as part of a session and "options" is in | |
| 1357 'sessionoptions', global values for local options will be stored too. | |
| 1358 4. Restore folds when using manual folding and 'viewoptions' contains | |
| 1359 "folds". Restore manually opened and closed folds. | |
| 1360 5. The scroll position and the cursor position in the file. Doesn't work very | |
| 1361 well when there are closed folds. | |
| 1362 6. The local current directory, if it is different from the global current | |
| 1363 directory. | |
| 1364 | |
| 1365 Note that Views and Sessions are not perfect: | |
| 1366 - They don't restore everything. For example, defined functions, autocommands | |
| 1367 and ":syntax on" are not included. Things like register contents and | |
| 1368 command line history are in viminfo, not in Sessions or Views. | |
| 9 | 1369 - Global option values are only set when they differ from the default value. |
| 7 | 1370 When the current value is not the default value, loading a Session will not |
| 1371 set it back to the default value. Local options will be set back to the | |
| 1372 default value though. | |
| 1373 - Existing mappings will be overwritten without warning. An existing mapping | |
| 1374 may cause an error for ambiguity. | |
| 1375 - When storing manual folds and when storing manually opened/closed folds, | |
| 1376 changes in the file between saving and loading the view will mess it up. | |
| 1377 - The Vim script is not very efficient. But still faster than typing the | |
| 1378 commands yourself! | |
| 1379 | |
| 1380 *:lo* *:loadview* | |
| 1381 :lo[adview] [nr] Load the view for the current file. When [nr] is | |
| 1382 omitted, the view stored with ":mkview" is loaded. | |
| 1383 When [nr] is specified, the view stored with ":mkview | |
| 1384 [nr]" is loaded. | |
| 1385 | |
| 1386 The combination of ":mkview" and ":loadview" can be used to store up to ten | |
| 1387 different views of a file. These are remembered in the directory specified | |
| 1388 with the 'viewdir' option. The views are stored using the file name. If a | |
| 1389 file is renamed or accessed through a (symbolic) link the view will not be | |
| 1390 found. | |
| 1391 | |
| 1392 You might want to clean up your 'viewdir' directory now and then. | |
| 1393 | |
| 1394 To automatically save and restore views for *.c files: > | |
| 1395 au BufWinLeave *.c mkview | |
| 1396 au BufWinEnter *.c silent loadview | |
| 1397 | |
| 1398 ============================================================================== | |
|
8148
f5da459c5698
commit https://github.com/vim/vim/commit/e0fa3742ead676a3074a10edadbc955e1a89153d
Christian Brabandt <cb@256bit.org>
parents:
6051
diff
changeset
|
1399 10. The viminfo file *viminfo* *viminfo-file* *E136* |
| 7 | 1400 *E575* *E576* *E577* |
| 1401 If you exit Vim and later start it again, you would normally lose a lot of | |
| 1402 information. The viminfo file can be used to remember that information, which | |
| 1403 enables you to continue where you left off. | |
| 1404 | |
| 1405 This is introduced in section |21.3| of the user manual. | |
| 1406 | |
| 1407 The viminfo file is used to store: | |
| 1408 - The command line history. | |
| 1409 - The search string history. | |
| 1410 - The input-line history. | |
| 56 | 1411 - Contents of non-empty registers. |
| 7 | 1412 - Marks for several files. |
| 1413 - File marks, pointing to locations in files. | |
| 1414 - Last search/substitute pattern (for 'n' and '&'). | |
| 1415 - The buffer list. | |
| 1416 - Global variables. | |
| 1417 | |
| 1418 The viminfo file is not supported when the |+viminfo| feature has been | |
| 1419 disabled at compile time. | |
| 1420 | |
| 1421 You could also use a Session file. The difference is that the viminfo file | |
| 1422 does not depend on what you are working on. There normally is only one | |
| 1423 viminfo file. Session files are used to save the state of a specific editing | |
| 1424 Session. You could have several Session files, one for each project you are | |
| 1425 working on. Viminfo and Session files together can be used to effectively | |
| 1426 enter Vim and directly start working in your desired setup. |session-file| | |
| 1427 | |
| 1428 *viminfo-read* | |
| 1429 When Vim is started and the 'viminfo' option is non-empty, the contents of | |
| 1430 the viminfo file are read and the info can be used in the appropriate places. | |
| 1733 | 1431 The |v:oldfiles| variable is filled. The marks are not read in at startup |
| 1432 (but file marks are). See |initialization| for how to set the 'viminfo' | |
| 1433 option upon startup. | |
| 7 | 1434 |
| 1435 *viminfo-write* | |
| 1436 When Vim exits and 'viminfo' is non-empty, the info is stored in the viminfo | |
| 1437 file (it's actually merged with the existing one, if one exists). The | |
| 1438 'viminfo' option is a string containing information about what info should be | |
| 1439 stored, and contains limits on how much should be stored (see 'viminfo'). | |
| 1440 | |
|
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1441 Merging happens in two ways. Most items that have been changed or set in the |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1442 current Vim session are stored, and what was not changed is filled from what |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1443 is currently in the viminfo file. For example: |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1444 - Vim session A reads the viminfo, which contains variable START. |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1445 - Vim session B does the same |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1446 - Vim session A sets the variables AAA and BOTH and exits |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1447 - Vim session B sets the variables BBB and BOTH and exits |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1448 Now the viminfo will have: |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1449 START - it was in the viminfo and wasn't changed in session A or B |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1450 AAA - value from session A, session B kept it |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1451 BBB - value from session B |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1452 BOTH - value from session B, value from session A is lost |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1453 |
|
9464
be72f4201a1d
commit https://github.com/vim/vim/commit/063b9d15abea041a5bfff3ffc4e219e26fd1d4fa
Christian Brabandt <cb@256bit.org>
parents:
9319
diff
changeset
|
1454 *viminfo-timestamp* |
|
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1455 For some items a timestamp is used to keep the last changed version. Here it |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1456 doesn't matter in which sequence Vim sessions exit, the newest item(s) are |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1457 always kept. This is used for: |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1458 - The command line history. |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1459 - The search string history. |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1460 - The input-line history. |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1461 - Contents of non-empty registers. |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1462 - The jump list |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1463 - File marks |
|
9319
1472ed67c36f
commit https://github.com/vim/vim/commit/a02a551e18209423584fcb923e93c6be18f3aa45
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
1464 The timestamp feature was added before Vim 8.0. Older versions of Vim, |
|
1472ed67c36f
commit https://github.com/vim/vim/commit/a02a551e18209423584fcb923e93c6be18f3aa45
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
1465 starting with 7.4.1131, will keep the items with timestamp, but not use them. |
|
1472ed67c36f
commit https://github.com/vim/vim/commit/a02a551e18209423584fcb923e93c6be18f3aa45
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
1466 Thus when using both an older and a newer version of Vim the most recent data |
|
1472ed67c36f
commit https://github.com/vim/vim/commit/a02a551e18209423584fcb923e93c6be18f3aa45
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
1467 will be kept. |
|
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1468 |
| 7 | 1469 Notes for Unix: |
| 1470 - The file protection for the viminfo file will be set to prevent other users | |
| 1471 from being able to read it, because it may contain any text or commands that | |
| 1472 you have worked with. | |
| 1473 - If you want to share the viminfo file with other users (e.g. when you "su" | |
| 1474 to another user), you can make the file writable for the group or everybody. | |
| 1475 Vim will preserve this when writing new viminfo files. Be careful, don't | |
| 1476 allow just anybody to read and write your viminfo file! | |
| 1477 - Vim will not overwrite a viminfo file that is not writable by the current | |
| 1478 "real" user. This helps for when you did "su" to become root, but your | |
| 1479 $HOME is still set to a normal user's home directory. Otherwise Vim would | |
| 1480 create a viminfo file owned by root that nobody else can read. | |
| 1270 | 1481 - The viminfo file cannot be a symbolic link. This is to avoid security |
| 1482 issues. | |
| 7 | 1483 |
| 1484 Marks are stored for each file separately. When a file is read and 'viminfo' | |
| 1485 is non-empty, the marks for that file are read from the viminfo file. NOTE: | |
| 1486 The marks are only written when exiting Vim, which is fine because marks are | |
| 1487 remembered for all the files you have opened in the current editing session, | |
| 1488 unless ":bdel" is used. If you want to save the marks for a file that you are | |
| 1489 about to abandon with ":bdel", use ":wv". The '[' and ']' marks are not | |
| 1490 stored, but the '"' mark is. The '"' mark is very useful for jumping to the | |
| 1491 cursor position when the file was last exited. No marks are saved for files | |
| 1492 that start with any string given with the "r" flag in 'viminfo'. This can be | |
| 1493 used to avoid saving marks for files on removable media (for MS-DOS you would | |
| 1494 use "ra:,rb:", for Amiga "rdf0:,rdf1:,rdf2:"). | |
| 1733 | 1495 The |v:oldfiles| variable is filled with the file names that the viminfo file |
| 1496 has marks for. | |
| 7 | 1497 |
| 1498 *viminfo-file-marks* | |
| 1499 Uppercase marks ('A to 'Z) are stored when writing the viminfo file. The | |
| 1500 numbered marks ('0 to '9) are a bit special. When the viminfo file is written | |
| 1501 (when exiting or with the ":wviminfo" command), '0 is set to the current cursor | |
| 1502 position and file. The old '0 is moved to '1, '1 to '2, etc. This | |
| 1503 resembles what happens with the "1 to "9 delete registers. If the current | |
| 1504 cursor position is already present in '0 to '9, it is moved to '0, to avoid | |
| 1505 having the same position twice. The result is that with "'0", you can jump | |
| 1506 back to the file and line where you exited Vim. To do that right away, try | |
| 1507 using this command: > | |
| 1508 | |
| 1509 vim -c "normal '0" | |
| 1510 | |
| 1623 | 1511 In a csh compatible shell you could make an alias for it: > |
| 7 | 1512 |
| 1513 alias lvim vim -c '"'normal "'"0'"' | |
| 1514 | |
| 1623 | 1515 For a bash-like shell: > |
| 1516 | |
| 1517 alias lvim='vim -c "normal '\''0"' | |
| 1518 | |
| 7 | 1519 Use the "r" flag in 'viminfo' to specify for which files no marks should be |
| 1520 remembered. | |
| 1521 | |
| 1522 | |
| 1523 VIMINFO FILE NAME *viminfo-file-name* | |
| 1524 | |
| 1525 - The default name of the viminfo file is "$HOME/.viminfo" for Unix and OS/2, | |
| 1526 "s:.viminfo" for Amiga, "$HOME\_viminfo" for MS-DOS and Win32. For the last | |
| 1527 two, when $HOME is not set, "$VIM\_viminfo" is used. When $VIM is also not | |
| 1528 set, "c:\_viminfo" is used. For OS/2 "$VIM/.viminfo" is used when $HOME is | |
| 1529 not set and $VIM is set. | |
| 1530 - The 'n' flag in the 'viminfo' option can be used to specify another viminfo | |
| 1531 file name |'viminfo'|. | |
| 1532 - The "-i" Vim argument can be used to set another file name, |-i|. When the | |
| 1533 file name given is "NONE" (all uppercase), no viminfo file is ever read or | |
| 1534 written. Also not for the commands below! | |
| 1535 - For the commands below, another file name can be given, overriding the | |
| 1536 default and the name given with 'viminfo' or "-i" (unless it's NONE). | |
| 1537 | |
| 1538 | |
| 1539 CHARACTER ENCODING *viminfo-encoding* | |
| 1540 | |
| 1541 The text in the viminfo file is encoded as specified with the 'encoding' | |
| 1542 option. Normally you will always work with the same 'encoding' value, and | |
| 1543 this works just fine. However, if you read the viminfo file with another | |
| 1544 value for 'encoding' than what it was written with, some of the text | |
| 1545 (non-ASCII characters) may be invalid. If this is unacceptable, add the 'c' | |
| 1546 flag to the 'viminfo' option: > | |
| 1547 :set viminfo+=c | |
| 1548 Vim will then attempt to convert the text in the viminfo file from the | |
| 1549 'encoding' value it was written with to the current 'encoding' value. This | |
| 1550 requires Vim to be compiled with the |+iconv| feature. Filenames are not | |
| 1551 converted. | |
| 1552 | |
| 1553 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
1554 MANUALLY READING AND WRITING *viminfo-read-write* |
| 7 | 1555 |
| 1556 Two commands can be used to read and write the viminfo file manually. This | |
| 1557 can be used to exchange registers between two running Vim programs: First | |
| 1558 type ":wv" in one and then ":rv" in the other. Note that if the register | |
| 1559 already contained something, then ":rv!" would be required. Also note | |
| 1560 however that this means everything will be overwritten with information from | |
| 1561 the first Vim, including the command line history, etc. | |
| 1562 | |
| 1563 The viminfo file itself can be edited by hand too, although we suggest you | |
| 1564 start with an existing one to get the format right. It is reasonably | |
| 1565 self-explanatory once you're in there. This can be useful in order to | |
| 1566 create a second file, say "~/.my_viminfo" which could contain certain | |
| 1567 settings that you always want when you first start Vim. For example, you | |
| 1568 can preload registers with particular data, or put certain commands in the | |
| 1569 command line history. A line in your .vimrc file like > | |
| 1570 :rviminfo! ~/.my_viminfo | |
| 1571 can be used to load this information. You could even have different viminfos | |
| 1572 for different types of files (e.g., C code) and load them based on the file | |
| 1573 name, using the ":autocmd" command (see |:autocmd|). | |
| 1574 | |
| 1575 *viminfo-errors* | |
| 1576 When Vim detects an error while reading a viminfo file, it will not overwrite | |
| 1577 that file. If there are more than 10 errors, Vim stops reading the viminfo | |
| 1578 file. This was done to avoid accidentally destroying a file when the file | |
| 1579 name of the viminfo file is wrong. This could happen when accidentally typing | |
| 1580 "vim -i file" when you wanted "vim -R file" (yes, somebody accidentally did | |
| 1581 that!). If you want to overwrite a viminfo file with an error in it, you will | |
| 1582 either have to fix the error, or delete the file (while Vim is running, so | |
| 1583 most of the information will be restored). | |
| 1584 | |
| 1585 *:rv* *:rviminfo* *E195* | |
| 1586 :rv[iminfo][!] [file] Read from viminfo file [file] (default: see above). | |
| 1587 If [!] is given, then any information that is | |
| 1733 | 1588 already set (registers, marks, |v:oldfiles|, etc.) |
| 1589 will be overwritten {not in Vi} | |
| 7 | 1590 |
|
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1591 *:wv* *:wviminfo* *E137* *E138* *E574* *E886* *E929* |
| 7 | 1592 :wv[iminfo][!] [file] Write to viminfo file [file] (default: see above). |
| 1593 The information in the file is first read in to make | |
| 1594 a merge between old and new info. When [!] is used, | |
| 1595 the old information is not read first, only the | |
| 1596 internal info is written. If 'viminfo' is empty, marks | |
| 1597 for up to 100 files will be written. | |
|
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
1598 When you get error "E929: Too many viminfo temp files" |
| 7 | 1599 check that no old temp files were left behind (e.g. |
| 1600 ~/.viminf*) and that you can write in the directory of | |
| 1601 the .viminfo file. | |
| 1602 {not in Vi} | |
| 1603 | |
| 1733 | 1604 *:ol* *:oldfiles* |
| 1605 :ol[dfiles] List the files that have marks stored in the viminfo | |
| 1606 file. This list is read on startup and only changes | |
| 1607 afterwards with ":rviminfo!". Also see |v:oldfiles|. | |
| 1608 The number can be used with |c_#<|. | |
|
2570
71b56b4e7785
Make the references to features in the help more consistent. (Sylvain Hitier)
Bram Moolenaar <bram@vim.org>
parents:
2561
diff
changeset
|
1609 {not in Vi, only when compiled with the |+eval| |
|
71b56b4e7785
Make the references to features in the help more consistent. (Sylvain Hitier)
Bram Moolenaar <bram@vim.org>
parents:
2561
diff
changeset
|
1610 feature} |
| 1733 | 1611 |
| 1612 :bro[wse] ol[dfiles][!] | |
| 1613 List file names as with |:oldfiles|, and then prompt | |
| 1614 for a number. When the number is valid that file from | |
| 1615 the list is edited. | |
| 1616 If you get the |press-enter| prompt you can press "q" | |
| 1617 and still get the prompt to enter a file number. | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1989
diff
changeset
|
1618 Use ! to abandon a modified buffer. |abandon| |
| 1733 | 1619 {not when compiled with tiny or small features} |
| 1620 | |
| 7 | 1621 vim:tw=78:ts=8:ft=help:norl: |