Mercurial > vim
annotate runtime/doc/editing.txt @ 7659:07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Jan 17 22:26:33 2016 +0100
Update help files.
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Sun, 17 Jan 2016 22:30:06 +0100 |
| parents | a49163681559 |
| children | 93f747af7b58 |
| rev | line source |
|---|---|
|
7659
07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Christian Brabandt <cb@256bit.org>
parents:
7480
diff
changeset
|
1 *editing.txt* For Vim version 7.4. Last change: 2016 Jan 17 |
| 7 | 2 |
| 3 | |
| 4 VIM REFERENCE MANUAL by Bram Moolenaar | |
| 5 | |
| 6 | |
| 7 Editing files *edit-files* | |
| 8 | |
| 9 1. Introduction |edit-intro| | |
| 10 2. Editing a file |edit-a-file| | |
| 39 | 11 3. The argument list |argument-list| |
| 12 4. Writing |writing| | |
| 13 5. Writing and quitting |write-quit| | |
| 14 6. Dialogs |edit-dialogs| | |
| 15 7. The current directory |current-directory| | |
| 7 | 16 8. Editing binary files |edit-binary| |
| 17 9. Encryption |encryption| | |
| 18 10. Timestamps |timestamps| | |
| 39 | 19 11. File Searching |file-searching| |
| 7 | 20 |
| 21 ============================================================================== | |
| 22 1. Introduction *edit-intro* | |
| 23 | |
| 24 Editing a file with Vim means: | |
| 25 | |
| 39 | 26 1. reading the file into a buffer |
| 7 | 27 2. changing the buffer with editor commands |
| 28 3. writing the buffer into a file | |
| 29 | |
| 30 *current-file* | |
| 31 As long as you don't write the buffer, the original file remains unchanged. | |
| 32 If you start editing a file (read a file into the buffer), the file name is | |
| 22 | 33 remembered as the "current file name". This is also known as the name of the |
| 39 | 34 current buffer. It can be used with "%" on the command line |:_%|. |
| 7 | 35 |
| 36 *alternate-file* | |
| 37 If there already was a current file name, then that one becomes the alternate | |
| 39 | 38 file name. It can be used with "#" on the command line |:_#| and you can use |
| 39 the |CTRL-^| command to toggle between the current and the alternate file. | |
| 40 However, the alternate file name is not changed when |:keepalt| is used. | |
| 5510 | 41 An alternate file name is remembered for each window. |
| 22 | 42 |
| 43 *:keepalt* *:keepa* | |
| 44 :keepalt {cmd} Execute {cmd} while keeping the current alternate file | |
| 45 name. Note that commands invoked indirectly (e.g., | |
| 46 with a function) may still set the alternate file | |
| 47 name. {not in Vi} | |
| 48 | |
| 39 | 49 All file names are remembered in the buffer list. When you enter a file name, |
| 236 | 50 for editing (e.g., with ":e filename") or writing (e.g., with ":w filename"), |
| 39 | 51 the file name is added to the list. You can use the buffer list to remember |
| 52 which files you edited and to quickly switch from one file to another (e.g., | |
| 53 to copy text) with the |CTRL-^| command. First type the number of the file | |
| 54 and then hit CTRL-^. {Vi: only one alternate file name is remembered} | |
| 55 | |
| 7 | 56 |
| 57 CTRL-G or *CTRL-G* *:f* *:fi* *:file* | |
| 268 | 58 :f[ile] Prints the current file name (as typed, unless ":cd" |
| 59 was used), the cursor position (unless the 'ruler' | |
| 60 option is set), and the file status (readonly, | |
| 61 modified, read errors, new file). See the 'shortmess' | |
| 62 option about how to make this message shorter. | |
| 63 {Vi does not include column number} | |
| 7 | 64 |
| 14 | 65 :f[ile]! like |:file|, but don't truncate the name even when |
| 66 'shortmess' indicates this. | |
| 67 | |
| 7 | 68 {count}CTRL-G Like CTRL-G, but prints the current file name with |
| 69 full path. If the count is higher than 1 the current | |
| 70 buffer number is also given. {not in Vi} | |
| 71 | |
| 72 *g_CTRL-G* *word-count* *byte-count* | |
| 161 | 73 g CTRL-G Prints the current position of the cursor in five |
| 74 ways: Column, Line, Word, Character and Byte. If the | |
| 75 number of Characters and Bytes is the same then the | |
| 76 Character position is omitted. | |
| 77 If there are characters in the line that take more | |
| 78 than one position on the screen (<Tab> or special | |
| 79 character), both the "real" column and the screen | |
| 80 column are shown, separated with a dash. | |
|
7480
a49163681559
commit https://github.com/vim/vim/commit/ed767a2073ef150971b0439a58e7ee582af6984e
Christian Brabandt <cb@256bit.org>
parents:
7477
diff
changeset
|
81 Also see the 'ruler' option and the |wordcount()| |
|
a49163681559
commit https://github.com/vim/vim/commit/ed767a2073ef150971b0439a58e7ee582af6984e
Christian Brabandt <cb@256bit.org>
parents:
7477
diff
changeset
|
82 function. |
|
a49163681559
commit https://github.com/vim/vim/commit/ed767a2073ef150971b0439a58e7ee582af6984e
Christian Brabandt <cb@256bit.org>
parents:
7477
diff
changeset
|
83 {not in Vi} |
| 7 | 84 |
| 85 *v_g_CTRL-G* | |
| 161 | 86 {Visual}g CTRL-G Similar to "g CTRL-G", but Word, Character, Line, and |
| 87 Byte counts for the visually selected region are | |
| 88 displayed. | |
| 89 In Blockwise mode, Column count is also shown. (For | |
| 7 | 90 {Visual} see |Visual-mode|.) |
| 91 {not in VI} | |
| 92 | |
| 93 *:file_f* | |
| 14 | 94 :f[ile][!] {name} Sets the current file name to {name}. The optional ! |
| 95 avoids truncating the message, as with |:file|. | |
| 28 | 96 If the buffer did have a name, that name becomes the |
| 97 |alternate-file| name. An unlisted buffer is created | |
| 98 to hold the old name. | |
| 139 | 99 *:0file* |
| 14 | 100 :0f[ile][!] Remove the name of the current buffer. The optional ! |
| 101 avoids truncating the message, as with |:file|. {not | |
| 102 in Vi} | |
| 7 | 103 |
| 104 :buffers | |
| 105 :files | |
| 106 :ls List all the currently known file names. See | |
| 107 'windows.txt' |:files| |:buffers| |:ls|. {not in | |
| 108 Vi} | |
| 109 | |
| 110 Vim will remember the full path name of a file name that you enter. In most | |
| 111 cases when the file name is displayed only the name you typed is shown, but | |
| 112 the full path name is being used if you used the ":cd" command |:cd|. | |
| 113 | |
| 114 *home-replace* | |
| 115 If the environment variable $HOME is set, and the file name starts with that | |
| 116 string, it is often displayed with HOME replaced with "~". This was done to | |
| 117 keep file names short. When reading or writing files the full name is still | |
| 118 used, the "~" is only used when displaying file names. When replacing the | |
| 119 file name would result in just "~", "~/" is used instead (to avoid confusion | |
| 42 | 120 between options set to $HOME with 'backupext' set to "~"). |
| 7 | 121 |
| 122 When writing the buffer, the default is to use the current file name. Thus | |
| 123 when you give the "ZZ" or ":wq" command, the original file will be | |
| 124 overwritten. If you do not want this, the buffer can be written into another | |
| 125 file by giving a file name argument to the ":write" command. For example: > | |
| 126 | |
| 127 vim testfile | |
| 128 [change the buffer with editor commands] | |
| 129 :w newfile | |
| 130 :q | |
| 131 | |
| 132 This will create a file "newfile", that is a modified copy of "testfile". | |
| 133 The file "testfile" will remain unchanged. Anyway, if the 'backup' option is | |
| 134 set, Vim renames or copies the original file before it will be overwritten. | |
| 135 You can use this file if you discover that you need the original file. See | |
| 136 also the 'patchmode' option. The name of the backup file is normally the same | |
| 137 as the original file with 'backupext' appended. The default "~" is a bit | |
| 138 strange to avoid accidentally overwriting existing files. If you prefer ".bak" | |
| 139 change the 'backupext' option. Extra dots are replaced with '_' on MS-DOS | |
| 140 machines, when Vim has detected that an MS-DOS-like filesystem is being used | |
| 141 (e.g., messydos or crossdos) or when the 'shortname' option is on. The | |
| 142 backup file can be placed in another directory by setting 'backupdir'. | |
| 143 | |
| 144 *auto-shortname* | |
| 145 Technical: On the Amiga you can use 30 characters for a file name. But on an | |
| 146 MS-DOS-compatible filesystem only 8 plus 3 characters are | |
| 147 available. Vim tries to detect the type of filesystem when it is | |
| 148 creating the .swp file. If an MS-DOS-like filesystem is suspected, | |
| 149 a flag is set that has the same effect as setting the 'shortname' | |
| 150 option. This flag will be reset as soon as you start editing a | |
| 151 new file. The flag will be used when making the file name for the | |
| 152 ".swp" and ".~" files for the current file. But when you are | |
| 153 editing a file in a normal filesystem and write to an MS-DOS-like | |
| 154 filesystem the flag will not have been set. In that case the | |
| 155 creation of the ".~" file may fail and you will get an error | |
| 156 message. Use the 'shortname' option in this case. | |
| 157 | |
| 158 When you started editing without giving a file name, "No File" is displayed in | |
| 159 messages. If the ":write" command is used with a file name argument, the file | |
| 160 name for the current file is set to that file name. This only happens when | |
| 633 | 161 the 'F' flag is included in 'cpoptions' (by default it is included) |cpo-F|. |
| 162 This is useful when entering text in an empty buffer and then writing it to a | |
| 163 file. If 'cpoptions' contains the 'f' flag (by default it is NOT included) | |
| 164 |cpo-f| the file name is set for the ":read file" command. This is useful | |
| 165 when starting Vim without an argument and then doing ":read file" to start | |
| 166 editing a file. | |
| 167 When the file name was set and 'filetype' is empty the filetype detection | |
| 168 autocommands will be triggered. | |
| 7 | 169 *not-edited* |
| 170 Because the file name was set without really starting to edit that file, you | |
| 171 are protected from overwriting that file. This is done by setting the | |
| 172 "notedited" flag. You can see if this flag is set with the CTRL-G or ":file" | |
| 173 command. It will include "[Not edited]" when the "notedited" flag is set. | |
| 174 When writing the buffer to the current file name (with ":w!"), the "notedited" | |
| 175 flag is reset. | |
| 176 | |
| 177 *abandon* | |
| 178 Vim remembers whether you have changed the buffer. You are protected from | |
| 179 losing the changes you made. If you try to quit without writing, or want to | |
| 180 start editing another file, Vim will refuse this. In order to overrule this | |
| 181 protection, add a '!' to the command. The changes will then be lost. For | |
| 182 example: ":q" will not work if the buffer was changed, but ":q!" will. To see | |
| 183 whether the buffer was changed use the "CTRL-G" command. The message includes | |
| 184 the string "[Modified]" if the buffer has been changed. | |
| 185 | |
| 186 If you want to automatically save the changes without asking, switch on the | |
| 187 'autowriteall' option. 'autowrite' is the associated Vi-compatible option | |
| 188 that does not work for all commands. | |
| 189 | |
| 190 If you want to keep the changed buffer without saving it, switch on the | |
| 5277 | 191 'hidden' option. See |hidden-buffer|. Some commands work like this even when |
| 192 'hidden' is not set, check the help for the command. | |
| 7 | 193 |
| 194 ============================================================================== | |
| 195 2. Editing a file *edit-a-file* | |
| 196 | |
| 5277 | 197 *:e* *:edit* *reload* |
| 7 | 198 :e[dit] [++opt] [+cmd] Edit the current file. This is useful to re-edit the |
| 199 current file, when it has been changed outside of Vim. | |
| 200 This fails when changes have been made to the current | |
| 201 buffer and 'autowriteall' isn't set or the file can't | |
| 202 be written. | |
| 203 Also see |++opt| and |+cmd|. | |
| 204 {Vi: no ++opt} | |
| 205 | |
| 5277 | 206 *:edit!* *discard* |
| 7 | 207 :e[dit]! [++opt] [+cmd] |
| 208 Edit the current file always. Discard any changes to | |
| 209 the current buffer. This is useful if you want to | |
| 210 start all over again. | |
| 211 Also see |++opt| and |+cmd|. | |
| 212 {Vi: no ++opt} | |
| 213 | |
| 214 *:edit_f* | |
| 215 :e[dit] [++opt] [+cmd] {file} | |
| 216 Edit {file}. | |
| 217 This fails when changes have been made to the current | |
| 218 buffer, unless 'hidden' is set or 'autowriteall' is | |
| 219 set and the file can be written. | |
| 220 Also see |++opt| and |+cmd|. | |
| 221 {Vi: no ++opt} | |
| 222 | |
| 223 *:edit!_f* | |
| 224 :e[dit]! [++opt] [+cmd] {file} | |
| 225 Edit {file} always. Discard any changes to the | |
| 226 current buffer. | |
| 227 Also see |++opt| and |+cmd|. | |
| 228 {Vi: no ++opt} | |
| 229 | |
| 230 :e[dit] [++opt] [+cmd] #[count] | |
| 39 | 231 Edit the [count]th buffer (as shown by |:files|). |
| 232 This command does the same as [count] CTRL-^. But ":e | |
| 233 #" doesn't work if the alternate buffer doesn't have a | |
| 234 file name, while CTRL-^ still works then. | |
| 7 | 235 Also see |++opt| and |+cmd|. |
| 236 {Vi: no ++opt} | |
| 237 | |
| 238 *:ene* *:enew* | |
| 239 :ene[w] Edit a new, unnamed buffer. This fails when changes | |
| 240 have been made to the current buffer, unless 'hidden' | |
| 241 is set or 'autowriteall' is set and the file can be | |
| 242 written. | |
| 243 If 'fileformats' is not empty, the first format given | |
| 244 will be used for the new buffer. If 'fileformats' is | |
| 245 empty, the 'fileformat' of the current buffer is used. | |
| 246 {not in Vi} | |
| 247 | |
| 248 *:ene!* *:enew!* | |
| 249 :ene[w]! Edit a new, unnamed buffer. Discard any changes to | |
| 250 the current buffer. | |
| 251 Set 'fileformat' like |:enew|. | |
| 252 {not in Vi} | |
| 253 | |
| 254 *:fin* *:find* | |
| 255 :fin[d][!] [++opt] [+cmd] {file} | |
| 256 Find {file} in 'path' and then |:edit| it. | |
| 257 {not in Vi} {not available when the |+file_in_path| | |
| 258 feature was disabled at compile time} | |
| 259 | |
| 260 :{count}fin[d][!] [++opt] [+cmd] {file} | |
| 261 Just like ":find", but use the {count} match in | |
| 262 'path'. Thus ":2find file" will find the second | |
| 263 "file" found in 'path'. When there are fewer matches | |
| 264 for the file in 'path' than asked for, you get an | |
| 265 error message. | |
| 266 | |
| 267 *:ex* | |
| 268 :ex [++opt] [+cmd] [file] | |
| 269 Same as |:edit|. | |
| 270 | |
| 271 *:vi* *:visual* | |
| 272 :vi[sual][!] [++opt] [+cmd] [file] | |
| 42 | 273 When used in Ex mode: Leave |Ex-mode|, go back to |
| 7 | 274 Normal mode. Otherwise same as |:edit|. |
| 275 | |
| 276 *:vie* *:view* | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
277 :vie[w][!] [++opt] [+cmd] file |
| 42 | 278 When used in Ex mode: Leave |Ex mode|, go back to |
| 7 | 279 Normal mode. Otherwise same as |:edit|, but set |
| 280 'readonly' option for this buffer. {not in Vi} | |
| 281 | |
| 282 *CTRL-^* *CTRL-6* | |
| 2725 | 283 CTRL-^ Edit the alternate file. Mostly the alternate file is |
| 284 the previously edited file. This is a quick way to | |
| 285 toggle between two files. It is equivalent to ":e #", | |
| 286 except that it also works when there is no file name. | |
| 287 | |
| 7 | 288 If the 'autowrite' or 'autowriteall' option is on and |
| 289 the buffer was changed, write it. | |
| 290 Mostly the ^ character is positioned on the 6 key, | |
| 291 pressing CTRL and 6 then gets you what we call CTRL-^. | |
| 292 But on some non-US keyboards CTRL-^ is produced in | |
| 293 another way. | |
| 294 | |
| 39 | 295 {count}CTRL-^ Edit [count]th file in the buffer list (equivalent to |
| 296 ":e #[count]"). This is a quick way to switch between | |
| 297 files. | |
| 298 See |CTRL-^| above for further details. | |
| 299 {not in Vi} | |
| 300 | |
| 7 | 301 [count]]f *]f* *[f* |
| 302 [count][f Same as "gf". Deprecated. | |
| 303 | |
| 304 *gf* *E446* *E447* | |
| 305 [count]gf Edit the file whose name is under or after the cursor. | |
| 306 Mnemonic: "goto file". | |
| 307 Uses the 'isfname' option to find out which characters | |
| 308 are supposed to be in a file name. Trailing | |
| 6647 | 309 punctuation characters ".,:;!" are ignored. Escaped |
| 310 spaces "\ " are reduced to a single space. | |
| 1668 | 311 Uses the 'path' option as a list of directory names to |
| 312 look for the file. See the 'path' option for details | |
| 313 about relative directories and wildcards. | |
| 7 | 314 Uses the 'suffixesadd' option to check for file names |
| 315 with a suffix added. | |
| 316 If the file can't be found, 'includeexpr' is used to | |
| 317 modify the name and another attempt is done. | |
| 318 If a [count] is given, the count'th file that is found | |
| 319 in the 'path' is edited. | |
| 320 This command fails if Vim refuses to |abandon| the | |
| 321 current file. | |
| 820 | 322 If you want to edit the file in a new window use |
| 323 |CTRL-W_CTRL-F|. | |
| 7 | 324 If you do want to edit a new file, use: > |
| 325 :e <cfile> | |
| 326 < To make gf always work like that: > | |
| 327 :map gf :e <cfile><CR> | |
| 328 < If the name is a hypertext link, that looks like | |
| 329 "type://machine/path", you need the |netrw| plugin. | |
| 330 For Unix the '~' character is expanded, like in | |
| 331 "~user/file". Environment variables are expanded too | |
| 332 |expand-env|. | |
| 333 {not in Vi} | |
| 334 {not available when the |+file_in_path| feature was | |
| 335 disabled at compile time} | |
| 336 | |
| 337 *v_gf* | |
| 338 {Visual}[count]gf Same as "gf", but the highlighted text is used as the | |
| 339 name of the file to edit. 'isfname' is ignored. | |
| 340 Leading blanks are skipped, otherwise all blanks and | |
| 341 special characters are included in the file name. | |
| 342 (For {Visual} see |Visual-mode|.) | |
| 343 {not in VI} | |
| 344 | |
| 681 | 345 *gF* |
| 346 [count]gF Same as "gf", except if a number follows the file | |
| 347 name, then the cursor is positioned on that line in | |
| 348 the file. The file name and the number must be | |
| 349 separated by a non-filename (see 'isfname') and | |
| 350 non-numeric character. White space between the | |
| 351 filename, the separator and the number are ignored. | |
| 852 | 352 Examples: |
| 353 eval.c:10 ~ | |
| 354 eval.c @ 20 ~ | |
| 355 eval.c (30) ~ | |
| 356 eval.c 40 ~ | |
| 357 | |
| 681 | 358 *v_gF* |
| 359 {Visual}[count]gF Same as "v_gf". | |
| 360 | |
| 7 | 361 These commands are used to start editing a single file. This means that the |
| 362 file is read into the buffer and the current file name is set. The file that | |
| 363 is opened depends on the current directory, see |:cd|. | |
| 364 | |
| 365 See |read-messages| for an explanation of the message that is given after the | |
| 366 file has been read. | |
| 367 | |
| 368 You can use the ":e!" command if you messed up the buffer and want to start | |
| 369 all over again. The ":e" command is only useful if you have changed the | |
| 370 current file name. | |
| 371 | |
| 372 *:filename* *{file}* | |
| 1620 | 373 Besides the things mentioned here, more special items for where a filename is |
| 374 expected are mentioned at |cmdline-special|. | |
| 375 | |
| 1668 | 376 Note for systems other than Unix: When using a command that accepts a single |
| 377 file name (like ":edit file") spaces in the file name are allowed, but | |
| 378 trailing spaces are ignored. This is useful on systems that regularly embed | |
| 379 spaces in file names (like MS-Windows and the Amiga). Example: The command | |
| 380 ":e Long File Name " will edit the file "Long File Name". When using a | |
| 381 command that accepts more than one file name (like ":next file1 file2") | |
| 382 embedded spaces must be escaped with a backslash. | |
| 7 | 383 |
| 1121 | 384 *wildcard* *wildcards* |
| 3682 | 385 Wildcards in {file} are expanded, but as with file completion, 'wildignore' |
| 386 and 'suffixes' apply. Which wildcards are supported depends on the system. | |
| 387 These are the common ones: | |
| 444 | 388 ? matches one character |
| 7 | 389 * matches anything, including nothing |
| 444 | 390 ** matches anything, including nothing, recurses into directories |
| 7 | 391 [abc] match 'a', 'b' or 'c' |
| 444 | 392 |
| 7 | 393 To avoid the special meaning of the wildcards prepend a backslash. However, |
| 394 on MS-Windows the backslash is a path separator and "path\[abc]" is still seen | |
| 395 as a wildcard when "[" is in the 'isfname' option. A simple way to avoid this | |
| 396 is to use "path\[[]abc]". Then the file "path[abc]" literally. | |
| 397 | |
| 444 | 398 *starstar-wildcard* |
| 399 Expanding "**" is possible on Unix, Win32, Mac OS/X and a few other systems. | |
| 400 This allows searching a directory tree. This goes up to 100 directories deep. | |
| 3750 | 401 Note there are some commands where this works slightly differently, see |
| 1668 | 402 |file-searching|. |
| 444 | 403 Example: > |
| 404 :n **/*.txt | |
| 405 Finds files: | |
| 406 ttt.txt | |
| 407 subdir/ttt.txt | |
| 408 a/b/c/d/ttt.txt | |
| 409 When non-wildcard characters are used these are only matched in the first | |
| 410 directory. Example: > | |
| 411 :n /usr/inc**/*.h | |
| 412 Finds files: | |
| 413 /usr/include/types.h | |
| 414 /usr/include/sys/types.h | |
| 415 /usr/inc_old/types.h | |
| 7 | 416 *backtick-expansion* *`-expansion* |
| 7013 | 417 On Unix and a few other systems you can also use backticks for the file name |
| 418 argument, for example: > | |
| 419 :next `find . -name ver\\*.c -print` | |
|
7051
eff26a8620ce
commit https://github.com/vim/vim/commit/88774fdd23f08355297bb8cda78856859051d3c7
Christian Brabandt <cb@256bit.org>
parents:
7013
diff
changeset
|
420 :view `ls -t *.patch \| head -n1` |
| 7013 | 421 The backslashes before the star are required to prevent the shell from |
| 422 expanding "ver*.c" prior to execution of the find program. The backslash | |
| 423 before the shell pipe symbol "|" prevents Vim from parsing it as command | |
| 424 termination. | |
| 7 | 425 This also works for most other systems, with the restriction that the |
| 426 backticks must be around the whole item. It is not possible to have text | |
| 427 directly before the first or just after the last backtick. | |
| 428 | |
| 8 | 429 *`=* |
| 7013 | 430 You can have the backticks expanded as a Vim expression, instead of as an |
| 431 external command, by putting an equal sign right after the first backtick, | |
| 432 e.g.: > | |
| 39 | 433 :e `=tempname()` |
| 434 The expression can contain just about anything, thus this can also be used to | |
| 3682 | 435 avoid the special meaning of '"', '|', '%' and '#'. However, 'wildignore' |
| 4119 | 436 does apply like to other wildcards. |
| 7013 | 437 |
|
7051
eff26a8620ce
commit https://github.com/vim/vim/commit/88774fdd23f08355297bb8cda78856859051d3c7
Christian Brabandt <cb@256bit.org>
parents:
7013
diff
changeset
|
438 Environment variables in the expression are expanded when evaluating the |
|
eff26a8620ce
commit https://github.com/vim/vim/commit/88774fdd23f08355297bb8cda78856859051d3c7
Christian Brabandt <cb@256bit.org>
parents:
7013
diff
changeset
|
439 expression, thus this works: > |
|
eff26a8620ce
commit https://github.com/vim/vim/commit/88774fdd23f08355297bb8cda78856859051d3c7
Christian Brabandt <cb@256bit.org>
parents:
7013
diff
changeset
|
440 :e `=$HOME . '/.vimrc'` |
|
eff26a8620ce
commit https://github.com/vim/vim/commit/88774fdd23f08355297bb8cda78856859051d3c7
Christian Brabandt <cb@256bit.org>
parents:
7013
diff
changeset
|
441 This does not work, $HOME is inside a string and used literally: > |
|
eff26a8620ce
commit https://github.com/vim/vim/commit/88774fdd23f08355297bb8cda78856859051d3c7
Christian Brabandt <cb@256bit.org>
parents:
7013
diff
changeset
|
442 :e `='$HOME' . '/.vimrc'` |
| 7013 | 443 |
| 3682 | 444 If the expression returns a string then names are to be separated with line |
| 445 breaks. When the result is a |List| then each item is used as a name. Line | |
| 446 breaks also separate names. | |
|
6951
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6647
diff
changeset
|
447 Note that such expressions are only supported in places where a filename is |
|
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6647
diff
changeset
|
448 expected as an argument to an Ex-command. |
| 7 | 449 |
| 450 *++opt* *[++opt]* | |
| 595 | 451 The [++opt] argument can be used to force the value of 'fileformat', |
| 452 'fileencoding' or 'binary' to a value for one command, and to specify the | |
| 453 behavior for bad characters. The form is: > | |
| 819 | 454 ++{optname} |
| 455 Or: > | |
| 7 | 456 ++{optname}={value} |
| 457 | |
| 819 | 458 Where {optname} is one of: *++ff* *++enc* *++bin* *++nobin* *++edit* |
| 7 | 459 ff or fileformat overrides 'fileformat' |
| 460 enc or encoding overrides 'fileencoding' | |
| 461 bin or binary sets 'binary' | |
| 462 nobin or nobinary resets 'binary' | |
| 856 | 463 bad specifies behavior for bad characters |
| 819 | 464 edit for |:read| only: keep option values as if editing |
| 856 | 465 a file |
| 7 | 466 |
| 467 {value} cannot contain white space. It can be any valid value for these | |
| 468 options. Examples: > | |
| 469 :e ++ff=unix | |
| 470 This edits the same file again with 'fileformat' set to "unix". > | |
| 471 | |
| 472 :w ++enc=latin1 newfile | |
| 473 This writes the current buffer to "newfile" in latin1 format. | |
| 474 | |
| 595 | 475 There may be several ++opt arguments, separated by white space. They must all |
| 476 appear before any |+cmd| argument. | |
| 477 | |
| 478 *++bad* | |
| 479 The argument of "++bad=" specifies what happens with characters that can't be | |
| 480 converted and illegal bytes. It can be one of three things: | |
| 481 ++bad=X A single-byte character that replaces each bad character. | |
| 482 ++bad=keep Keep bad characters without conversion. Note that this may | |
| 856 | 483 result in illegal bytes in your text! |
| 595 | 484 ++bad=drop Remove the bad characters. |
| 485 | |
| 486 The default is like "++bad=?": Replace each bad character with a question | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
487 mark. In some places an inverted question mark is used (0xBF). |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
488 |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
489 Note that not all commands use the ++bad argument, even though they do not |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
490 give an error when you add it. E.g. |:write|. |
| 595 | 491 |
| 7 | 492 Note that when reading, the 'fileformat' and 'fileencoding' options will be |
| 493 set to the used format. When writing this doesn't happen, thus a next write | |
| 494 will use the old value of the option. Same for the 'binary' option. | |
| 495 | |
| 496 | |
| 497 *+cmd* *[+cmd]* | |
| 498 The [+cmd] argument can be used to position the cursor in the newly opened | |
| 499 file, or execute any other command: | |
| 500 + Start at the last line. | |
| 501 +{num} Start at line {num}. | |
| 502 +/{pat} Start at first line containing {pat}. | |
| 503 +{command} Execute {command} after opening the new file. | |
| 504 {command} is any Ex command. | |
| 505 To include a white space in the {pat} or {command}, precede it with a | |
| 506 backslash. Double the number of backslashes. > | |
| 507 :edit +/The\ book file | |
| 508 :edit +/dir\ dirname\\ file | |
| 509 :edit +set\ dir=c:\\\\temp file | |
| 510 Note that in the last example the number of backslashes is halved twice: Once | |
| 511 for the "+cmd" argument and once for the ":set" command. | |
| 512 | |
| 513 *file-formats* | |
| 514 The 'fileformat' option sets the <EOL> style for a file: | |
| 515 'fileformat' characters name ~ | |
| 516 "dos" <CR><NL> or <NL> DOS format *DOS-format* | |
| 517 "unix" <NL> Unix format *Unix-format* | |
| 518 "mac" <CR> Mac format *Mac-format* | |
| 519 Previously 'textmode' was used. It is obsolete now. | |
| 520 | |
| 521 When reading a file, the mentioned characters are interpreted as the <EOL>. | |
| 522 In DOS format (default for MS-DOS, OS/2 and Win32), <CR><NL> and <NL> are both | |
| 523 interpreted as the <EOL>. Note that when writing the file in DOS format, | |
| 524 <CR> characters will be added for each single <NL>. Also see |file-read|. | |
| 525 | |
| 526 When writing a file, the mentioned characters are used for <EOL>. For DOS | |
| 527 format <CR><NL> is used. Also see |DOS-format-write|. | |
| 528 | |
| 529 You can read a file in DOS format and write it in Unix format. This will | |
| 530 replace all <CR><NL> pairs by <NL> (assuming 'fileformats' includes "dos"): > | |
| 531 :e file | |
| 532 :set fileformat=unix | |
| 533 :w | |
| 534 If you read a file in Unix format and write with DOS format, all <NL> | |
| 535 characters will be replaced with <CR><NL> (assuming 'fileformats' includes | |
| 536 "unix"): > | |
| 537 :e file | |
| 538 :set fileformat=dos | |
| 539 :w | |
| 540 | |
| 541 If you start editing a new file and the 'fileformats' option is not empty | |
| 542 (which is the default), Vim will try to detect whether the lines in the file | |
| 543 are separated by the specified formats. When set to "unix,dos", Vim will | |
| 544 check for lines with a single <NL> (as used on Unix and Amiga) or by a <CR> | |
| 545 <NL> pair (MS-DOS). Only when ALL lines end in <CR><NL>, 'fileformat' is set | |
| 546 to "dos", otherwise it is set to "unix". When 'fileformats' includes "mac", | |
| 547 and no <NL> characters are found in the file, 'fileformat' is set to "mac". | |
| 548 | |
| 549 If the 'fileformat' option is set to "dos" on non-MS-DOS systems the message | |
| 550 "[dos format]" is shown to remind you that something unusual is happening. On | |
| 551 MS-DOS systems you get the message "[unix format]" if 'fileformat' is set to | |
| 552 "unix". On all systems but the Macintosh you get the message "[mac format]" | |
| 553 if 'fileformat' is set to "mac". | |
| 554 | |
| 555 If the 'fileformats' option is empty and DOS format is used, but while reading | |
| 556 a file some lines did not end in <CR><NL>, "[CR missing]" will be included in | |
| 557 the file message. | |
| 558 If the 'fileformats' option is empty and Mac format is used, but while reading | |
| 559 a file a <NL> was found, "[NL missing]" will be included in the file message. | |
| 560 | |
| 561 If the new file does not exist, the 'fileformat' of the current buffer is used | |
| 562 when 'fileformats' is empty. Otherwise the first format from 'fileformats' is | |
| 563 used for the new file. | |
| 564 | |
| 565 Before editing binary, executable or Vim script files you should set the | |
| 566 'binary' option. A simple way to do this is by starting Vim with the "-b" | |
| 567 option. This will avoid the use of 'fileformat'. Without this you risk that | |
| 568 single <NL> characters are unexpectedly replaced with <CR><NL>. | |
| 569 | |
| 570 You can encrypt files that are written by setting the 'key' option. This | |
| 571 provides some security against others reading your files. |encryption| | |
| 572 | |
| 573 | |
| 574 ============================================================================== | |
| 39 | 575 3. The argument list *argument-list* *arglist* |
| 7 | 576 |
| 577 If you give more than one file name when starting Vim, this list is remembered | |
| 578 as the argument list. You can jump to each file in this list. | |
| 579 | |
| 580 Do not confuse this with the buffer list, which you can see with the | |
| 581 |:buffers| command. The argument list was already present in Vi, the buffer | |
| 39 | 582 list is new in Vim. Every file name in the argument list will also be present |
| 583 in the buffer list (unless it was deleted with |:bdel| or |:bwipe|). But it's | |
| 584 common that names in the buffer list are not in the argument list. | |
| 7 | 585 |
| 586 This subject is introduced in section |07.2| of the user manual. | |
| 587 | |
| 588 There is one global argument list, which is used for all windows by default. | |
| 589 It is possible to create a new argument list local to a window, see | |
| 590 |:arglocal|. | |
| 591 | |
| 592 You can use the argument list with the following commands, and with the | |
| 593 expression functions |argc()| and |argv()|. These all work on the argument | |
| 594 list of the current window. | |
| 595 | |
| 596 *:ar* *:args* | |
| 597 :ar[gs] Print the argument list, with the current file in | |
| 598 square brackets. | |
| 599 | |
| 600 :ar[gs] [++opt] [+cmd] {arglist} *:args_f* | |
| 601 Define {arglist} as the new argument list and edit | |
| 602 the first one. This fails when changes have been made | |
| 603 and Vim does not want to |abandon| the current buffer. | |
| 604 Also see |++opt| and |+cmd|. | |
| 605 {Vi: no ++opt} | |
| 606 | |
| 607 :ar[gs]! [++opt] [+cmd] {arglist} *:args_f!* | |
| 608 Define {arglist} as the new argument list and edit | |
| 609 the first one. Discard any changes to the current | |
| 610 buffer. | |
| 611 Also see |++opt| and |+cmd|. | |
| 612 {Vi: no ++opt} | |
| 613 | |
| 614 :[count]arge[dit][!] [++opt] [+cmd] {name} *:arge* *:argedit* | |
| 615 Add {name} to the argument list and edit it. | |
| 616 When {name} already exists in the argument list, this | |
| 617 entry is edited. | |
| 618 This is like using |:argadd| and then |:edit|. | |
| 619 Note that only one file name is allowed, and spaces | |
| 620 inside the file name are allowed, like with |:edit|. | |
| 621 [count] is used like with |:argadd|. | |
| 622 [!] is required if the current file cannot be | |
| 623 |abandon|ed. | |
| 624 Also see |++opt| and |+cmd|. | |
| 625 {not in Vi} | |
| 626 | |
| 627 :[count]arga[dd] {name} .. *:arga* *:argadd* *E479* | |
| 6238 | 628 :[count]arga[dd] |
| 629 Add the {name}s to the argument list. When {name} is | |
| 6421 | 630 omitted add the current buffer name to the argument |
| 6238 | 631 list. |
| 7 | 632 If [count] is omitted, the {name}s are added just |
| 633 after the current entry in the argument list. | |
| 634 Otherwise they are added after the [count]'th file. | |
| 635 If the argument list is "a b c", and "b" is the | |
| 636 current argument, then these commands result in: | |
| 637 command new argument list ~ | |
| 638 :argadd x a b x c | |
| 639 :0argadd x x a b c | |
| 640 :1argadd x a x b c | |
| 6421 | 641 :$argadd x a b c x |
|
7659
07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Christian Brabandt <cb@256bit.org>
parents:
7480
diff
changeset
|
642 And after the last one: |
| 6421 | 643 :+2argadd y a b c x y |
| 7 | 644 There is no check for duplicates, it is possible to |
| 645 add a file to the argument list twice. | |
| 646 The currently edited file is not changed. | |
| 647 {not in Vi} {not available when compiled without the | |
| 648 |+listcmds| feature} | |
| 649 Note: you can also use this method: > | |
| 650 :args ## x | |
| 651 < This will add the "x" item and sort the new list. | |
| 652 | |
| 653 :argd[elete] {pattern} .. *:argd* *:argdelete* *E480* | |
| 654 Delete files from the argument list that match the | |
| 655 {pattern}s. {pattern} is used like a file pattern, | |
| 656 see |file-pattern|. "%" can be used to delete the | |
| 657 current entry. | |
| 658 This command keeps the currently edited file, also | |
| 659 when it's deleted from the argument list. | |
| 280 | 660 Example: > |
| 661 :argdel *.obj | |
| 662 < {not in Vi} {not available when compiled without the | |
| 7 | 663 |+listcmds| feature} |
| 664 | |
| 6421 | 665 :[range]argd[elete] Delete the {range} files from the argument list. |
| 666 Example: > | |
| 667 :10,$argdel | |
| 668 < Deletes arguments 10 and further, keeping 1-9. > | |
| 669 :$argd | |
| 670 < Deletes just the last one. > | |
| 671 :argd | |
| 672 :.argd | |
| 673 < Deletes the current argument. > | |
| 674 :%argd | |
| 675 < Removes all the files from the arglist. | |
| 7 | 676 When the last number in the range is too high, up to |
| 6421 | 677 the last argument is deleted. |
| 7 | 678 {not in Vi} {not available when compiled without the |
| 679 |+listcmds| feature} | |
| 680 | |
| 681 *:argu* *:argument* | |
| 682 :[count]argu[ment] [count] [++opt] [+cmd] | |
| 683 Edit file [count] in the argument list. When [count] | |
| 684 is omitted the current entry is used. This fails | |
| 685 when changes have been made and Vim does not want to | |
| 686 |abandon| the current buffer. | |
| 687 Also see |++opt| and |+cmd|. | |
| 688 {not in Vi} {not available when compiled without the | |
| 689 |+listcmds| feature} | |
| 690 | |
| 691 :[count]argu[ment]! [count] [++opt] [+cmd] | |
| 692 Edit file [count] in the argument list, discard any | |
| 693 changes to the current buffer. When [count] is | |
| 694 omitted the current entry is used. | |
| 695 Also see |++opt| and |+cmd|. | |
| 696 {not in Vi} {not available when compiled without the | |
| 697 |+listcmds| feature} | |
| 698 | |
| 699 :[count]n[ext] [++opt] [+cmd] *:n* *:ne* *:next* *E165* *E163* | |
| 700 Edit [count] next file. This fails when changes have | |
| 701 been made and Vim does not want to |abandon| the | |
| 702 current buffer. Also see |++opt| and |+cmd|. {Vi: no | |
| 703 count or ++opt}. | |
| 704 | |
| 705 :[count]n[ext]! [++opt] [+cmd] | |
| 706 Edit [count] next file, discard any changes to the | |
| 707 buffer. Also see |++opt| and |+cmd|. {Vi: no count | |
| 708 or ++opt}. | |
| 709 | |
| 710 :n[ext] [++opt] [+cmd] {arglist} *:next_f* | |
| 711 Same as |:args_f|. | |
| 712 | |
| 713 :n[ext]! [++opt] [+cmd] {arglist} | |
| 714 Same as |:args_f!|. | |
| 715 | |
| 716 :[count]N[ext] [count] [++opt] [+cmd] *:Next* *:N* *E164* | |
| 717 Edit [count] previous file in argument list. This | |
| 718 fails when changes have been made and Vim does not | |
| 719 want to |abandon| the current buffer. | |
| 720 Also see |++opt| and |+cmd|. {Vi: no count or ++opt}. | |
| 721 | |
| 722 :[count]N[ext]! [count] [++opt] [+cmd] | |
| 723 Edit [count] previous file in argument list. Discard | |
| 724 any changes to the buffer. Also see |++opt| and | |
| 725 |+cmd|. {Vi: no count or ++opt}. | |
| 726 | |
| 727 :[count]prev[ious] [count] [++opt] [+cmd] *:prev* *:previous* | |
| 728 Same as :Next. Also see |++opt| and |+cmd|. {Vi: | |
| 729 only in some versions} | |
| 730 | |
| 731 *:rew* *:rewind* | |
| 732 :rew[ind] [++opt] [+cmd] | |
| 733 Start editing the first file in the argument list. | |
| 734 This fails when changes have been made and Vim does | |
| 735 not want to |abandon| the current buffer. | |
| 736 Also see |++opt| and |+cmd|. {Vi: no ++opt} | |
| 737 | |
| 738 :rew[ind]! [++opt] [+cmd] | |
| 739 Start editing the first file in the argument list. | |
| 740 Discard any changes to the buffer. Also see |++opt| | |
| 741 and |+cmd|. {Vi: no ++opt} | |
| 742 | |
| 743 *:fir* *:first* | |
| 744 :fir[st][!] [++opt] [+cmd] | |
| 745 Other name for ":rewind". {not in Vi} | |
| 746 | |
| 747 *:la* *:last* | |
| 748 :la[st] [++opt] [+cmd] | |
| 749 Start editing the last file in the argument list. | |
| 750 This fails when changes have been made and Vim does | |
| 751 not want to |abandon| the current buffer. | |
| 752 Also see |++opt| and |+cmd|. {not in Vi} | |
| 753 | |
| 754 :la[st]! [++opt] [+cmd] | |
| 755 Start editing the last file in the argument list. | |
| 756 Discard any changes to the buffer. Also see |++opt| | |
| 757 and |+cmd|. {not in Vi} | |
| 758 | |
| 759 *:wn* *:wnext* | |
| 1702 | 760 :[count]wn[ext] [++opt] |
| 7 | 761 Write current file and start editing the [count] |
| 762 next file. Also see |++opt| and |+cmd|. {not in Vi} | |
| 763 | |
| 1702 | 764 :[count]wn[ext] [++opt] {file} |
| 7 | 765 Write current file to {file} and start editing the |
| 766 [count] next file, unless {file} already exists and | |
| 767 the 'writeany' option is off. Also see |++opt| and | |
| 768 |+cmd|. {not in Vi} | |
| 769 | |
| 1702 | 770 :[count]wn[ext]! [++opt] {file} |
| 7 | 771 Write current file to {file} and start editing the |
| 772 [count] next file. Also see |++opt| and |+cmd|. {not | |
| 773 in Vi} | |
| 774 | |
| 1702 | 775 :[count]wN[ext][!] [++opt] [file] *:wN* *:wNext* |
| 776 :[count]wp[revious][!] [++opt] [file] *:wp* *:wprevious* | |
| 7 | 777 Same as :wnext, but go to previous file instead of |
| 778 next. {not in Vi} | |
| 779 | |
| 780 The [count] in the commands above defaults to one. For some commands it is | |
| 781 possible to use two counts. The last one (rightmost one) is used. | |
| 782 | |
| 783 If no [+cmd] argument is present, the cursor is positioned at the last known | |
| 784 cursor position for the file. If 'startofline' is set, the cursor will be | |
| 785 positioned at the first non-blank in the line, otherwise the last know column | |
| 786 is used. If there is no last known cursor position the cursor will be in the | |
| 787 first line (the last line in Ex mode). | |
| 788 | |
| 39 | 789 *{arglist}* |
| 7 | 790 The wildcards in the argument list are expanded and the file names are sorted. |
| 791 Thus you can use the command "vim *.c" to edit all the C files. From within | |
| 39 | 792 Vim the command ":n *.c" does the same. |
| 793 | |
| 794 White space is used to separate file names. Put a backslash before a space or | |
| 1240 | 795 tab to include it in a file name. E.g., to edit the single file "foo bar": > |
| 39 | 796 :next foo\ bar |
| 797 | |
| 798 On Unix and a few other systems you can also use backticks, for example: > | |
| 799 :next `find . -name \\*.c -print` | |
| 7 | 800 The backslashes before the star are required to prevent "*.c" to be expanded |
| 801 by the shell before executing the find program. | |
| 802 | |
| 803 *arglist-position* | |
| 804 When there is an argument list you can see which file you are editing in the | |
| 805 title of the window (if there is one and 'title' is on) and with the file | |
| 806 message you get with the "CTRL-G" command. You will see something like | |
| 807 (file 4 of 11) | |
| 808 If 'shortmess' contains 'f' it will be | |
| 809 (4 of 11) | |
| 810 If you are not really editing the file at the current position in the argument | |
| 811 list it will be | |
| 812 (file (4) of 11) | |
| 813 This means that you are position 4 in the argument list, but not editing the | |
| 814 fourth file in the argument list. This happens when you do ":e file". | |
| 815 | |
| 816 | |
| 817 LOCAL ARGUMENT LIST | |
| 818 | |
| 819 {not in Vi} | |
|
2570
71b56b4e7785
Make the references to features in the help more consistent. (Sylvain Hitier)
Bram Moolenaar <bram@vim.org>
parents:
2561
diff
changeset
|
820 {not available when compiled without the |+windows| or |+listcmds| features} |
| 7 | 821 |
| 822 *:arglocal* | |
| 823 :argl[ocal] Make a local copy of the global argument list. | |
| 824 Doesn't start editing another file. | |
| 825 | |
| 826 :argl[ocal][!] [++opt] [+cmd] {arglist} | |
| 827 Define a new argument list, which is local to the | |
| 828 current window. Works like |:args_f| otherwise. | |
| 829 | |
| 830 *:argglobal* | |
| 831 :argg[lobal] Use the global argument list for the current window. | |
| 832 Doesn't start editing another file. | |
| 833 | |
| 834 :argg[lobal][!] [++opt] [+cmd] {arglist} | |
| 835 Use the global argument list for the current window. | |
| 836 Define a new global argument list like |:args_f|. | |
| 837 All windows using the global argument list will see | |
| 838 this new list. | |
| 839 | |
| 840 There can be several argument lists. They can be shared between windows. | |
| 841 When they are shared, changing the argument list in one window will also | |
| 842 change it in the other window. | |
| 843 | |
| 844 When a window is split the new window inherits the argument list from the | |
| 845 current window. The two windows then share this list, until one of them uses | |
| 846 |:arglocal| or |:argglobal| to use another argument list. | |
| 847 | |
| 848 | |
| 849 USING THE ARGUMENT LIST | |
| 850 | |
| 851 *:argdo* | |
| 6474 | 852 :[range]argdo[!] {cmd} Execute {cmd} for each file in the argument list or |
| 853 if [range] is specified only for arguments in that | |
| 854 range. It works like doing this: > | |
| 7 | 855 :rewind |
| 856 :{cmd} | |
| 857 :next | |
| 858 :{cmd} | |
| 859 etc. | |
| 860 < When the current file can't be |abandon|ed and the [!] | |
| 861 is not present, the command fails. | |
| 862 When an error is detected on one file, further files | |
| 863 in the argument list will not be visited. | |
| 864 The last file in the argument list (or where an error | |
| 865 occurred) becomes the current file. | |
| 866 {cmd} can contain '|' to concatenate several commands. | |
| 867 {cmd} must not change the argument list. | |
| 868 Note: While this command is executing, the Syntax | |
| 869 autocommand event is disabled by adding it to | |
| 870 'eventignore'. This considerably speeds up editing | |
| 871 each file. | |
| 872 {not in Vi} {not available when compiled without the | |
| 873 |+listcmds| feature} | |
|
7092
64e30831fa42
commit https://github.com/vim/vim/commit/aa23b379421aa214e6543b06c974594a25799b09
Christian Brabandt <cb@256bit.org>
parents:
7051
diff
changeset
|
874 Also see |:windo|, |:tabdo|, |:bufdo|, |:cdo|, |:ldo|, |
|
64e30831fa42
commit https://github.com/vim/vim/commit/aa23b379421aa214e6543b06c974594a25799b09
Christian Brabandt <cb@256bit.org>
parents:
7051
diff
changeset
|
875 |:cfdo| and |:lfdo| |
| 7 | 876 |
| 877 Example: > | |
| 878 :args *.c | |
| 879 :argdo set ff=unix | update | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
880 This sets the 'fileformat' option to "unix" and writes the file if it is now |
| 7 | 881 changed. This is done for all *.c files. |
| 882 | |
| 883 Example: > | |
| 884 :args *.[ch] | |
| 885 :argdo %s/\<my_foo\>/My_Foo/ge | update | |
| 886 This changes the word "my_foo" to "My_Foo" in all *.c and *.h files. The "e" | |
| 887 flag is used for the ":substitute" command to avoid an error for files where | |
| 888 "my_foo" isn't used. ":update" writes the file only if changes were made. | |
| 889 | |
| 890 ============================================================================== | |
| 39 | 891 4. Writing *writing* *save-file* |
| 7 | 892 |
| 893 Note: When the 'write' option is off, you are not able to write any file. | |
| 894 | |
| 895 *:w* *:write* | |
| 896 *E502* *E503* *E504* *E505* | |
| 1121 | 897 *E512* *E514* *E667* *E796* |
| 1702 | 898 :w[rite] [++opt] Write the whole buffer to the current file. This is |
| 7 | 899 the normal way to save changes to a file. It fails |
| 900 when the 'readonly' option is set or when there is | |
| 901 another reason why the file can't be written. | |
| 1702 | 902 For ++opt see |++opt|, but only ++bin, ++nobin, ++ff |
| 903 and ++enc are effective. | |
| 7 | 904 |
| 1702 | 905 :w[rite]! [++opt] Like ":write", but forcefully write when 'readonly' is |
| 7 | 906 set or there is another reason why writing was |
| 907 refused. | |
| 908 Note: This may change the permission and ownership of | |
| 909 the file and break (symbolic) links. Add the 'W' flag | |
| 910 to 'cpoptions' to avoid this. | |
| 911 | |
| 1702 | 912 :[range]w[rite][!] [++opt] |
| 913 Write the specified lines to the current file. This | |
| 7 | 914 is unusual, because the file will not contain all |
| 915 lines in the buffer. | |
| 916 | |
| 917 *:w_f* *:write_f* | |
| 1702 | 918 :[range]w[rite] [++opt] {file} |
| 919 Write the specified lines to {file}, unless it | |
| 7 | 920 already exists and the 'writeany' option is off. |
| 921 | |
| 922 *:w!* | |
| 1702 | 923 :[range]w[rite]! [++opt] {file} |
| 924 Write the specified lines to {file}. Overwrite an | |
| 7 | 925 existing file. |
| 926 | |
| 927 *:w_a* *:write_a* *E494* | |
| 1702 | 928 :[range]w[rite][!] [++opt] >> |
| 929 Append the specified lines to the current file. | |
| 7 | 930 |
| 1702 | 931 :[range]w[rite][!] [++opt] >> {file} |
| 7 | 932 Append the specified lines to {file}. '!' forces the |
| 933 write even if file does not exist. | |
| 934 | |
| 935 *:w_c* *:write_c* | |
| 1702 | 936 :[range]w[rite] [++opt] !{cmd} |
| 937 Execute {cmd} with [range] lines as standard input | |
| 7 | 938 (note the space in front of the '!'). {cmd} is |
| 939 executed like with ":!{cmd}", any '!' is replaced with | |
| 940 the previous command |:!|. | |
| 941 | |
| 31 | 942 The default [range] for the ":w" command is the whole buffer (1,$). If you |
| 1620 | 943 write the whole buffer, it is no longer considered changed. When you |
| 944 write it to a different file with ":w somefile" it depends on the "+" flag in | |
| 945 'cpoptions'. When included, the write command will reset the 'modified' flag, | |
| 946 even though the buffer itself may still be different from its file. | |
| 31 | 947 |
| 7 | 948 If a file name is given with ":w" it becomes the alternate file. This can be |
| 949 used, for example, when the write fails and you want to try again later with | |
| 950 ":w #". This can be switched off by removing the 'A' flag from the | |
| 951 'cpoptions' option. | |
| 952 | |
| 953 *:sav* *:saveas* | |
| 1702 | 954 :sav[eas][!] [++opt] {file} |
| 955 Save the current buffer under the name {file} and set | |
| 7 | 956 the filename of the current buffer to {file}. The |
| 957 previous name is used for the alternate file name. | |
| 958 The [!] is needed to overwrite an existing file. | |
| 633 | 959 When 'filetype' is empty filetype detection is done |
| 960 with the new name, before the file is written. | |
| 819 | 961 When the write was successful 'readonly' is reset. |
| 7 | 962 {not in Vi} |
| 963 | |
| 964 *:up* *:update* | |
| 1702 | 965 :[range]up[date][!] [++opt] [>>] [file] |
| 7 | 966 Like ":write", but only write when the buffer has been |
| 967 modified. {not in Vi} | |
| 968 | |
| 969 | |
| 970 WRITING WITH MULTIPLE BUFFERS *buffer-write* | |
| 971 | |
| 972 *:wa* *:wall* | |
| 973 :wa[ll] Write all changed buffers. Buffers without a file | |
| 974 name or which are readonly are not written. {not in | |
| 975 Vi} | |
| 976 | |
| 977 :wa[ll]! Write all changed buffers, even the ones that are | |
| 978 readonly. Buffers without a file name are not | |
| 979 written. {not in Vi} | |
| 980 | |
| 981 | |
| 982 Vim will warn you if you try to overwrite a file that has been changed | |
| 983 elsewhere. See |timestamp|. | |
| 984 | |
| 985 *backup* *E207* *E506* *E507* *E508* *E509* *E510* | |
| 986 If you write to an existing file (but do not append) while the 'backup', | |
| 987 'writebackup' or 'patchmode' option is on, a backup of the original file is | |
| 988 made. The file is either copied or renamed (see 'backupcopy'). After the | |
| 989 file has been successfully written and when the 'writebackup' option is on and | |
| 990 the 'backup' option is off, the backup file is deleted. When the 'patchmode' | |
| 991 option is on the backup file may be renamed. | |
| 992 | |
| 993 *backup-table* | |
| 994 'backup' 'writebackup' action ~ | |
| 995 off off no backup made | |
| 996 off on backup current file, deleted afterwards (default) | |
| 997 on off delete old backup, backup current file | |
| 998 on on delete old backup, backup current file | |
| 999 | |
| 1000 When the 'backupskip' pattern matches with the name of the file which is | |
| 1001 written, no backup file is made. The values of 'backup' and 'writebackup' are | |
| 1002 ignored then. | |
| 1003 | |
| 1004 When the 'backup' option is on, an old backup file (with the same name as the | |
| 1005 new backup file) will be deleted. If 'backup' is not set, but 'writebackup' | |
| 1006 is set, an existing backup file will not be deleted. The backup file that is | |
| 1007 made while the file is being written will have a different name. | |
| 1008 | |
| 1009 On some filesystems it's possible that in a crash you lose both the backup and | |
| 1010 the newly written file (it might be there but contain bogus data). In that | |
| 1011 case try recovery, because the swap file is synced to disk and might still be | |
| 1012 there. |:recover| | |
| 1013 | |
| 1014 The directories given with the 'backupdir' option is used to put the backup | |
| 1015 file in. (default: same directory as the written file). | |
| 1016 | |
| 1017 Whether the backup is a new file, which is a copy of the original file, or the | |
| 1018 original file renamed depends on the 'backupcopy' option. See there for an | |
| 1019 explanation of when the copy is made and when the file is renamed. | |
| 1020 | |
| 1021 If the creation of a backup file fails, the write is not done. If you want | |
| 1022 to write anyway add a '!' to the command. | |
| 1023 | |
|
2698
b6471224d2af
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
2662
diff
changeset
|
1024 *write-permissions* |
|
b6471224d2af
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
2662
diff
changeset
|
1025 When writing a new file the permissions are read-write. For unix the mask is |
|
b6471224d2af
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
2662
diff
changeset
|
1026 0666 with additionally umask applied. When writing a file that was read Vim |
|
b6471224d2af
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
2662
diff
changeset
|
1027 will preserve the permissions, but clear the s-bit. |
|
b6471224d2af
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
2662
diff
changeset
|
1028 |
| 7 | 1029 *write-readonly* |
| 1030 When the 'cpoptions' option contains 'W', Vim will refuse to overwrite a | |
| 1031 readonly file. When 'W' is not present, ":w!" will overwrite a readonly file, | |
| 1032 if the system allows it (the directory must be writable). | |
| 1033 | |
| 1034 *write-fail* | |
| 1035 If the writing of the new file fails, you have to be careful not to lose | |
| 1036 your changes AND the original file. If there is no backup file and writing | |
| 236 | 1037 the new file failed, you have already lost the original file! DON'T EXIT VIM |
| 1038 UNTIL YOU WRITE OUT THE FILE! If a backup was made, it is put back in place | |
| 7 | 1039 of the original file (if possible). If you exit Vim, and lose the changes |
| 1040 you made, the original file will mostly still be there. If putting back the | |
| 1041 original file fails, there will be an error message telling you that you | |
| 1042 lost the original file. | |
| 1043 | |
| 1044 *DOS-format-write* | |
| 1045 If the 'fileformat' is "dos", <CR> <NL> is used for <EOL>. This is default | |
| 1046 for MS-DOS, Win32 and OS/2. On other systems the message "[dos format]" is | |
| 1047 shown to remind you that an unusual <EOL> was used. | |
| 1048 *Unix-format-write* | |
| 1049 If the 'fileformat' is "unix", <NL> is used for <EOL>. On MS-DOS, Win32 and | |
| 1050 OS/2 the message "[unix format]" is shown. | |
| 1051 *Mac-format-write* | |
| 1052 If the 'fileformat' is "mac", <CR> is used for <EOL>. On non-Mac systems the | |
| 1053 message "[mac format]" is shown. | |
| 1054 | |
| 1055 See also |file-formats| and the 'fileformat' and 'fileformats' options. | |
| 1056 | |
| 1057 *ACL* | |
| 1058 ACL stands for Access Control List. It is an advanced way to control access | |
| 1059 rights for a file. It is used on new MS-Windows and Unix systems, but only | |
| 1060 when the filesystem supports it. | |
| 1061 Vim attempts to preserve the ACL info when writing a file. The backup file | |
| 1062 will get the ACL info of the original file. | |
| 1063 The ACL info is also used to check if a file is read-only (when opening the | |
| 1064 file). | |
| 1065 | |
| 1066 *read-only-share* | |
| 1067 When MS-Windows shares a drive on the network it can be marked as read-only. | |
| 1068 This means that even if the file read-only attribute is absent, and the ACL | |
| 1069 settings on NT network shared drives allow writing to the file, you can still | |
| 1070 not write to the file. Vim on Win32 platforms will detect read-only network | |
| 1071 drives and will mark the file as read-only. You will not be able to override | |
| 1072 it with |:write|. | |
| 1073 | |
| 1074 *write-device* | |
| 1075 When the file name is actually a device name, Vim will not make a backup (that | |
| 1076 would be impossible). You need to use "!", since the device already exists. | |
| 1077 Example for Unix: > | |
| 1078 :w! /dev/lpt0 | |
| 1079 and for MS-DOS or MS-Windows: > | |
| 1080 :w! lpt0 | |
| 1081 For Unix a device is detected when the name doesn't refer to a normal file or | |
| 1082 a directory. A fifo or named pipe also looks like a device to Vim. | |
| 1083 For MS-DOS and MS-Windows the device is detected by its name: | |
| 1084 AUX | |
| 1085 CON | |
| 1086 CLOCK$ | |
| 1087 NUL | |
| 1088 PRN | |
| 1089 COMn n=1,2,3... etc | |
| 1090 LPTn n=1,2,3... etc | |
| 1091 The names can be in upper- or lowercase. | |
| 1092 | |
| 1093 ============================================================================== | |
| 39 | 1094 5. Writing and quitting *write-quit* |
| 7 | 1095 |
| 1096 *:q* *:quit* | |
| 1097 :q[uit] Quit the current window. Quit Vim if this is the last | |
| 1098 window. This fails when changes have been made and | |
| 1099 Vim refuses to |abandon| the current buffer, and when | |
| 1100 the last file in the argument list has not been | |
| 1101 edited. | |
| 674 | 1102 If there are other tab pages and quitting the last |
| 1103 window in the current tab page the current tab page is | |
| 1104 closed |tab-page|. | |
| 3682 | 1105 Triggers the |QuitPre| autocommand event. |
| 7 | 1106 |
| 1107 :conf[irm] q[uit] Quit, but give prompt when changes have been made, or | |
| 1108 the last file in the argument list has not been | |
| 1109 edited. See |:confirm| and 'confirm'. {not in Vi} | |
| 1110 | |
|
7477
05cf4cc72a9f
commit https://github.com/vim/vim/commit/fa7353428f705f7a13465a1943dddeede4083023
Christian Brabandt <cb@256bit.org>
parents:
7469
diff
changeset
|
1111 :q[uit]! Quit without writing, also when the current buffer has |
|
7469
15eefe1b0dad
commit https://github.com/vim/vim/commit/027387f70c671f62e3e08e0bdd09ec05b0232735
Christian Brabandt <cb@256bit.org>
parents:
7092
diff
changeset
|
1112 changes. If this is the last window and there is a |
|
15eefe1b0dad
commit https://github.com/vim/vim/commit/027387f70c671f62e3e08e0bdd09ec05b0232735
Christian Brabandt <cb@256bit.org>
parents:
7092
diff
changeset
|
1113 modified hidden buffer, the current buffer is |
|
15eefe1b0dad
commit https://github.com/vim/vim/commit/027387f70c671f62e3e08e0bdd09ec05b0232735
Christian Brabandt <cb@256bit.org>
parents:
7092
diff
changeset
|
1114 abandoned and the first changed hidden buffer becomes |
| 6385 | 1115 the current buffer. |
| 1116 Use ":qall!" to exit always. | |
| 7 | 1117 |
| 1118 :cq[uit] Quit always, without writing, and return an error | |
| 1119 code. See |:cq|. Used for Manx's QuickFix mode (see | |
| 1120 |quickfix|). {not in Vi} | |
| 1121 | |
| 1122 *:wq* | |
| 1702 | 1123 :wq [++opt] Write the current file and quit. Writing fails when |
| 7 | 1124 the file is read-only or the buffer does not have a |
| 1125 name. Quitting fails when the last file in the | |
| 1126 argument list has not been edited. | |
| 1127 | |
| 1702 | 1128 :wq! [++opt] Write the current file and quit. Writing fails when |
| 7 | 1129 the current buffer does not have a name. |
| 1130 | |
| 1702 | 1131 :wq [++opt] {file} Write to {file} and quit. Quitting fails when the |
| 7 | 1132 last file in the argument list has not been edited. |
| 1133 | |
| 1702 | 1134 :wq! [++opt] {file} Write to {file} and quit. |
| 7 | 1135 |
| 1702 | 1136 :[range]wq[!] [++opt] [file] |
| 1137 Same as above, but only write the lines in [range]. | |
| 7 | 1138 |
| 1139 *:x* *:xit* | |
| 1702 | 1140 :[range]x[it][!] [++opt] [file] |
| 7 | 1141 Like ":wq", but write only when changes have been |
| 1142 made. | |
| 1143 When 'hidden' is set and there are more windows, the | |
| 1144 current buffer becomes hidden, after writing the file. | |
| 1145 | |
| 1146 *:exi* *:exit* | |
| 1702 | 1147 :[range]exi[t][!] [++opt] [file] |
| 7 | 1148 Same as :xit. |
| 1149 | |
| 1150 *ZZ* | |
| 1151 ZZ Write current file, if modified, and quit (same as | |
| 1152 ":x"). (Note: If there are several windows for the | |
| 1153 current file, the file is written if it was modified | |
| 1154 and the window is closed). | |
| 1155 | |
| 1156 *ZQ* | |
| 1157 ZQ Quit without checking for changes (same as ":q!"). | |
| 1158 {not in Vi} | |
| 1159 | |
| 1160 MULTIPLE WINDOWS AND BUFFERS *window-exit* | |
| 1161 | |
| 1162 *:qa* *:qall* | |
| 1163 :qa[ll] Exit Vim, unless there are some buffers which have been | |
| 1164 changed. (Use ":bmod" to go to the next modified buffer). | |
| 1165 When 'autowriteall' is set all changed buffers will be | |
| 1166 written, like |:wqall|. {not in Vi} | |
| 1167 | |
| 1168 :conf[irm] qa[ll] | |
| 1169 Exit Vim. Bring up a prompt when some buffers have been | |
| 1170 changed. See |:confirm|. {not in Vi} | |
| 1171 | |
| 1172 :qa[ll]! Exit Vim. Any changes to buffers are lost. {not in Vi} | |
| 1620 | 1173 Also see |:cquit|, it does the same but exits with a non-zero |
| 1174 value. | |
| 7 | 1175 |
| 1176 *:quita* *:quitall* | |
| 1177 :quita[ll][!] Same as ":qall". {not in Vi} | |
| 1178 | |
| 1702 | 1179 :wqa[ll] [++opt] *:wqa* *:wqall* *:xa* *:xall* |
| 7 | 1180 :xa[ll] Write all changed buffers and exit Vim. If there are buffers |
| 1181 without a file name, which are readonly or which cannot be | |
| 1182 written for another reason, Vim will not quit. {not in Vi} | |
| 1183 | |
| 1702 | 1184 :conf[irm] wqa[ll] [++opt] |
| 7 | 1185 :conf[irm] xa[ll] |
| 1186 Write all changed buffers and exit Vim. Bring up a prompt | |
| 1187 when some buffers are readonly or cannot be written for | |
| 1188 another reason. See |:confirm|. {not in Vi} | |
| 1189 | |
| 1702 | 1190 :wqa[ll]! [++opt] |
| 7 | 1191 :xa[ll]! Write all changed buffers, even the ones that are readonly, |
| 1192 and exit Vim. If there are buffers without a file name or | |
| 1193 which cannot be written for another reason, Vim will not quit. | |
| 1194 {not in Vi} | |
| 1195 | |
| 1196 ============================================================================== | |
| 39 | 1197 6. Dialogs *edit-dialogs* |
| 1198 | |
| 1199 *:confirm* *:conf* | |
| 1200 :conf[irm] {command} Execute {command}, and use a dialog when an | |
| 1201 operation has to be confirmed. Can be used on the | |
| 3445 | 1202 |:q|, |:qa| and |:w| commands (the latter to override |
| 1203 a read-only setting), and any other command that can | |
| 1204 fail in such a way, such as |:only|, |:buffer|, | |
| 1205 |:bdelete|, etc. | |
| 39 | 1206 |
| 1207 Examples: > | |
| 1208 :confirm w foo | |
| 1209 < Will ask for confirmation when "foo" already exists. > | |
| 1210 :confirm q | |
| 1211 < Will ask for confirmation when there are changes. > | |
| 1212 :confirm qa | |
| 1213 < If any modified, unsaved buffers exist, you will be prompted to save | |
| 1214 or abandon each one. There are also choices to "save all" or "abandon | |
| 1215 all". | |
| 1216 | |
| 1217 If you want to always use ":confirm", set the 'confirm' option. | |
| 1218 | |
| 1219 *:browse* *:bro* *E338* *E614* *E615* *E616* *E578* | |
| 1220 :bro[wse] {command} Open a file selection dialog for an argument to | |
| 1221 {command}. At present this works for |:e|, |:w|, | |
|
2296
eb7be7b075a6
Support :browse for commands that use an error file argument. (Lech Lorens)
Bram Moolenaar <bram@vim.org>
parents:
2283
diff
changeset
|
1222 |:wall|, |:wq|, |:wqall|, |:x|, |:xall|, |:exit|, |
|
eb7be7b075a6
Support :browse for commands that use an error file argument. (Lech Lorens)
Bram Moolenaar <bram@vim.org>
parents:
2283
diff
changeset
|
1223 |:view|, |:sview|, |:r|, |:saveas|, |:sp|, |:mkexrc|, |
|
eb7be7b075a6
Support :browse for commands that use an error file argument. (Lech Lorens)
Bram Moolenaar <bram@vim.org>
parents:
2283
diff
changeset
|
1224 |:mkvimrc|, |:mksession|, |:mkview|, |:split|, |
|
eb7be7b075a6
Support :browse for commands that use an error file argument. (Lech Lorens)
Bram Moolenaar <bram@vim.org>
parents:
2283
diff
changeset
|
1225 |:vsplit|, |:tabe|, |:tabnew|, |:cfile|, |:cgetfile|, |
|
eb7be7b075a6
Support :browse for commands that use an error file argument. (Lech Lorens)
Bram Moolenaar <bram@vim.org>
parents:
2283
diff
changeset
|
1226 |:caddfile|, |:lfile|, |:lgetfile|, |:laddfile|, |
|
eb7be7b075a6
Support :browse for commands that use an error file argument. (Lech Lorens)
Bram Moolenaar <bram@vim.org>
parents:
2283
diff
changeset
|
1227 |:diffsplit|, |:diffpatch|, |:open|, |:pedit|, |
|
eb7be7b075a6
Support :browse for commands that use an error file argument. (Lech Lorens)
Bram Moolenaar <bram@vim.org>
parents:
2283
diff
changeset
|
1228 |:redir|, |:source|, |:update|, |:visual|, |:vsplit|, |
|
eb7be7b075a6
Support :browse for commands that use an error file argument. (Lech Lorens)
Bram Moolenaar <bram@vim.org>
parents:
2283
diff
changeset
|
1229 and |:qall| if 'confirm' is set. |
| 39 | 1230 {only in Win32, Athena, Motif, GTK and Mac GUI} |
| 1231 When ":browse" is not possible you get an error | |
| 1232 message. If the |+browse| feature is missing or the | |
| 1233 {command} doesn't support browsing, the {command} is | |
| 1234 executed without a dialog. | |
| 1235 ":browse set" works like |:options|. | |
|
2296
eb7be7b075a6
Support :browse for commands that use an error file argument. (Lech Lorens)
Bram Moolenaar <bram@vim.org>
parents:
2283
diff
changeset
|
1236 See also |:oldfiles| for ":browse oldfiles". |
| 39 | 1237 |
| 1238 The syntax is best shown via some examples: > | |
| 1239 :browse e $vim/foo | |
| 1240 < Open the browser in the $vim/foo directory, and edit the | |
| 1241 file chosen. > | |
| 1242 :browse e | |
| 1243 < Open the browser in the directory specified with 'browsedir', | |
| 1244 and edit the file chosen. > | |
| 1245 :browse w | |
| 1246 < Open the browser in the directory of the current buffer, | |
| 1247 with the current buffer filename as default, and save the | |
| 1248 buffer under the filename chosen. > | |
| 1249 :browse w C:/bar | |
| 1250 < Open the browser in the C:/bar directory, with the current | |
| 1251 buffer filename as default, and save the buffer under the | |
| 1252 filename chosen. | |
| 1253 Also see the |'browsedir'| option. | |
| 1254 For versions of Vim where browsing is not supported, the command is executed | |
| 1255 unmodified. | |
| 1256 | |
| 1257 *browsefilter* | |
| 3682 | 1258 For MS Windows and GTK, you can modify the filters that are used in the browse |
| 1259 dialog. By setting the g:browsefilter or b:browsefilter variables, you can | |
| 1260 change the filters globally or locally to the buffer. The variable is set to | |
| 1261 a string in the format "{filter label}\t{pattern};{pattern}\n" where {filter | |
| 1262 label} is the text that appears in the "Files of Type" comboBox, and {pattern} | |
| 1263 is the pattern which filters the filenames. Several patterns can be given, | |
| 1264 separated by ';'. | |
| 39 | 1265 |
| 1266 For Motif the same format is used, but only the very first pattern is actually | |
| 1267 used (Motif only offers one pattern, but you can edit it). | |
| 1268 | |
| 1269 For example, to have only Vim files in the dialog, you could use the following | |
| 1270 command: > | |
| 1271 | |
| 3682 | 1272 let g:browsefilter = "Vim Scripts\t*.vim\nVim Startup Files\t*vimrc\n" |
| 39 | 1273 |
| 1274 You can override the filter setting on a per-buffer basis by setting the | |
| 1275 b:browsefilter variable. You would most likely set b:browsefilter in a | |
| 1276 filetype plugin, so that the browse dialog would contain entries related to | |
| 1277 the type of file you are currently editing. Disadvantage: This makes it | |
| 1278 difficult to start editing a file of a different type. To overcome this, you | |
| 1279 may want to add "All Files\t*.*\n" as the final filter, so that the user can | |
| 1280 still access any desired file. | |
| 1281 | |
| 3682 | 1282 To avoid setting browsefilter when Vim does not actually support it, you can |
| 1283 use has("browsefilter"): > | |
| 1284 | |
| 1285 if has("browsefilter") | |
| 1286 let g:browsefilter = "whatever" | |
| 1287 endif | |
| 1288 | |
| 39 | 1289 ============================================================================== |
| 1290 7. The current directory *current-directory* | |
| 1291 | |
| 1292 You may use the |:cd| and |:lcd| commands to change to another directory, so | |
| 1293 you will not have to type that directory name in front of the file names. It | |
| 1294 also makes a difference for executing external commands, e.g. ":!ls". | |
| 1295 | |
| 167 | 1296 Changing directory fails when the current buffer is modified, the '.' flag is |
| 1297 present in 'cpoptions' and "!" is not used in the command. | |
| 1298 | |
| 835 | 1299 *:cd* *E747* *E472* |
| 167 | 1300 :cd[!] On non-Unix systems: Print the current directory |
| 39 | 1301 name. On Unix systems: Change the current directory |
| 1302 to the home directory. Use |:pwd| to print the | |
| 1303 current directory on all systems. | |
| 1304 | |
| 167 | 1305 :cd[!] {path} Change the current directory to {path}. |
| 39 | 1306 If {path} is relative, it is searched for in the |
| 1307 directories listed in |'cdpath'|. | |
| 1308 Does not change the meaning of an already opened file, | |
| 1309 because its full path name is remembered. Files from | |
| 1310 the |arglist| may change though! | |
| 1311 On MS-DOS this also changes the active drive. | |
| 1312 To change to the directory of the current file: > | |
| 1313 :cd %:h | |
| 1314 < | |
| 1315 *:cd-* *E186* | |
| 167 | 1316 :cd[!] - Change to the previous current directory (before the |
| 39 | 1317 previous ":cd {path}" command). {not in Vi} |
| 1318 | |
| 1319 *:chd* *:chdir* | |
| 167 | 1320 :chd[ir][!] [path] Same as |:cd|. |
| 39 | 1321 |
| 1322 *:lc* *:lcd* | |
| 167 | 1323 :lc[d][!] {path} Like |:cd|, but only set the current directory for the |
| 39 | 1324 current window. The current directory for other |
| 1325 windows is not changed. {not in Vi} | |
| 1326 | |
| 1327 *:lch* *:lchdir* | |
| 167 | 1328 :lch[dir][!] Same as |:lcd|. {not in Vi} |
| 39 | 1329 |
| 1330 *:pw* *:pwd* *E187* | |
| 1331 :pw[d] Print the current directory name. {Vi: no pwd} | |
| 1332 Also see |getcwd()|. | |
| 1333 | |
| 1334 So long as no |:lcd| command has been used, all windows share the same current | |
| 1335 directory. Using a command to jump to another window doesn't change anything | |
| 1336 for the current directory. | |
| 1337 When a |:lcd| command has been used for a window, the specified directory | |
| 1338 becomes the current directory for that window. Windows where the |:lcd| | |
| 1339 command has not been used stick to the global current directory. When jumping | |
| 1340 to another window the current directory will become the last specified local | |
| 1341 current directory. If none was specified, the global current directory is | |
| 1342 used. | |
| 1343 When a |:cd| command is used, the current window will lose his local current | |
| 1344 directory and will use the global current directory from now on. | |
| 1345 | |
| 1346 After using |:cd| the full path name will be used for reading and writing | |
| 1347 files. On some networked file systems this may cause problems. The result of | |
| 1348 using the full path name is that the file names currently in use will remain | |
| 1349 referring to the same file. Example: If you have a file a:test and a | |
| 1350 directory a:vim the commands ":e test" ":cd vim" ":w" will overwrite the file | |
| 1351 a:test and not write a:vim/test. But if you do ":w test" the file a:vim/test | |
| 1352 will be written, because you gave a new file name and did not refer to a | |
| 1353 filename before the ":cd". | |
| 1354 | |
| 1355 ============================================================================== | |
| 7 | 1356 8. Editing binary files *edit-binary* |
| 1357 | |
| 1358 Although Vim was made to edit text files, it is possible to edit binary | |
| 1359 files. The |-b| Vim argument (b for binary) makes Vim do file I/O in binary | |
| 1360 mode, and sets some options for editing binary files ('binary' on, 'textwidth' | |
| 1361 to 0, 'modeline' off, 'expandtab' off). Setting the 'binary' option has the | |
| 1362 same effect. Don't forget to do this before reading the file. | |
| 1363 | |
| 1364 There are a few things to remember when editing binary files: | |
| 1365 - When editing executable files the number of characters must not change. | |
| 1366 Use only the "R" or "r" command to change text. Do not delete characters | |
| 1367 with "x" or by backspacing. | |
| 1368 - Set the 'textwidth' option to 0. Otherwise lines will unexpectedly be | |
| 1369 split in two. | |
| 1370 - When there are not many <EOL>s, the lines will become very long. If you | |
| 1371 want to edit a line that does not fit on the screen reset the 'wrap' option. | |
| 1372 Horizontal scrolling is used then. If a line becomes too long (more than | |
| 1373 about 32767 characters on the Amiga, much more on 32-bit systems, see | |
| 1374 |limits|) you cannot edit that line. The line will be split when reading | |
| 1375 the file. It is also possible that you get an "out of memory" error when | |
| 1376 reading the file. | |
| 1377 - Make sure the 'binary' option is set BEFORE loading the | |
| 1378 file. Otherwise both <CR> <NL> and <NL> are considered to end a line | |
| 1379 and when the file is written the <NL> will be replaced with <CR> <NL>. | |
| 1380 - <Nul> characters are shown on the screen as ^@. You can enter them with | |
| 1381 "CTRL-V CTRL-@" or "CTRL-V 000" {Vi cannot handle <Nul> characters in the | |
| 1382 file} | |
| 7013 | 1383 - To insert a <NL> character in the file split a line. When writing the |
| 7 | 1384 buffer to a file a <NL> will be written for the <EOL>. |
| 1385 - Vim normally appends an <EOL> at the end of the file if there is none. | |
| 1386 Setting the 'binary' option prevents this. If you want to add the final | |
| 1387 <EOL>, set the 'endofline' option. You can also read the value of this | |
| 1388 option to see if there was an <EOL> for the last line (you cannot see this | |
| 1389 in the text). | |
| 1390 | |
| 1391 ============================================================================== | |
| 1392 9. Encryption *encryption* | |
| 1393 | |
| 1394 Vim is able to write files encrypted, and read them back. The encrypted text | |
| 1395 cannot be read without the right key. | |
|
2283
7e1bd501306d
Mainly documentation updates.
Bram Moolenaar <bram@vim.org>
parents:
2267
diff
changeset
|
1396 {only available when compiled with the |+cryptv| feature} *E833* |
| 7 | 1397 |
| 2662 | 1398 The text in the swap file and the undo file is also encrypted. *E843* |
|
6070
32a77cc160d9
Update runtime files. Make matchparen plugin backwards compatible.
Bram Moolenaar <bram@vim.org>
parents:
5908
diff
changeset
|
1399 However, this is done block-by-block and may reduce the time needed to crack a |
|
32a77cc160d9
Update runtime files. Make matchparen plugin backwards compatible.
Bram Moolenaar <bram@vim.org>
parents:
5908
diff
changeset
|
1400 password. You can disable the swap file, but then a crash will cause you to |
|
32a77cc160d9
Update runtime files. Make matchparen plugin backwards compatible.
Bram Moolenaar <bram@vim.org>
parents:
5908
diff
changeset
|
1401 lose your work. The undo file can be disabled without much disadvantage. > |
|
32a77cc160d9
Update runtime files. Make matchparen plugin backwards compatible.
Bram Moolenaar <bram@vim.org>
parents:
5908
diff
changeset
|
1402 :set noundofile |
|
32a77cc160d9
Update runtime files. Make matchparen plugin backwards compatible.
Bram Moolenaar <bram@vim.org>
parents:
5908
diff
changeset
|
1403 :noswapfile edit secrets |
| 2267 | 1404 |
| 1405 Note: The text in memory is not encrypted. A system administrator may be able | |
| 1406 to see your text while you are editing it. When filtering text with | |
| 6122 | 1407 ":!filter" or using ":w !command" the text is also not encrypted, this may |
| 1408 reveal it to others. The 'viminfo' file is not encrypted. | |
| 1409 | |
| 1410 You could do this to edit very secret text: > | |
| 1411 :set noundofile viminfo= | |
| 1412 :noswapfile edit secrets.txt | |
|
7051
eff26a8620ce
commit https://github.com/vim/vim/commit/88774fdd23f08355297bb8cda78856859051d3c7
Christian Brabandt <cb@256bit.org>
parents:
7013
diff
changeset
|
1413 Keep in mind that without a swap file you risk losing your work in the event |
| 7013 | 1414 of a crash or a power failure. |
| 7 | 1415 |
| 1416 WARNING: If you make a typo when entering the key and then write the file and | |
| 1417 exit, the text will be lost! | |
| 1418 | |
| 1419 The normal way to work with encryption, is to use the ":X" command, which will | |
| 1420 ask you to enter a key. A following write command will use that key to | |
| 1421 encrypt the file. If you later edit the same file, Vim will ask you to enter | |
| 1422 a key. If you type the same key as that was used for writing, the text will | |
| 1423 be readable again. If you use a wrong key, it will be a mess. | |
| 1424 | |
| 1425 *:X* | |
| 1426 :X Prompt for an encryption key. The typing is done without showing the | |
| 1427 actual text, so that someone looking at the display won't see it. | |
| 1428 The typed key is stored in the 'key' option, which is used to encrypt | |
| 1429 the file when it is written. The file will remain unchanged until you | |
| 1430 write it. See also |-x|. | |
| 1431 | |
| 1432 The value of the 'key' options is used when text is written. When the option | |
| 1433 is not empty, the written file will be encrypted, using the value as the | |
| 1434 encryption key. A magic number is prepended, so that Vim can recognize that | |
| 1435 the file is encrypted. | |
| 1436 | |
| 1437 To disable the encryption, reset the 'key' option to an empty value: > | |
| 1438 :set key= | |
| 1439 | |
|
2360
d8e4b27cef80
Change 'cryptmethod' from a number to a string option. Make it global-local.
Bram Moolenaar <bram@vim.org>
parents:
2345
diff
changeset
|
1440 You can use the 'cryptmethod' option to select the type of encryption, use one |
| 6122 | 1441 of these: > |
| 1442 :setlocal cm=zip " weak method, backwards compatible | |
| 1443 :setlocal cm=blowfish " method with flaws | |
| 1444 :setlocal cm=blowfish2 " medium strong method | |
| 1445 | |
|
2360
d8e4b27cef80
Change 'cryptmethod' from a number to a string option. Make it global-local.
Bram Moolenaar <bram@vim.org>
parents:
2345
diff
changeset
|
1446 Do this before writing the file. When reading an encrypted file it will be |
|
d8e4b27cef80
Change 'cryptmethod' from a number to a string option. Make it global-local.
Bram Moolenaar <bram@vim.org>
parents:
2345
diff
changeset
|
1447 set automatically to the method used when that file was written. You can |
|
d8e4b27cef80
Change 'cryptmethod' from a number to a string option. Make it global-local.
Bram Moolenaar <bram@vim.org>
parents:
2345
diff
changeset
|
1448 change 'cryptmethod' before writing that file to change the method. |
| 6122 | 1449 |
| 6369 | 1450 To set the default method, used for new files, use this in your |vimrc| |
| 1451 file: > | |
| 6122 | 1452 set cm=blowfish2 |
| 6369 | 1453 Using "blowfish2" is highly recommended. Only use another method if you |
| 1454 must use an older Vim version that does not support it. | |
| 6122 | 1455 |
| 2725 | 1456 The message given for reading and writing a file will show "[crypted]" when |
| 6122 | 1457 using zip, "[blowfish]" when using blowfish, etc. |
|
2180
f60a0c9cbe6c
Add the blowfish encryption patch from Mohsin Ahmed. Needs more work.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
1458 |
|
2239
732cb7b31956
Crypt the text in the undo file if the file itself is crypted.
Bram Moolenaar <bram@vim.org>
parents:
2199
diff
changeset
|
1459 When writing an undo file, the same key and method will be used for the text |
|
732cb7b31956
Crypt the text in the undo file if the file itself is crypted.
Bram Moolenaar <bram@vim.org>
parents:
2199
diff
changeset
|
1460 in the undo file. |persistent-undo|. |
|
732cb7b31956
Crypt the text in the undo file if the file itself is crypted.
Bram Moolenaar <bram@vim.org>
parents:
2199
diff
changeset
|
1461 |
|
7659
07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Christian Brabandt <cb@256bit.org>
parents:
7480
diff
changeset
|
1462 To test for blowfish support you can use these conditions: > |
|
07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Christian Brabandt <cb@256bit.org>
parents:
7480
diff
changeset
|
1463 has('crypt-blowfish') |
|
07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Christian Brabandt <cb@256bit.org>
parents:
7480
diff
changeset
|
1464 has('crypt-blowfish2') |
|
07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Christian Brabandt <cb@256bit.org>
parents:
7480
diff
changeset
|
1465 This works since Vim 7.4.1099 while blowfish support was added earlier. |
|
07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Christian Brabandt <cb@256bit.org>
parents:
7480
diff
changeset
|
1466 Thus the condition failing doesn't mean blowfish is not supported. You can |
|
07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Christian Brabandt <cb@256bit.org>
parents:
7480
diff
changeset
|
1467 test for blowfish with: > |
|
07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Christian Brabandt <cb@256bit.org>
parents:
7480
diff
changeset
|
1468 v:version >= 703 |
|
07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Christian Brabandt <cb@256bit.org>
parents:
7480
diff
changeset
|
1469 And for blowfish2 with: > |
|
07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Christian Brabandt <cb@256bit.org>
parents:
7480
diff
changeset
|
1470 v:version > 704 || (v:version == 704 && has('patch401')) |
|
07f11de5efca
commit https://github.com/vim/vim/commit/85084ef1e999dcf50e8d466106a33bac24a0febb
Christian Brabandt <cb@256bit.org>
parents:
7480
diff
changeset
|
1471 < |
|
2199
014a996ac896
Use UINT32_T in the code, define it to uint32_t or unsigned int.
Bram Moolenaar <bram@vim.org>
parents:
2184
diff
changeset
|
1472 *E817* *E818* *E819* *E820* |
|
2184
5028c4d6d825
Fixed encryption big/little endian test.
Bram Moolenaar <bram@vim.org>
parents:
2180
diff
changeset
|
1473 When encryption does not work properly, you would be able to write your text |
|
5028c4d6d825
Fixed encryption big/little endian test.
Bram Moolenaar <bram@vim.org>
parents:
2180
diff
changeset
|
1474 to a file and never be able to read it back. Therefore a test is performed to |
|
5028c4d6d825
Fixed encryption big/little endian test.
Bram Moolenaar <bram@vim.org>
parents:
2180
diff
changeset
|
1475 check if the encryption works as expected. If you get one of these errors |
|
5028c4d6d825
Fixed encryption big/little endian test.
Bram Moolenaar <bram@vim.org>
parents:
2180
diff
changeset
|
1476 don't write the file encrypted! You need to rebuild the Vim binary to fix |
|
5028c4d6d825
Fixed encryption big/little endian test.
Bram Moolenaar <bram@vim.org>
parents:
2180
diff
changeset
|
1477 this. |
|
5028c4d6d825
Fixed encryption big/little endian test.
Bram Moolenaar <bram@vim.org>
parents:
2180
diff
changeset
|
1478 |
| 2264 | 1479 *E831* This is an internal error, "cannot happen". If you can reproduce it, |
|
2251
646d34788036
Fix a few compiler warnings. Fix crash with encrypted undo file.
Bram Moolenaar <bram@vim.org>
parents:
2239
diff
changeset
|
1480 please report to the developers. |
|
646d34788036
Fix a few compiler warnings. Fix crash with encrypted undo file.
Bram Moolenaar <bram@vim.org>
parents:
2239
diff
changeset
|
1481 |
|
2184
5028c4d6d825
Fixed encryption big/little endian test.
Bram Moolenaar <bram@vim.org>
parents:
2180
diff
changeset
|
1482 When reading a file that has been encrypted and the 'key' option is not empty, |
|
5028c4d6d825
Fixed encryption big/little endian test.
Bram Moolenaar <bram@vim.org>
parents:
2180
diff
changeset
|
1483 it will be used for decryption. If the value is empty, you will be prompted |
|
5028c4d6d825
Fixed encryption big/little endian test.
Bram Moolenaar <bram@vim.org>
parents:
2180
diff
changeset
|
1484 to enter the key. If you don't enter a key, or you enter the wrong key, the |
|
5028c4d6d825
Fixed encryption big/little endian test.
Bram Moolenaar <bram@vim.org>
parents:
2180
diff
changeset
|
1485 file is edited without being decrypted. There is no warning about using the |
|
5028c4d6d825
Fixed encryption big/little endian test.
Bram Moolenaar <bram@vim.org>
parents:
2180
diff
changeset
|
1486 wrong key (this makes brute force methods to find the key more difficult). |
| 7 | 1487 |
| 1488 If want to start reading a file that uses a different key, set the 'key' | |
| 1489 option to an empty string, so that Vim will prompt for a new one. Don't use | |
| 1490 the ":set" command to enter the value, other people can read the command over | |
| 1491 your shoulder. | |
| 1492 | |
| 1493 Since the value of the 'key' option is supposed to be a secret, its value can | |
| 1494 never be viewed. You should not set this option in a vimrc file. | |
| 1495 | |
| 2368 | 1496 An encrypted file can be recognized by the "file" command, if you add these |
| 1497 lines to "/etc/magic", "/usr/share/misc/magic" or wherever your system has the | |
| 7 | 1498 "magic" file: > |
| 1499 0 string VimCrypt~ Vim encrypted file | |
|
2364
151b037b7e74
Fix hang when resizing in diff mode and there are concealed items.
Bram Moolenaar <bram@vim.org>
parents:
2360
diff
changeset
|
1500 >9 string 01 - "zip" cryptmethod |
|
151b037b7e74
Fix hang when resizing in diff mode and there are concealed items.
Bram Moolenaar <bram@vim.org>
parents:
2360
diff
changeset
|
1501 >9 string 02 - "blowfish" cryptmethod |
| 6122 | 1502 >9 string 03 - "blowfish2" cryptmethod |
| 7 | 1503 |
| 1504 Notes: | |
| 1505 - Encryption is not possible when doing conversion with 'charconvert'. | |
| 1506 - Text you copy or delete goes to the numbered registers. The registers can | |
| 1507 be saved in the .viminfo file, where they could be read. Change your | |
| 1508 'viminfo' option to be safe. | |
| 1509 - Someone can type commands in Vim when you walk away for a moment, he should | |
| 1510 not be able to get the key. | |
| 1511 - If you make a typing mistake when entering the key, you might not be able to | |
| 1512 get your text back! | |
| 1513 - If you type the key with a ":set key=value" command, it can be kept in the | |
| 1514 history, showing the 'key' value in a viminfo file. | |
| 1515 - There is never 100% safety. The encryption in Vim has not been tested for | |
| 1516 robustness. | |
| 2581 | 1517 - The algorithm used for 'cryptmethod' "zip" is breakable. A 4 character key |
| 1518 in about one hour, a 6 character key in one day (on a Pentium 133 PC). This | |
| 1519 requires that you know some text that must appear in the file. An expert | |
| 1520 can break it for any key. When the text has been decrypted, this also means | |
| 1521 that the key can be revealed, and other files encrypted with the same key | |
| 1522 can be decrypted. | |
| 1523 - Pkzip uses the same encryption as 'cryptmethod' "zip", and US Govt has no | |
| 1524 objection to its export. Pkzip's public file APPNOTE.TXT describes this | |
| 1525 algorithm in detail. | |
| 6259 | 1526 - The implementation of 'cryptmethod' "blowfish" has a flaw. It is possible |
| 1527 to crack the first 64 bytes of a file and in some circumstances more of the | |
| 6122 | 1528 file. Use of it is not recommended, but it's still the strongest method |
| 1529 supported by Vim 7.3 and 7.4. The "zip" method is even weaker. | |
| 7 | 1530 - Vim originates from the Netherlands. That is where the sources come from. |
| 1531 Thus the encryption code is not exported from the USA. | |
| 1532 | |
| 1533 ============================================================================== | |
| 1534 10. Timestamps *timestamp* *timestamps* | |
| 1535 | |
| 5908 | 1536 Vim remembers the modification timestamp, mode and size of a file when you |
| 1537 begin editing it. This is used to avoid that you have two different versions | |
| 1538 of the same file (without you knowing this). | |
| 7 | 1539 |
| 5908 | 1540 After a shell command is run (|:!cmd| |suspend| |:read!| |K|) timestamps, |
| 1541 file modes and file sizes are compared for all buffers in a window. Vim will | |
| 1542 run any associated |FileChangedShell| autocommands or display a warning for | |
| 1543 any files that have changed. In the GUI this happens when Vim regains input | |
| 1544 focus. | |
| 7 | 1545 |
| 1546 *E321* *E462* | |
| 1547 If you want to automatically reload a file when it has been changed outside of | |
| 1548 Vim, set the 'autoread' option. This doesn't work at the moment you write the | |
| 1549 file though, only when the file wasn't changed inside of Vim. | |
| 1550 | |
| 1551 Note that if a FileChangedShell autocommand is defined you will not get a | |
| 1552 warning message or prompt. The autocommand is expected to handle this. | |
| 1553 | |
| 139 | 1554 There is no warning for a directory (e.g., with |netrw-browse|). But you do |
| 1555 get warned if you started editing a new file and it was created as a directory | |
| 1556 later. | |
| 7 | 1557 |
| 1558 When Vim notices the timestamp of a file has changed, and the file is being | |
| 1559 edited in a buffer but has not changed, Vim checks if the contents of the file | |
| 1560 is equal. This is done by reading the file again (into a hidden buffer, which | |
| 1561 is immediately deleted again) and comparing the text. If the text is equal, | |
| 1562 you will get no warning. | |
| 1563 | |
| 1564 If you don't get warned often enough you can use the following command. | |
| 1565 | |
| 1566 *:checkt* *:checktime* | |
| 1567 :checkt[ime] Check if any buffers were changed outside of Vim. | |
| 1568 This checks and warns you if you would end up with two | |
| 1569 versions of a file. | |
| 1570 If this is called from an autocommand, a ":global" | |
| 1571 command or is not typed the actual check is postponed | |
| 1572 until a moment the side effects (reloading the file) | |
| 1573 would be harmless. | |
| 1574 Each loaded buffer is checked for its associated file | |
| 1575 being changed. If the file was changed Vim will take | |
| 1576 action. If there are no changes in the buffer and | |
| 1577 'autoread' is set, the buffer is reloaded. Otherwise, | |
| 1578 you are offered the choice of reloading the file. If | |
| 1579 the file was deleted you get an error message. | |
| 1580 If the file previously didn't exist you get a warning | |
| 1581 if it exists now. | |
| 1582 Once a file has been checked the timestamp is reset, | |
| 1583 you will not be warned again. | |
| 1584 | |
| 1585 :[N]checkt[ime] {filename} | |
| 1586 :[N]checkt[ime] [N] | |
| 1587 Check the timestamp of a specific buffer. The buffer | |
| 1588 may be specified by name, number or with a pattern. | |
| 1589 | |
| 1590 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1591 *E813* *E814* |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1592 Vim will reload the buffer if you chose to. If a window is visible that |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1593 contains this buffer, the reloading will happen in the context of this window. |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1594 Otherwise a special window is used, so that most autocommands will work. You |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1595 can't close this window. A few other restrictions apply. Best is to make |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1596 sure nothing happens outside of the current buffer. E.g., setting |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1597 window-local options may end up in the wrong window. Splitting the window, |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1598 doing something there and closing it should be OK (if there are no side |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1599 effects from other autocommands). Closing unrelated windows and buffers will |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1600 get you into trouble. |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1601 |
| 7 | 1602 Before writing a file the timestamp is checked. If it has changed, Vim will |
| 1603 ask if you really want to overwrite the file: | |
| 1604 | |
| 1605 WARNING: The file has been changed since reading it!!! | |
| 1606 Do you really want to write to it (y/n)? | |
| 1607 | |
| 1608 If you hit 'y' Vim will continue writing the file. If you hit 'n' the write is | |
| 1609 aborted. If you used ":wq" or "ZZ" Vim will not exit, you will get another | |
| 1610 chance to write the file. | |
| 1611 | |
| 1612 The message would normally mean that somebody has written to the file after | |
| 1613 the edit session started. This could be another person, in which case you | |
| 1614 probably want to check if your changes to the file and the changes from the | |
| 1615 other person should be merged. Write the file under another name and check for | |
| 1616 differences (the "diff" program can be used for this). | |
| 1617 | |
| 1618 It is also possible that you modified the file yourself, from another edit | |
| 1619 session or with another command (e.g., a filter command). Then you will know | |
| 1620 which version of the file you want to keep. | |
| 1621 | |
| 236 | 1622 There is one situation where you get the message while there is nothing wrong: |
| 1623 On a Win32 system on the day daylight saving time starts. There is something | |
| 1624 in the Win32 libraries that confuses Vim about the hour time difference. The | |
| 1625 problem goes away the next day. | |
| 1626 | |
| 39 | 1627 ============================================================================== |
| 1628 11. File Searching *file-searching* | |
| 1629 | |
| 1630 {not available when compiled without the |+path_extra| feature} | |
| 1631 | |
| 1632 The file searching is currently used for the 'path', 'cdpath' and 'tags' | |
| 1668 | 1633 options, for |finddir()| and |findfile()|. Other commands use |wildcards| |
| 1634 which is slightly different. | |
| 1121 | 1635 |
| 1636 There are three different types of searching: | |
| 39 | 1637 |
| 444 | 1638 1) Downward search: *starstar* |
| 39 | 1639 Downward search uses the wildcards '*', '**' and possibly others |
| 1668 | 1640 supported by your operating system. '*' and '**' are handled inside Vim, |
| 1641 so they work on all operating systems. Note that "**" only acts as a | |
| 1642 special wildcard when it is at the start of a name. | |
| 39 | 1643 |
| 1620 | 1644 The usage of '*' is quite simple: It matches 0 or more characters. In a |
| 1645 search pattern this would be ".*". Note that the "." is not used for file | |
| 1646 searching. | |
| 39 | 1647 |
| 1648 '**' is more sophisticated: | |
| 1649 - It ONLY matches directories. | |
| 1668 | 1650 - It matches up to 30 directories deep by default, so you can use it to |
| 1651 search an entire directory tree | |
| 39 | 1652 - The maximum number of levels matched can be given by appending a number |
| 1653 to '**'. | |
| 1654 Thus '/usr/**2' can match: > | |
| 1655 /usr | |
| 1656 /usr/include | |
| 1657 /usr/include/sys | |
| 1658 /usr/include/g++ | |
| 1659 /usr/lib | |
| 1660 /usr/lib/X11 | |
| 1661 .... | |
| 1662 < It does NOT match '/usr/include/g++/std' as this would be three | |
| 1663 levels. | |
| 1668 | 1664 The allowed number range is 0 ('**0' is removed) to 100 |
| 39 | 1665 If the given number is smaller than 0 it defaults to 30, if it's |
| 1668 | 1666 bigger than 100 then 100 is used. The system also has a limit on the |
| 1667 path length, usually 256 or 1024 bytes. | |
| 39 | 1668 - '**' can only be at the end of the path or be followed by a path |
| 1669 separator or by a number and a path separator. | |
| 1670 | |
| 1671 You can combine '*' and '**' in any order: > | |
| 1672 /usr/**/sys/* | |
| 1668 | 1673 /usr/*tory/sys/** |
| 39 | 1674 /usr/**2/sys/* |
| 1675 | |
| 1676 2) Upward search: | |
| 1677 Here you can give a directory and then search the directory tree upward for | |
| 236 | 1678 a file. You could give stop-directories to limit the upward search. The |
| 39 | 1679 stop-directories are appended to the path (for the 'path' option) or to |
| 236 | 1680 the filename (for the 'tags' option) with a ';'. If you want several |
| 1681 stop-directories separate them with ';'. If you want no stop-directory | |
| 39 | 1682 ("search upward till the root directory) just use ';'. > |
| 1683 /usr/include/sys;/usr | |
| 1684 < will search in: > | |
| 1685 /usr/include/sys | |
| 1686 /usr/include | |
| 1687 /usr | |
| 1688 < | |
| 1689 If you use a relative path the upward search is started in Vim's current | |
| 1690 directory or in the directory of the current file (if the relative path | |
| 1691 starts with './' and 'd' is not included in 'cpoptions'). | |
| 1692 | |
| 1693 If Vim's current path is /u/user_x/work/release and you do > | |
| 1694 :set path=include;/u/user_x | |
| 1695 < and then search for a file with |gf| the file is searched in: > | |
| 1696 /u/user_x/work/release/include | |
| 1697 /u/user_x/work/include | |
| 1698 /u/user_x/include | |
| 1699 | |
| 236 | 1700 3) Combined up/downward search: |
| 39 | 1701 If Vim's current path is /u/user_x/work/release and you do > |
| 1702 set path=**;/u/user_x | |
| 1703 < and then search for a file with |gf| the file is searched in: > | |
| 1704 /u/user_x/work/release/** | |
| 1705 /u/user_x/work/** | |
| 1706 /u/user_x/** | |
| 1707 < | |
| 236 | 1708 BE CAREFUL! This might consume a lot of time, as the search of |
| 39 | 1709 '/u/user_x/**' includes '/u/user_x/work/**' and |
| 1710 '/u/user_x/work/release/**'. So '/u/user_x/work/release/**' is searched | |
| 236 | 1711 three times and '/u/user_x/work/**' is searched twice. |
| 39 | 1712 |
| 1713 In the above example you might want to set path to: > | |
| 1714 :set path=**,/u/user_x/** | |
|
2429
7ce8b24450dc
Improvements for ":find" completion. (Nazri Ramliy)
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
1715 < This searches: |
|
7ce8b24450dc
Improvements for ":find" completion. (Nazri Ramliy)
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
1716 /u/user_x/work/release/** ~ |
|
7ce8b24450dc
Improvements for ":find" completion. (Nazri Ramliy)
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
1717 /u/user_x/** ~ |
|
7ce8b24450dc
Improvements for ":find" completion. (Nazri Ramliy)
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
1718 This searches the same directories, but in a different order. |
| 39 | 1719 |
|
2429
7ce8b24450dc
Improvements for ":find" completion. (Nazri Ramliy)
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
1720 Note that completion for ":find", ":sfind", and ":tabfind" commands do not |
|
7ce8b24450dc
Improvements for ":find" completion. (Nazri Ramliy)
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
1721 currently work with 'path' items that contain a url or use the double star |
| 3456 | 1722 with depth limiter (/usr/**2) or upward search (;) notations. |
| 7 | 1723 |
| 1724 vim:tw=78:ts=8:ft=help:norl: |