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