|
1231
|
1 *message.txt* For Vim version 7.1. Last change: 2007 Mar 20
|
|
7
|
2
|
|
|
3
|
|
|
4 VIM REFERENCE MANUAL by Bram Moolenaar
|
|
|
5
|
|
|
6
|
|
|
7 This file contains an alphabetical list of messages and error messages that
|
|
|
8 Vim produces. You can use this if you don't understand what the message
|
|
|
9 means. It is not complete though.
|
|
|
10
|
|
|
11 1. Old messages |:messages|
|
|
|
12 2. Error messages |error-messages|
|
|
|
13 3. Messages |messages|
|
|
|
14
|
|
|
15 ==============================================================================
|
|
|
16 1. Old messages *:messages* *:mes* *message-history*
|
|
|
17
|
|
|
18 The ":messages" command can be used to view previously given messages. This
|
|
|
19 is especially useful when messages have been overwritten or truncated. This
|
|
|
20 depends on the 'shortmess' option.
|
|
|
21
|
|
625
|
22 The number of remembered messages is fixed at 20 for the tiny version and 100
|
|
|
23 for other versions.
|
|
7
|
24
|
|
447
|
25 *g<*
|
|
|
26 The "g<" command can be used to see the last page of previous command output.
|
|
532
|
27 This is especially useful if you accidentally typed <Space> at the hit-enter
|
|
1118
|
28 prompt. You are then back at the hit-enter prompt and can then scroll further
|
|
|
29 back.
|
|
447
|
30 Note: when you stopped the output with "q" at the more prompt only up to that
|
|
|
31 point will be displayed.
|
|
|
32 The previous command output is cleared when another command produces output.
|
|
|
33
|
|
7
|
34 If you are using translated messages, the first printed line tells who
|
|
|
35 maintains the messages or the translations. You can use this to contact the
|
|
|
36 maintainer when you spot a mistake.
|
|
|
37
|
|
|
38 If you want to find help on a specific (error) message, use the ID at the
|
|
|
39 start of the message. For example, to get help on the message: >
|
|
|
40
|
|
|
41 E72: Close error on swap file
|
|
|
42
|
|
|
43 or (translated): >
|
|
|
44
|
|
|
45 E72: Errore durante chiusura swap file
|
|
|
46
|
|
|
47 Use: >
|
|
|
48
|
|
|
49 :help E72
|
|
|
50
|
|
|
51 If you are lazy, it also works without the shift key: >
|
|
|
52
|
|
|
53 :help e72
|
|
|
54
|
|
|
55 ==============================================================================
|
|
|
56 2. Error messages *error-messages*
|
|
|
57
|
|
|
58 When an error message is displayed, but it is removed before you could read
|
|
|
59 it, you can see it again with: >
|
|
|
60 :echo errmsg
|
|
|
61 or view a list of recent messages with: >
|
|
|
62 :messages
|
|
|
63
|
|
|
64
|
|
|
65 LIST OF MESSAGES
|
|
|
66 *E222* *E228* *E232* *E256* *E293* *E298* *E304* *E317*
|
|
|
67 *E318* *E356* *E438* *E439* *E440* *E316* *E320* *E322*
|
|
84
|
68 *E323* *E341* *E473* *E570* *E685* >
|
|
7
|
69 Add to read buffer
|
|
|
70 makemap: Illegal mode
|
|
|
71 Cannot create BalloonEval with both message and callback
|
|
|
72 Hangul automata ERROR
|
|
|
73 block was not locked
|
|
|
74 Didn't get block nr {N}?
|
|
|
75 ml_timestamp: Didn't get block 0??
|
|
|
76 pointer block id wrong {N}
|
|
|
77 Updated too many blocks?
|
|
|
78 get_varp ERROR
|
|
|
79 u_undo: line numbers wrong
|
|
|
80 undo list corrupt
|
|
|
81 undo line missing
|
|
|
82 ml_get: cannot find line {N}
|
|
|
83 cannot find line {N}
|
|
|
84 line number out of range: {N} past the end
|
|
|
85 line count wrong in block {N}
|
|
|
86 Internal error
|
|
84
|
87 Internal error: {function}
|
|
7
|
88 fatal error in cs_manage_matches
|
|
|
89
|
|
|
90 This is an internal error. If you can reproduce it, please send in a bug
|
|
|
91 report. |bugs|
|
|
|
92
|
|
|
93 >
|
|
|
94 ATTENTION
|
|
|
95 Found a swap file by the name ...
|
|
|
96
|
|
|
97 See |ATTENTION|.
|
|
|
98
|
|
|
99 *E92* >
|
|
|
100 Buffer {N} not found
|
|
|
101
|
|
|
102 The buffer you requested does not exist. This can also happen when you have
|
|
|
103 wiped out a buffer which contains a mark or is referenced in another way.
|
|
|
104 |:bwipeout|
|
|
|
105
|
|
|
106 *E95* >
|
|
|
107 Buffer with this name already exists
|
|
|
108
|
|
|
109 You cannot have two buffers with the same name.
|
|
|
110
|
|
|
111 *E72* >
|
|
|
112 Close error on swap file
|
|
|
113
|
|
|
114 The |swap-file|, that is used to keep a copy of the edited text, could not be
|
|
|
115 closed properly. Mostly harmless.
|
|
|
116
|
|
|
117 *E169* >
|
|
|
118 Command too recursive
|
|
|
119
|
|
|
120 This happens when an Ex command executes an Ex command that executes an Ex
|
|
|
121 command, etc. This is only allowed 200 times. When it's more there probably
|
|
|
122 is an endless loop. Probably a |:execute| or |:source| command is involved.
|
|
|
123
|
|
|
124 *E254* >
|
|
|
125 Cannot allocate color {name}
|
|
|
126
|
|
|
127 The color name {name} is unknown. See |gui-colors| for a list of colors that
|
|
|
128 are available on most systems.
|
|
|
129
|
|
|
130 *E458* >
|
|
|
131 Cannot allocate colormap entry for "xxxx"
|
|
|
132 Cannot allocate colormap entry, some colors may be incorrect
|
|
|
133
|
|
|
134 This means that there are not enough colors available for Vim. It will still
|
|
|
135 run, but some of the colors will not appear in the specified color. Try
|
|
|
136 stopping other applications that use many colors, or start them after starting
|
|
|
137 gvim.
|
|
|
138 Netscape is known to consume a lot of colors. You can avoid this by telling
|
|
|
139 it to use its own colormap: >
|
|
|
140 netscape -install
|
|
|
141 Or tell it to limit to a certain number of colors (64 should work well): >
|
|
|
142 netscape -ncols 64
|
|
|
143 This can also be done with a line in your Xdefaults file: >
|
|
|
144 Netscape*installColormap: Yes
|
|
|
145 or >
|
|
|
146 Netscape*maxImageColors: 64
|
|
|
147 <
|
|
|
148 *E79* >
|
|
|
149 Cannot expand wildcards
|
|
|
150
|
|
|
151 A filename contains a strange combination of characters, which causes Vim to
|
|
|
152 attempt expanding wildcards but this fails. This does NOT mean that no
|
|
|
153 matching file names could be found, but that the pattern was illegal.
|
|
|
154
|
|
|
155 *E459* >
|
|
|
156 Cannot go back to previous directory
|
|
|
157
|
|
|
158 While expanding a file name, Vim failed to go back to the previously used
|
|
|
159 directory. All file names being used may be invalid now! You need to have
|
|
|
160 execute permission on the current directory.
|
|
|
161
|
|
|
162 *E190* *E212* >
|
|
|
163 Cannot open "{filename}" for writing
|
|
|
164 Can't open file for writing
|
|
|
165
|
|
|
166 For some reason the file you are writing to cannot be created or overwritten.
|
|
|
167 The reason could be that you do not have permission to write in the directory
|
|
|
168 or the file name is not valid.
|
|
|
169
|
|
|
170 *E166* >
|
|
|
171 Can't open linked file for writing
|
|
|
172
|
|
|
173 You are trying to write to a file which can't be overwritten, and the file is
|
|
|
174 a link (either a hard link or a symbolic link). Writing might still be
|
|
|
175 possible if the directory that contains the link or the file is writable, but
|
|
|
176 Vim now doesn't know if you want to delete the link and write the file in its
|
|
|
177 place, or if you want to delete the file itself and write the new file in its
|
|
|
178 place. If you really want to write the file under this name, you have to
|
|
|
179 manually delete the link or the file, or change the permissions so that Vim
|
|
|
180 can overwrite.
|
|
|
181
|
|
|
182 *E46* >
|
|
|
183 Cannot set read-only variable "{name}"
|
|
|
184
|
|
|
185 You are trying to assign a value to an argument of a function |a:var| or a Vim
|
|
|
186 internal variable |v:var| which is read-only.
|
|
|
187
|
|
|
188 *E90* >
|
|
|
189 Cannot unload last buffer
|
|
|
190
|
|
|
191 Vim always requires one buffer to be loaded, otherwise there would be nothing
|
|
|
192 to display in the window.
|
|
|
193
|
|
|
194 *E40* >
|
|
|
195 Can't open errorfile <filename>
|
|
|
196
|
|
|
197 When using the ":make" or ":grep" commands: The file used to save the error
|
|
|
198 messages or grep output cannot be opened. This can have several causes:
|
|
|
199 - 'shellredir' has a wrong value.
|
|
|
200 - The shell changes directory, causing the error file to be written in another
|
|
|
201 directory. This could be fixed by changing 'makeef', but then the make
|
|
|
202 command is still executed in the wrong directory.
|
|
|
203 - 'makeef' has a wrong value.
|
|
|
204 - The 'grepprg' or 'makeprg' could not be executed. This cannot always be
|
|
|
205 detected (especially on MS-Windows). Check your $PATH.
|
|
|
206
|
|
|
207 >
|
|
|
208 Can't open file C:\TEMP\VIoD243.TMP
|
|
|
209
|
|
|
210 On MS-Windows, this message appears when the output of an external command was
|
|
|
211 to be read, but the command didn't run successfully. This can be caused by
|
|
|
212 many things. Check the 'shell', 'shellquote', 'shellxquote', 'shellslash' and
|
|
|
213 related options. It might also be that the external command was not found,
|
|
|
214 there is no different error message for that.
|
|
|
215
|
|
|
216 *E12* >
|
|
|
217 Command not allowed from exrc/vimrc in current dir or tag search
|
|
|
218
|
|
|
219 Some commands are not allowed for security reasons. These commands mostly
|
|
|
220 come from a .exrc or .vimrc file in the current directory, or from a tags
|
|
|
221 file. Also see 'secure'.
|
|
|
222
|
|
|
223 *E74* >
|
|
|
224 Command too complex
|
|
|
225
|
|
|
226 A mapping resulted in a very long command string. Could be caused by a
|
|
|
227 mapping that indirectly calls itself.
|
|
|
228
|
|
|
229 >
|
|
|
230 CONVERSION ERROR
|
|
|
231
|
|
|
232 When writing a file and the text "CONVERSION ERROR" appears, this means that
|
|
|
233 some bits were lost when converting text from the internally used UTF-8 to the
|
|
|
234 format of the file. The file will not be marked unmodified. If you care
|
|
|
235 about the loss of information, set the 'fileencoding' option to another value
|
|
|
236 that can handle the characters in the buffer and write again. If you don't
|
|
|
237 care, you can abandon the buffer or reset the 'modified' option.
|
|
|
238
|
|
|
239 *E302* >
|
|
|
240 Could not rename swap file
|
|
|
241
|
|
|
242 When the file name changes, Vim tries to rename the |swap-file| as well.
|
|
|
243 This failed and the old swap file is now still used. Mostly harmless.
|
|
|
244
|
|
|
245 *E43* *E44* >
|
|
|
246 Damaged match string
|
|
|
247 Corrupted regexp program
|
|
|
248
|
|
|
249 Something inside Vim went wrong and resulted in a corrupted regexp. If you
|
|
|
250 know how to reproduce this problem, please report it. |bugs|
|
|
|
251
|
|
|
252 *E208* *E209* *E210* >
|
|
|
253 Error writing to "{filename}"
|
|
|
254 Error closing "{filename}"
|
|
|
255 Error reading "{filename}"
|
|
|
256
|
|
|
257 This occurs when Vim is trying to rename a file, but a simple change of file
|
|
|
258 name doesn't work. Then the file will be copied, but somehow this failed.
|
|
|
259 The result may be that both the original file and the destination file exist
|
|
|
260 and the destination file may be incomplete.
|
|
|
261
|
|
|
262 >
|
|
|
263 Vim: Error reading input, exiting...
|
|
|
264
|
|
|
265 This occurs when Vim cannot read typed characters while input is required.
|
|
|
266 Vim got stuck, the only thing it can do is exit. This can happen when both
|
|
|
267 stdin and stderr are redirected and executing a script that doesn't exit Vim.
|
|
|
268
|
|
|
269 *E47* >
|
|
|
270 Error while reading errorfile
|
|
|
271
|
|
|
272 Reading the error file was not possible. This is NOT caused by an error
|
|
|
273 message that was not recognized.
|
|
|
274
|
|
|
275 *E80* >
|
|
|
276 Error while writing
|
|
|
277
|
|
|
278 Writing a file was not completed successfully. The file is probably
|
|
|
279 incomplete.
|
|
|
280
|
|
|
281 *E13* *E189* >
|
|
|
282 File exists (use ! to override)
|
|
|
283 "{filename}" exists (use ! to override)
|
|
|
284
|
|
|
285 You are protected from accidentally overwriting a file. When you want to
|
|
|
286 write anyway, use the same command, but add a "!" just after the command.
|
|
|
287 Example: >
|
|
|
288 :w /tmp/test
|
|
|
289 changes to: >
|
|
|
290 :w! /tmp/test
|
|
|
291 <
|
|
457
|
292 *E768* >
|
|
|
293 Swap file exists: {filename} (:silent! overrides)
|
|
|
294
|
|
|
295 You are protected from overwriting a file that is being edited by Vim. This
|
|
|
296 happens when you use ":w! filename" and a swapfile is found.
|
|
|
297 - If the swapfile was left over from an old crashed edit session you may want
|
|
|
298 to delete the swapfile. Edit {filename} to find out information about the
|
|
|
299 swapfile.
|
|
|
300 - If you want to write anyway prepend ":silent!" to the command. For example: >
|
|
856
|
301 :silent! w! /tmp/test
|
|
457
|
302 < The special command is needed, since you already added the ! for overwriting
|
|
|
303 an existing file.
|
|
|
304
|
|
7
|
305 *E139* >
|
|
|
306 File is loaded in another buffer
|
|
|
307
|
|
|
308 You are trying to write a file under a name which is also used in another
|
|
|
309 buffer. This would result in two versions of the same file.
|
|
|
310
|
|
|
311 *E142* >
|
|
|
312 File not written: Writing is disabled by 'write' option
|
|
|
313
|
|
|
314 The 'write' option is off. This makes all commands that try to write a file
|
|
|
315 generate this message. This could be caused by a |-m| commandline argument.
|
|
|
316 You can switch the 'write' option on with ":set write".
|
|
|
317
|
|
|
318 *E25* >
|
|
|
319 GUI cannot be used: Not enabled at compile time
|
|
|
320
|
|
|
321 You are running a version of Vim that doesn't include the GUI code. Therefore
|
|
|
322 "gvim" and ":gui" don't work.
|
|
|
323
|
|
|
324 *E49* >
|
|
|
325 Invalid scroll size
|
|
|
326
|
|
|
327 This is caused by setting an invalid value for the 'scroll', 'scrolljump' or
|
|
|
328 'scrolloff' options.
|
|
|
329
|
|
|
330 *E17* >
|
|
|
331 "{filename}" is a directory
|
|
|
332
|
|
|
333 You tried to write a file with the name of a directory. This is not possible.
|
|
|
334 You probably need to append a file name.
|
|
|
335
|
|
|
336 *E19* >
|
|
|
337 Mark has invalid line number
|
|
|
338
|
|
|
339 You are using a mark that has a line number that doesn't exist. This can
|
|
|
340 happen when you have a mark in another file, and some other program has
|
|
|
341 deleted lines from it.
|
|
|
342
|
|
|
343 *E219* *E220* >
|
|
|
344 Missing {.
|
|
|
345 Missing }.
|
|
|
346
|
|
|
347 Using a {} construct in a file name, but there is a { without a matching } or
|
|
|
348 the other way around. It should be used like this: {foo,bar}. This matches
|
|
|
349 "foo" and "bar".
|
|
|
350
|
|
|
351 *E315* >
|
|
|
352 ml_get: invalid lnum:
|
|
|
353
|
|
|
354 This is an internal Vim error. Please try to find out how it can be
|
|
|
355 reproduced, and submit a bug report |bugreport.vim|.
|
|
|
356
|
|
|
357 *E173* >
|
|
|
358 {number} more files to edit
|
|
|
359
|
|
|
360 You are trying to exit, while the last item in the argument list has not been
|
|
|
361 edited. This protects you from accidentally exiting when you still have more
|
|
|
362 files to work on. See |argument-list|. If you do want to exit, just do it
|
|
|
363 again and it will work.
|
|
|
364
|
|
|
365 *E23* *E194* >
|
|
|
366 No alternate file
|
|
|
367 No alternate file name to substitute for '#'
|
|
|
368
|
|
|
369 The alternate file is not defined yet. See |alternate-file|.
|
|
|
370
|
|
|
371 *E32* >
|
|
|
372 No file name
|
|
|
373
|
|
|
374 The current buffer has no name. To write it, use ":w fname". Or give the
|
|
|
375 buffer a name with ":file fname".
|
|
|
376
|
|
|
377 *E141* >
|
|
|
378 No file name for buffer {number}
|
|
|
379
|
|
|
380 One of the buffers that was changed does not have a file name. Therefore it
|
|
|
381 cannot be written. You need to give the buffer a file name: >
|
|
|
382 :buffer {number}
|
|
|
383 :file {filename}
|
|
|
384 <
|
|
|
385 *E33* >
|
|
|
386 No previous substitute regular expression
|
|
|
387
|
|
|
388 When using the '~' character in a pattern, it is replaced with the previously
|
|
|
389 used pattern in a ":substitute" command. This fails when no such command has
|
|
167
|
390 been used yet. See |/~|. This also happens when using ":s/pat/%/", where the
|
|
|
391 "%" stands for the previous substitute string.
|
|
7
|
392
|
|
|
393 *E35* >
|
|
|
394 No previous regular expression
|
|
|
395
|
|
|
396 When using an empty search pattern, the previous search pattern is used. But
|
|
|
397 that is not possible if there was no previous search.
|
|
|
398
|
|
|
399 *E24* >
|
|
|
400 No such abbreviation
|
|
|
401
|
|
|
402 You have used an ":unabbreviate" command with an argument which is not an
|
|
|
403 existing abbreviation. All variations of this command give the same message:
|
|
|
404 ":cunabbrev", ":iunabbrev", etc. Check for trailing white space.
|
|
|
405
|
|
|
406 >
|
|
|
407 /dev/dsp: No such file or directory
|
|
|
408
|
|
|
409 Only given for GTK GUI with Gnome support. Gnome tries to use the audio
|
|
|
410 device and it isn't present. You can ignore this error.
|
|
|
411
|
|
|
412 *E31* >
|
|
|
413 No such mapping
|
|
|
414
|
|
|
415 You have used an ":unmap" command with an argument which is not an existing
|
|
|
416 mapping. All variations of this command give the same message: ":cunmap",
|
|
826
|
417 ":unmap!", etc. A few hints:
|
|
|
418 - Check for trailing white space.
|
|
|
419 - If the mapping is buffer-local you need to use ":unmap <buffer>".
|
|
|
420 |:map-<buffer>|
|
|
7
|
421
|
|
|
422 *E37* *E89* >
|
|
|
423 No write since last change (use ! to override)
|
|
|
424 No write since last change for buffer {N} (use ! to override)
|
|
|
425
|
|
|
426 You are trying to |abandon| a file that has changes. Vim protects you from
|
|
|
427 losing your work. You can either write the changed file with ":w", or, if you
|
|
|
428 are sure, |abandon| it anyway, and lose all the changes. This can be done by
|
|
|
429 adding a '!' character just after the command you used. Example: >
|
|
|
430 :e other_file
|
|
|
431 changes to: >
|
|
|
432 :e! other_file
|
|
|
433 <
|
|
|
434 *E162* >
|
|
|
435 No write since last change for buffer "{name}"
|
|
|
436
|
|
|
437 This appears when you try to exit Vim while some buffers are changed. You
|
|
|
438 will either have to write the changed buffer (with |:w|), or use a command to
|
|
|
439 abandon the buffer forcefully, e.g., with ":qa!". Careful, make sure you
|
|
|
440 don't throw away changes you really want to keep. You might have forgotten
|
|
|
441 about a buffer, especially when 'hidden' is set.
|
|
|
442
|
|
22
|
443 >
|
|
|
444 [No write since last change]
|
|
|
445
|
|
|
446 This appears when executing a shell command while at least one buffer was
|
|
|
447 changed. To avoid the message reset the 'warn' option.
|
|
|
448
|
|
7
|
449 *E38* >
|
|
|
450 Null argument
|
|
|
451
|
|
|
452 Something inside Vim went wrong and resulted in a NULL pointer. If you know
|
|
|
453 how to reproduce this problem, please report it. |bugs|
|
|
|
454
|
|
|
455 *E172* >
|
|
|
456 Only one file name allowed
|
|
|
457
|
|
|
458 The ":edit" command only accepts one file name. When you want to specify
|
|
|
459 several files for editing use ":next" |:next|.
|
|
|
460
|
|
|
461 *E41* *E82* *E83* *E342* >
|
|
|
462 Out of memory!
|
|
|
463 Out of memory! (allocating {number} bytes)
|
|
|
464 Cannot allocate any buffer, exiting...
|
|
|
465 Cannot allocate buffer, using other one...
|
|
|
466
|
|
|
467 Oh, oh. You must have been doing something complicated, or some other program
|
|
|
468 is consuming your memory. Be careful! Vim is not completely prepared for an
|
|
|
469 out-of-memory situation. First make sure that any changes are saved. Then
|
|
|
470 try to solve the memory shortage. To stay on the safe side, exit Vim and
|
|
|
471 start again. Also see |msdos-limitations|.
|
|
|
472
|
|
|
473 *E339* >
|
|
|
474 Pattern too long
|
|
|
475
|
|
|
476 This only happens on systems with 16 bit ints: The compiled regexp pattern is
|
|
|
477 longer than about 65000 characters. Try using a shorter pattern.
|
|
|
478
|
|
|
479 *E45* >
|
|
|
480 'readonly' option is set (use ! to override)
|
|
|
481
|
|
|
482 You are trying to write a file that was marked as read-only. To write the
|
|
|
483 file anyway, either reset the 'readonly' option, or add a '!' character just
|
|
|
484 after the command you used. Example: >
|
|
|
485 :w
|
|
|
486 changes to: >
|
|
|
487 :w!
|
|
|
488 <
|
|
|
489 *E294* *E295* *E301* >
|
|
|
490 Read error in swap file
|
|
|
491 Seek error in swap file read
|
|
|
492 Oops, lost the swap file!!!
|
|
|
493
|
|
|
494 Vim tried to read text from the |swap-file|, but something went wrong. The
|
|
|
495 text in the related buffer may now be corrupted! Check carefully before you
|
|
|
496 write a buffer. You may want to write it in another file and check for
|
|
|
497 differences.
|
|
|
498
|
|
|
499 *E192* >
|
|
|
500 Recursive use of :normal too deep
|
|
|
501
|
|
|
502 You are using a ":normal" command, whose argument again uses a ":normal"
|
|
|
503 command in a recursive way. This is restricted to 'maxmapdepth' levels. This
|
|
|
504 example illustrates how to get this message: >
|
|
|
505 :map gq :normal gq<CR>
|
|
|
506 If you type "gq", it will execute this mapping, which will call "gq" again.
|
|
|
507
|
|
|
508 *E22* >
|
|
|
509 Scripts nested too deep
|
|
|
510
|
|
|
511 Scripts can be read with the "-s" command-line argument and with the ":source"
|
|
|
512 command. The script can then again read another script. This can continue
|
|
|
513 for about 14 levels. When more nesting is done, Vim assumes that there is a
|
|
|
514 recursive loop somewhere and stops with this error message.
|
|
|
515
|
|
|
516 *E319* >
|
|
|
517 Sorry, the command is not available in this version
|
|
|
518
|
|
|
519 You have used a command that is not present in the version of Vim you are
|
|
|
520 using. When compiling Vim, many different features can be enabled or
|
|
|
521 disabled. This depends on how big Vim has chosen to be and the operating
|
|
|
522 system. See |+feature-list| for when which feature is available. The
|
|
|
523 |:version| command shows which feature Vim was compiled with.
|
|
|
524
|
|
|
525 *E300* >
|
|
|
526 Swap file already exists (symlink attack?)
|
|
|
527
|
|
|
528 This message appears when Vim is trying to open a swap file and finds it
|
|
|
529 already exists or finds a symbolic link in its place. This shouldn't happen,
|
|
|
530 because Vim already checked that the file doesn't exist. Either someone else
|
|
|
531 opened the same file at exactly the same moment (very unlikely) or someone is
|
|
|
532 attempting a symlink attack (could happen when editing a file in /tmp or when
|
|
|
533 'directory' starts with "/tmp", which is a bad choice).
|
|
|
534
|
|
|
535 *E432* >
|
|
|
536 Tags file not sorted: {file name}
|
|
|
537
|
|
|
538 Vim (and Vi) expect tags files to be sorted in ASCII order. Binary searching
|
|
|
539 can then be used, which is a lot faster than a linear search. If your tags
|
|
|
540 files are not properly sorted, reset the |'tagbsearch'| option.
|
|
|
541 This message is only given when Vim detects a problem when searching for a
|
|
|
542 tag. Sometimes this message is not given, even thought the tags file is not
|
|
|
543 properly sorted.
|
|
|
544
|
|
|
545 *E460* >
|
|
|
546 The resource fork would be lost (add ! to override)
|
|
|
547
|
|
|
548 On the Macintosh (classic), when writing a file, Vim attempts to preserve all
|
|
|
549 info about a file, including its resource fork. If this is not possible you
|
|
|
550 get this error message. Append "!" to the command name to write anyway (and
|
|
|
551 lose the info).
|
|
|
552
|
|
|
553 *E424* >
|
|
|
554 Too many different highlighting attributes in use
|
|
|
555
|
|
|
556 Vim can only handle about 223 different kinds of highlighting. If you run
|
|
|
557 into this limit, you have used too many |:highlight| commands with different
|
|
|
558 arguments. A ":highlight link" is not counted.
|
|
|
559
|
|
|
560 *E77* >
|
|
|
561 Too many file names
|
|
|
562
|
|
|
563 When expanding file names, more than one match was found. Only one match is
|
|
|
564 allowed for the command that was used.
|
|
|
565
|
|
|
566 *E303* >
|
|
|
567 Unable to open swap file for "{filename}", recovery impossible
|
|
|
568
|
|
|
569 Vim was not able to create a swap file. You can still edit the file, but if
|
|
|
570 Vim unexpected exits the changes will be lost. And Vim may consume a lot of
|
|
|
571 memory when editing a big file. You may want to change the 'directory' option
|
|
|
572 to avoid this error. See |swap-file|.
|
|
|
573
|
|
|
574 *E140* >
|
|
|
575 Use ! to write partial buffer
|
|
|
576
|
|
|
577 When using a range to write part of a buffer, it is unusual to overwrite the
|
|
|
578 original file. It is probably a mistake (e.g., when Visual mode was active
|
|
|
579 when using ":w"), therefore Vim requires using a ! after the command, e.g.:
|
|
|
580 ":3,10w!".
|
|
|
581 >
|
|
|
582
|
|
|
583 Warning: Cannot convert string "<Key>Escape,_Key_Cancel" to type
|
|
|
584 VirtualBinding
|
|
|
585
|
|
|
586 Messages like this appear when starting up. This is not a Vim problem, your
|
|
|
587 X11 configuration is wrong. You can find a hint on how to solve this here:
|
|
|
588 http://groups.yahoo.com/group/solarisonintel/message/12179.
|
|
|
589
|
|
|
590 *W10* >
|
|
|
591 Warning: Changing a readonly file
|
|
|
592
|
|
|
593 The file is read-only and you are making a change to it anyway. You can use
|
|
|
594 the |FileChangedRO| autocommand event to avoid this message (the autocommand
|
|
|
595 must reset the 'readonly' option). See 'modifiable' to completely disallow
|
|
|
596 making changes to a file.
|
|
548
|
597 This message is only given for the first change after 'readonly' has been set.
|
|
7
|
598
|
|
|
599 *W13* >
|
|
|
600 Warning: File "{filename}" has been created after editing started
|
|
|
601
|
|
|
602 You are editing a file in Vim when it didn't exist, but it does exist now.
|
|
|
603 You will have to decide if you want to keep the version in Vim or the newly
|
|
|
604 created file. This message is not given when 'buftype' is not empty.
|
|
|
605
|
|
|
606 *W11* >
|
|
|
607 Warning: File "{filename}" has changed since editing started
|
|
|
608
|
|
|
609 The file which you have started editing has got another timestamp and the
|
|
|
610 contents changed (more precisely: When reading the file again with the current
|
|
|
611 option settings and autocommands you would end up with different text). This
|
|
|
612 probably means that some other program changed the file. You will have to
|
|
|
613 find out what happened, and decide which version of the file you want to keep.
|
|
|
614 Set the 'autoread' option if you want to do this automatically.
|
|
|
615 This message is not given when 'buftype' is not empty.
|
|
|
616
|
|
|
617 There is one situation where you get this message even though there is nothing
|
|
|
618 wrong: If you save a file in Windows on the day the daylight saving time
|
|
|
619 starts. It can be fixed in one of these ways:
|
|
|
620 - Add this line in your autoexec.bat: >
|
|
|
621 SET TZ=-1
|
|
|
622 < Adjust the "-1" for your time zone.
|
|
|
623 - Disable "automatically adjust clock for daylight saving changes".
|
|
|
624 - Just write the file again the next day. Or set your clock to the next day,
|
|
|
625 write the file twice and set the clock back.
|
|
|
626
|
|
|
627 *W12* >
|
|
|
628 Warning: File "{filename}" has changed and the buffer was changed in Vim as well
|
|
|
629
|
|
|
630 Like the above, and the buffer for the file was changed in this Vim as well.
|
|
|
631 You will have to decide if you want to keep the version in this Vim or the one
|
|
|
632 on disk. This message is not given when 'buftype' is not empty.
|
|
|
633
|
|
|
634 *W16* >
|
|
|
635 Warning: Mode of file "{filename}" has changed since editing started
|
|
|
636
|
|
|
637 When the timestamp for a buffer was changed and the contents are still the
|
|
|
638 same but the mode (permissions) have changed. This usually occurs when
|
|
|
639 checking out a file from a version control system, which causes the read-only
|
|
|
640 bit to be reset. It should be safe to reload the file. Set 'autoread' to
|
|
|
641 automatically reload the file.
|
|
|
642
|
|
|
643 *E211* >
|
|
|
644 Warning: File "{filename}" no longer available
|
|
|
645
|
|
|
646 The file which you have started editing has disappeared, or is no longer
|
|
|
647 accessible. Make sure you write the buffer somewhere to avoid losing
|
|
|
648 changes. This message is not given when 'buftype' is not empty.
|
|
|
649
|
|
|
650 *W14* >
|
|
|
651 Warning: List of file names overflow
|
|
|
652
|
|
|
653 You must be using an awful lot of buffers. It's now possible that two buffers
|
|
|
654 have the same number, which causes various problems. You might want to exit
|
|
|
655 Vim and restart it.
|
|
|
656
|
|
|
657 *E296* *E297* >
|
|
|
658 Seek error in swap file write
|
|
|
659 Write error in swap file
|
|
|
660
|
|
|
661 This mostly happens when the disk is full. Vim could not write text into the
|
|
|
662 |swap-file|. It's not directly harmful, but when Vim unexpectedly exits some
|
|
|
663 text may be lost without recovery being possible. Vim might run out of memory
|
|
|
664 when this problem persists.
|
|
|
665
|
|
|
666 *connection-refused* >
|
|
|
667 Xlib: connection to "<machine-name:0.0" refused by server
|
|
|
668
|
|
|
669 This happens when Vim tries to connect to the X server, but the X server does
|
|
|
670 not allow a connection. The connection to the X server is needed to be able
|
|
|
671 to restore the title and for the xterm clipboard support. Unfortunately this
|
|
|
672 error message cannot be avoided, except by disabling the |+xterm_clipboard|
|
|
|
673 and |+X11| features.
|
|
|
674
|
|
|
675 *E10* >
|
|
|
676 \\ should be followed by /, ? or &
|
|
|
677
|
|
|
678 A command line started with a backslash or the range of a command contained a
|
|
|
679 backslash in a wrong place. This is often caused by command-line continuation
|
|
|
680 being disabled. Remove the 'C' flag from the 'cpoptions' option to enable it.
|
|
20
|
681 Or use ":set nocp".
|
|
7
|
682
|
|
|
683 *E471* >
|
|
|
684 Argument required
|
|
|
685
|
|
|
686 This happens when an Ex command with mandatory argument(s) was executed, but
|
|
|
687 no argument has been specified.
|
|
|
688
|
|
|
689 *E474* *E475* >
|
|
|
690 Invalid argument
|
|
|
691
|
|
|
692 An Ex command has been executed, but an invalid argument has been specified.
|
|
|
693
|
|
|
694 *E488* >
|
|
|
695 Trailing characters
|
|
|
696
|
|
|
697 An argument has been added to an Ex command that does not permit one.
|
|
|
698
|
|
|
699 *E477* *E478* >
|
|
|
700 No ! allowed
|
|
|
701 Don't panic!
|
|
|
702
|
|
|
703 You have added a "!" after an Ex command that doesn't permit one.
|
|
|
704
|
|
|
705 *E481* >
|
|
|
706 No range allowed
|
|
|
707
|
|
|
708 A range was specified for an Ex command that doesn't permit one. See
|
|
|
709 |cmdline-ranges|.
|
|
|
710
|
|
|
711 *E482* *E483* >
|
|
|
712 Can't create file {filename}
|
|
|
713 Can't get temp file name
|
|
|
714
|
|
|
715 Vim cannot create a temporary file.
|
|
|
716
|
|
|
717 *E484* *E485* >
|
|
|
718 Can't open file %s"
|
|
|
719 Can't read file %s"
|
|
|
720
|
|
|
721 Vim cannot read a temporary file.
|
|
|
722
|
|
|
723 *E464* >
|
|
|
724 Ambiguous use of user-defined command
|
|
|
725
|
|
|
726 There are two user-defined commands with a common name prefix, and you used
|
|
|
727 Command-line completion to execute one of them. |user-cmd-ambiguous|
|
|
|
728 Example: >
|
|
|
729 :command MyCommand1 echo "one"
|
|
|
730 :command MyCommand2 echo "two"
|
|
|
731 :MyCommand
|
|
|
732 <
|
|
|
733 *E492* >
|
|
|
734 Not an editor command
|
|
|
735
|
|
|
736 You tried to execute a command that is neither an Ex command nor
|
|
|
737 a user-defined command.
|
|
|
738
|
|
|
739 ==============================================================================
|
|
|
740 3. Messages *messages*
|
|
|
741
|
|
|
742 This is an (incomplete) overview of various messages that Vim gives:
|
|
|
743
|
|
446
|
744 *hit-enter* *press-enter* *hit-return*
|
|
|
745 *press-return* *hit-enter-prompt*
|
|
7
|
746
|
|
446
|
747 Press ENTER or type command to continue
|
|
7
|
748
|
|
|
749 This message is given when there is something on the screen for you to read,
|
|
|
750 and the screen is about to be redrawn:
|
|
|
751 - After executing an external command (e.g., ":!ls" and "=").
|
|
|
752 - Something is displayed on the status line that is longer than the width of
|
|
|
753 the window, or runs into the 'showcmd' or 'ruler' output.
|
|
|
754
|
|
446
|
755 -> Press <Enter> or <Space> to redraw the screen and continue, without that
|
|
|
756 key being used otherwise.
|
|
|
757 -> Press ':' or any other Normal mode command character to start that command.
|
|
698
|
758 -> Press 'k', <Up>, 'u', 'b' or 'g' to scroll back in the messages. This
|
|
|
759 works the same way as at the |more-prompt|. Only works when 'compatible'
|
|
|
760 is off and 'more' is on.
|
|
|
761 -> Pressing 'j', 'd' or <Down> is ignored when messages scrolled off the top
|
|
|
762 of the screen, 'compatible' is off and 'more' is on, to avoid that typing
|
|
|
763 one 'j' too many causes the messages to disappear.
|
|
446
|
764 -> Press <C-Y> to copy (yank) a modeless selection to the clipboard register.
|
|
7
|
765 -> Use a menu. The characters defined for Cmdline-mode are used.
|
|
|
766 -> When 'mouse' contains the 'r' flag, clicking the left mouse button works
|
|
|
767 like pressing <Space>. This makes it impossible to select text though.
|
|
|
768 -> For the GUI clicking the left mouse button in the last line works like
|
|
|
769 pressing <Space>.
|
|
|
770 {Vi: only ":" commands are interpreted}
|
|
|
771
|
|
447
|
772 If you accidentally hit <Enter> or <Space> and you want to see the displayed
|
|
|
773 text then use |g<|. This only works when 'more' is set.
|
|
|
774
|
|
7
|
775 To reduce the number of hit-enter prompts:
|
|
|
776 - Set 'cmdheight' to 2 or higher.
|
|
|
777 - Add flags to 'shortmess'.
|
|
|
778 - Reset 'showcmd' and/or 'ruler'.
|
|
|
779
|
|
539
|
780 If your script causes the hit-enter prompt and you don't know why, you may
|
|
|
781 find the |v:scrollstart| variable useful.
|
|
|
782
|
|
7
|
783 Also see 'mouse'. The hit-enter message is highlighted with the |hl-Question|
|
|
|
784 group.
|
|
|
785
|
|
|
786
|
|
|
787 *more-prompt* *pager* >
|
|
|
788 -- More --
|
|
446
|
789 -- More -- SPACE/d/j: screen/page/line down, b/u/k: up, q: quit
|
|
7
|
790
|
|
|
791 This message is given when the screen is filled with messages. It is only
|
|
|
792 given when the 'more' option is on. It is highlighted with the |hl-MoreMsg|
|
|
|
793 group.
|
|
|
794
|
|
|
795 Type effect ~
|
|
|
796 <CR> or <NL> or j or <Down> one more line
|
|
446
|
797 d down a page (half a screen)
|
|
|
798 <Space> or <PageDown> down a screen
|
|
447
|
799 G down all the way, until the hit-enter
|
|
856
|
800 prompt
|
|
446
|
801
|
|
7
|
802 <BS> or k or <Up> one line back (*)
|
|
446
|
803 u up a page (half a screen) (*)
|
|
|
804 b or <PageUp> back a screen (*)
|
|
447
|
805 g back to the start (*)
|
|
446
|
806
|
|
7
|
807 q, <Esc> or CTRL-C stop the listing
|
|
|
808 : stop the listing and enter a
|
|
|
809 command-line
|
|
|
810 <C-Y> yank (copy) a modeless selection to
|
|
|
811 the clipboard ("* and "+ registers)
|
|
|
812 {menu-entry} what the menu is defined to in
|
|
|
813 Cmdline-mode.
|
|
|
814 <LeftMouse> (**) next page
|
|
|
815
|
|
|
816 Any other key causes the meaning of the keys to be displayed.
|
|
|
817
|
|
446
|
818 (*) backwards scrolling is {not in Vi}. Only scrolls back to where messages
|
|
|
819 started to scroll.
|
|
7
|
820 (**) Clicking the left mouse button only works:
|
|
|
821 - For the GUI: in the last line of the screen.
|
|
|
822 - When 'r' is included in 'mouse' (but then selecting text won't work).
|
|
|
823
|
|
|
824
|
|
|
825 Note: The typed key is directly obtained from the terminal, it is not mapped
|
|
|
826 and typeahead is ignored.
|
|
|
827
|
|
532
|
828 The |g<| command can be used to see the last page of previous command output.
|
|
|
829 This is especially useful if you accidentally typed <Space> at the hit-enter
|
|
|
830 prompt.
|
|
|
831
|
|
7
|
832 vim:tw=78:ts=8:ft=help:norl:
|
