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