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