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