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