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