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