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