message.txt ForVim version 9.2. Last change: 2026 Feb 14VIM REFERENCE MANUAL by Bram MoolenaarThis file contains an alphabeticallist ofmessages and errormessages thatVim produces. You can use this if you don't understand what the messagemeans. Itis not complete though.1. Oldmessages:messages2. Errormessageserror-messages3. Messagesmessages==============================================================================1. Oldmessages:messages:mesmessage-historyThe ":messages" command can be used toview previously given messages. Thisis especially useful whenmessages have been overwritten or truncated. Thisdepends on the'shortmess' option.:mes[sages]Show all messages.:{count}mes[sages]Show the{count} most recent messages.:mes[sages] clearClear all messages.:{count}mes[sages] clearClear messages, keeping only the{count} mostrecent ones.The number of rememberedmessagesis determined by the'messagesopt' option.g<The "g<" command can be used to see the last page of previous command output.Thisis especially useful if you accidentally typed<Space>at thehit-enterprompt. You are then backat thehit-enter prompt and can then scroll furtherback.Note: If the output has been stopped with "q"at the more prompt,it will onlybe displayed up to this point.The previous command outputis cleared when another command produces output.The "g<" outputis not redirected.If you are using translated messages, the first printed line tells whomaintains themessages or the translations. You can use this to contact themaintainer when you spota mistake.If you want to findhelp ona specific (error) message, use the IDat thestart of the message. For example, to gethelp on the message:E72: Close error on swap fileor (translated):E72: Errore durante chiusura swap fileUse::help E72If you are lazy,it also works without theshift key::help e72The number in this ID has no meaning.==============================================================================2. Errormessageserror-messageserrorsWhen an error messageis displayed, butitis removed before you could readit, you can seeit again with: :echo errmsgOrviewalist of recentmessages with: :messagesSee:messages above.LIST OF MESSAGESE222E228E232E292E293E298E304E316E317E318E320E322E323E341E356E438E439E440E473E570 Add to read buffer makemap: Illegal mode Cannot create BalloonEval with both message and callback block was not locked Didn't get block nr {N}? ml_upd_block0(): Didn't get block 0?? pointer block id wrong {N} Updated too many blocks? get_varp ERROR u_undo: line numbers wrong undo list corrupt undo line missing ml_get: cannot find line {N} in buffer {nr} {name} line number out of range: {N} past the end line count wrong in block {N} Internal error: lalloc(0, ) Internal error: {function} Internal error in regexp fatal error in cs_manage_matches Invalid count for del_bytes(): {N}E340E685internal-errorThisis an internal error. If you can reproduce it, please send ina bugreport, seebugs. ATTENTION Found a swap file by the name ...SeeATTENTION.E92 Buffer {N} not foundThe buffer you requested does not exist. This can also happen when you havewiped outa buffer which containsamark oris referenced in another way.:bwipeoutE95 Buffer with this name already existsYou cannot have twobuffers with exactly the same name. This includes thepath leading to the file.E1513 Cannot switch buffer. 'winfixbuf' is enabledIfawindow has'winfixbuf' enabled, you cannot change that window's currentbuffer. You need to set'nowinfixbuf' before continuing. You may use [!] toforce thewindow to switch buffers, if your command supports it.E72 Close error on swap fileTheswap-file, thatis used to keepa copy of the edited text, could not beclosed properly. Mostly harmless.E169 Command too recursiveThis happens when anEx command executes anEx command that executes anExcommand, etc. The limitis 200 or the value of'maxfuncdepth', whateverislarger. When it's more there probablyis an endless loop. Probablya:execute or:source commandis involved.E254 Cannot allocate color {name}The color name{name}is unknown. Seegui-colors foralist of colors thatare available on most systems.E1244 Bad color string: {str}The provided color did not conform to thepattern #rrggbbE458 Cannot allocate colormap entry, some colors may be incorrectThis means that there are not enough colors available for Vim. It will stillrun, but some of the colors will not appear in the specified color. Trystopping other applications that use many colors, or start them afterstartinggvim.Browsers are known to consumea lot of colors. You can avoid this withnetscape by tellingit to use its own colormap:netscape -installOr tellit to limit toa certain number of colors (64 should work well):netscape -ncols 64This can also be done witha line in your Xdefaults file:Netscape*installColormap: YesorNetscape*maxImageColors: 64E79 Cannot expand wildcardsA filename containsa strange combination of characters, which causes Vim toattempt expandingwildcards but this fails. This does NOT mean that nomatching file names could be found, but that thepattern was illegal.E459 Cannot go back to previous directoryWhile expandinga file name, Vim failed togo back to the previously useddirectory. All file names being used may be invalid now! You need to haveexecute permission on the current directory.E190E212 Cannot open "{filename}" for writing Can't open file for writingFor some reason the file you arewriting to cannot be created or overwritten.The reason could be that youdo not have permission to write in the directoryor the file nameis not valid.E166 Can't open linked file for writingYou are trying to write toa file which can't be overwritten, and the fileisa link (eithera hard link ora symbolic link). Writing might still bepossible if the directory that contains the link or the fileis writable, butVim now doesn't know if you want to delete the link and write the file in itsplace, or if you want to delete the file itself and write the new file in itsplace. If you really want to write the file under this name, you have tomanually delete the link or the file, or change the permissions so that Vimcan overwrite.E46 Cannot change read-only variable "{name}"You are trying to assigna value to an argument ofa functiona:var ora Viminternal variablev:var whichis read-only.E90 Cannot unload last bufferVim always requires one buffer to be loaded, otherwise there would be nothingto display in the window.E40 Can't open errorfile <filename>When using the ":make" or ":grep" commands: The file used to save the errormessages orgrep output cannot be opened. This can have several causes:-'shellredir' hasa wrong value.- The shell changes directory, causing the error file to be written in another directory. This could be fixed bychanging'makeef', but then the make commandis still executed in the wrong directory.-'makeef' hasa wrong value.- The'grepprg' or'makeprg' could not be executed. This cannot always be detected (especially on MS-Windows). Check your $PATH. Can't open file C:\TEMP\VIoD243.TMPOn MS-Windows, this message appears when the output of an external command wasto be read, but the command didn't run successfully. This can be caused bymany things. Check the'shell','shellquote','shellxquote','shellslash' andrelated options. It might also be that the external command was not found,thereis no different error message for that.E12 Command not allowed from exrc/vimrc in current dir or tag searchSome commands are not allowed for security reasons. These commands mostlycome froma.exrc or.vimrc file in the current directory, or fromatagsfile. Also see'secure'.E74 Command too complexAmapping resulted ina very long command string. Could be caused byamapping that indirectly calls itself. CONVERSION ERRORWhenwritinga file and the text "CONVERSION ERROR" appears, this means thatsome bits were lost when converting text from the internally usedUTF-8 to theformat of the file. The file will not be marked unmodified. If you careabout the loss of information, set the'fileencoding' option to another valuethat can handle the characters in the buffer and write again. If you don'tcare, you canabandon the buffer or reset the'modified' option.If thereisabackup file, when'writebackup' or'backup'is set,it will notbe deleted, so you can moveit back into place if you want todiscard thechanges.E302 Could not rename swap fileWhen the file name changes, Vim tries to rename theswap-fileas well.This failed and the old swap fileis now still used. Mostly harmless.E43E44 Damaged match string Corrupted regexp programSomething inside Vim went wrong and resulted ina corrupted regexp. If youknow how to reproduce this problem, please report it.bugsE208E209E210 Error writing to "{filename}" Error closing "{filename}" Error reading "{filename}"This occurs when Vimis trying to renamea file, buta simple change of filename doesn't work. Then the file will be copied, but somehow this failed.The result may be that both the original file and the destination file existand the destination file may be incomplete. Vim: Error reading input, exiting...This occurs when Vim cannot read typed characters while inputis required.Vim got stuck, the only thingit candois exit. This can happen when bothstdin and stderr are redirected and executingascript that doesn't exit Vim.E47 Error while reading errorfileReading the error file was not possible. Thisis NOT caused by an errormessage that was not recognized.E80 Error while writingWritinga file was not completed successfully. The fileis probablyincomplete.E13E189 File exists (add ! to override) "{filename}" exists (add ! to override)You are protected from accidentally overwritinga file. When you want towrite anyway, use the same command, but adda "!" just after the command.Example::w /tmp/testchanges to::w! /tmp/testE768 Swap file exists: {filename} (:silent! overrides)You are protected from overwritinga file thatis being edited by Vim. Thishappens when you use ":w! filename" anda swapfileis found.- If the swapfile was left over from an old crashed edit session you may want to delete the swapfile. Edit{filename} to find out information about the swapfile.- If you want to write anyway prepend ":silent!" to the command. For example::silent! w! /tmp/test The special commandis needed, since you already added the! for overwriting an existing file.E139 File is loaded in another bufferYou are trying to writea file undera name whichis also used in anotherbuffer. This would result in two versions of the same file.E142 File not written: Writing is disabled by 'write' optionThe'write' optionis off. This makes all commands that try to writea filegenerate this message. This could be caused bya-m commandline argument.You can switch the'write' option on with ":set write".E25 GUI cannot be used: Not enabled at compile timeYou are runninga version of Vim that doesn't include theGUI code. Therefore"gvim" and ":gui" don't work.E49 Invalid scroll sizeThisis caused by setting an invalid value for the'scroll','scrolljump' or'scrolloff' options.E17 "{filename}" is a directoryYou tried to writea file with the name ofa directory. Thisis not possible.You probably need to appenda file name.E19 Mark has invalid line numberYou are usingamark that hasa line number that doesn't exist. This canhappen when you haveamark in another file, and some other program hasdeleted lines from it.E219E220 Missing {. Missing }.Usinga{} construct in a file name, but there is a { without a matching } orthe other way around. It should be used like this:{foo,bar}. This matches"foo" and "bar".E315 ml_get: invalid lnum: {number}Thisis an internal Vim error. Please try to find out howit can bereproduced, and submita bug reportbugreport.vim.E173 {number} more files to editYou are trying to exit, while the last item in the argumentlist has not beenedited. This protects you from accidentallyexiting when you still have morefiles to work on. Seeargument-list. If youdo want to exit, justdoitagain andit will work.E23E194 No alternate file No alternate file name to substitute for '#'The alternate fileis not defined yet. Seealternate-file.E32 No file nameThe current buffer has no name. To write it, use ":w fname". Or give thebuffera name with ":file fname".E141 No file name for buffer {number}One of thebuffers that was changed does not havea file name. Thereforeitcannot be written. You need to give the buffera file name::buffer {number}:file {filename}E33 No previous substitute regular expressionWhen using the '~' character ina pattern,itis replaced with the previouslyusedpattern ina ":substitute" command. This fails when no such command hasbeen used yet. See/~. This also happens when using ":s/pat/%/", where the"%" stands for the previous substitute string.E35 No previous regular expressionWhen using an empty search pattern, the previous searchpatternis used. Butthatis not possible if there was no previous search.E24 No such abbreviationYou have used an ":unabbreviate" command with an argument whichis not anexisting abbreviation. All variations of this command give the same message:":cunabbrev", ":iunabbrev", etc. Check for trailing white space. /dev/dsp: No such file or directoryOnly given forGTKGUI withGnome support.Gnome tries to use the audiodevice andit isn't present. You can ignore this error.E31 No such mappingYou have used an ":unmap" command with an argument whichis not an existingmapping. All variations of this command give the same message: ":cunmap",":unmap!", etc.A few hints:- Check for trailing white space.- If themappingis buffer-local you need to use ":unmap<buffer>".:map-<buffer>E37E89 No write since last change (add ! to override) No write since last change for buffer {N} (add ! to override)You are trying toabandona file that has changes. Vim protects you fromlosing your work. You can either write the changed file with ":w", or, if youare sure,abandonit anyway, and lose all the changes. This can be done byaddinga '!' character just after the command you used. Example::e other_filechanges to::e! other_fileE162 No write since last change for buffer "{name}"This appears when you try to exit Vim while somebuffers are changed. Youwill either have to write the changed buffer (with:w), or usea command toabandon the buffer forcefully, e.g., with ":qa!". Careful, make sure youdon't throw away changes you really want to keep. You might have forgottenabouta buffer, especially when'hidden'is set. [No write since last change]This appears when executinga shell command whileat least one buffer waschanged. To avoid the message reset the'warn' option.E38 Null argumentSomething inside Vim went wrong and resulted ina NULL pointer. If you knowhow to reproduce this problem, please report it.bugsE41E82E83E342 Out of memory! Out of memory! (allocating {number} bytes) Cannot allocate any buffer, exiting... Cannot allocate buffer, using other one...Oh, oh. Youmust have been doing something complicated, or some other programis consuming your memory. Be careful! Vimis not completely prepared for anout-of-memory situation. First make sure that any changes are saved. Thentry to solve the memory shortage. To stay on the safe side, exit Vim andstart again.If this happens while Vimis still initializing, editing filesis veryunlikely to work, therefore Vim will exit with value 123.Buffers are only partly kept in memory, thus editinga very large fileisunlikely to cause an out-of-memory situation. Undo informationis completelyin memory, you can reduce that with these options:-'undolevels' Set toa low value, or to -1 to disableundo completely. This helps fora change that affects all lines.-'undoreload' Set to zero to disable.E339 Pattern too longThis happens on systems with 16 bit ints: The compiledregexppatternislonger than about 65000 characters. Try usinga shorter pattern.It also happens when the offset ofa rule doesn't fit in thespace available.Try simplifying the pattern.E45 'readonly' option is set (add ! to override)You are trying to writea file that was markedas read-only. To write thefile anyway, either reset the'readonly' option, or adda '!' character justafter the command you used. Example::wchanges to::w!E294E295E301 Read error in swap file Seek error in swap file read Oops, lost the swap file!!!Vim tried to read text from theswap-file, but something went wrong. Thetext in the related buffer may now be corrupted! Check carefully before youwritea buffer. You may want to writeit in another file and check fordifferences.E192 Recursive use of :normal too deepYou are usinga ":normal" command, whose argument again usesa ":normal"command ina recursive way. Thisis restricted to'maxmapdepth' levels. Thisexample illustrates how to get this message::map gq :normal gq<CR>If you type "gq",it will execute this mapping, which will call "gq" again.E22 Scripts nested too deepScripts can be read with the "-s" command-line argument and with the:source! command. Thescript can then again read another script. This cancontinue for about 14 levels. When more nestingis done, Vim assumes thatthereisa recursive loop and stops with this error message.E319 Sorry, the command is not available in this versionYou have useda command thatis not present in the version of Vim you areusing. When compiling Vim, many different features can be enabled ordisabled. This depends on how big Vim has chosen to be and the operatingsystem. See+feature-list for when which featureis available. The:version command shows which feature Vim was compiled with.E300 Swap file already exists (symlink attack?)This message appears when Vimis trying to opena swap file and findsitalready exists or findsa symbolic link in its place. This shouldn't happen,because Vim already checked that the file doesn't exist. Either someone elseopened the same fileat exactly the same moment (very unlikely) or someoneisattemptinga symlink attack (could happen when editinga file in /tmp or when'directory' starts with "/tmp", whichisa bad choice).E432 Tags file not sorted: {file name}Vim (and Vi) expecttags files to be sorted in ASCII order. Binary searchingcan then be used, whichisa lot faster thana linear search. If yourtagsfiles are not properly sorted, reset the'tagbsearch' option.This messageis only given when Vim detectsa problem when searching foratag. Sometimes this messageis not given, even though thetags fileis notproperly sorted.E424 Too many different highlighting attributes in useVim can only handle about 223 different kinds of highlighting. If you runinto this limit, you have used too many:highlight commands with differentarguments.A ":highlight link"is not counted.E77 Too many file namesWhen expanding file names, more than one match was found. Only one matchisallowed for the command that was used.E303 Unable to open swap file for "{filename}", recovery impossibleVim was not able to createa swap file. You can still edit the file, but ifVim unexpectedly exits the changes will be lost. And Vim may consumea lot ofmemory when editinga big file. You may want to change the'directory' optionto avoid this error. This erroris not given when'directory'is empty. Seeswap-file.E140 Use ! to write partial bufferWhen usinga range to write part ofa buffer,itis unusual to overwrite theoriginal file. Itis probablya mistake (e.g., whenVisual mode was activewhen using ":w"), therefore Vim requires usinga! after the command, e.g.:":3,10w!". Warning: Cannot convert string "<Key>Escape,_Key_Cancel" to type VirtualBindingMessages like this appear whenstarting up. Thisis nota Vim problem, yourX11 configurationis wrong. You can finda hint on how to solve this here:http://groups.yahoo.com/group/solarisonintel/message/12179.[this URLis no longer valid]W10 Warning: Changing a readonly fileThe fileis read-only and you are makinga change toit anyway. You can usetheFileChangedROautocommand event to avoid this message (theautocommandmust reset the'readonly' option). See'modifiable' to completely disallowmaking changes toa file.This messageis only given for the first change after'readonly' has been set.W13 Warning: File "{filename}" has been created after editing startedYou are editinga file in Vim whenit didn't exist, butit does exist now.You will have to decide if you want to keep the version in Vim or the newlycreated file. This messageis not given when'buftype'is not empty.W11 Warning: File "{filename}" has changed since editing startedThe file which you have started editing has got anothertimestamp and thecontents changed (more precisely: When reading the file again with the currentoption settings andautocommands you wouldend up with different text). Thisprobably means that some other program changed the file. You will have tofind out what happened, and decide which version of the file you want to keep.Set the'autoread' option if you want todo this automatically.This messageis not given when'buftype'is not empty.Also see theFileChangedShell autocommand.You will be givenadialog with the following options:"OK":Dismiss the warning and continue editing. No changes areloaded, the buffer remainsasit is."Load File":Reload the file from disk,replacing the current buffercontents. Any changes you made in Vim that haven't been savedwill be lost."Load File and Options":Reload the file from disk and, in addition, apply relevantfile settings, suchas indentation,syntax highlighting, textwidth, and other filetype-specific options. This ensures thebuffer matches the file's intended configuration according toyour current settings and autocommands.Thereis one situation where you get this message even though thereis nothingwrong: If you savea file in Windows on the day the daylight saving timestarts. It can be fixed in one of these ways:- Add this line in your autoexec.bat: SET TZ=-1 Adjust the "-1" for your time zone.- Disable "automatically adjust clock for daylight saving changes".- Just write the file again the next day. Or set your clock to the next day, write the file twice and set the clock back.If you getW11 all the time, you may need to disable "Acronis ActiveProtection" or register Vimasa trusted service/application.W12 Warning: File "{filename}" has changed and the buffer was changed in Vim as wellLike the above, and the buffer for the file was changed in this Vimas well.You will have to decide if you want to keep the version in this Vim or the oneon disk. This messageis not given when'buftype'is not empty.W16 Warning: Mode of file "{filename}" has changed since editing startedWhen thetimestamp fora buffer was changed and the contents are still thesame but the mode (permissions) have changed. This usually occurs whenchecking outa file froma versioncontrol system, which causes the read-onlybit to be reset. It should be safe toreload the file. Set'autoread' toautomaticallyreload the file.E211 File "{filename}" no longer availableThe file which you have started editing has disappeared, oris no longeraccessible. Make sure you write the buffer somewhere to avoid losingchanges. This messageis not given when'buftype'is not empty.W14 Warning: List of file names overflowYoumust be using an awful lot of buffers. It's now possible that twobuffershave the same number, which causesvarious problems. You might want to exitVim and restart it.E931 Buffer cannot be registeredOut of memory ora duplicate buffer number. May happen after W14. Looking upa buffer will not always work, better restart Vim.E296E297 Seek error in swap file write Write error in swap fileThis mostly happens when the diskis full. Vim could not write text into theswap-file. It's not directly harmful, but when Vim unexpectedly exits sometext may be lost withoutrecovery being possible. Vim might run out of memorywhen this problem persists.connection-refused Xlib: connection to "<machine-name:0.0" refused by serverThis happens when Vim tries to connect to theX server, but theX server doesnot allowa connection. The connection to theX serveris needed to be ableto restore the title and for the xtermclipboard support. Unfortunately thiserror message cannot be avoided, except by disabling the+xterm_clipboardand+X11 features.E10 \\ should be followed by /, ? or &A command line started withabackslash or the range ofa command containedabackslash ina wrong place. Thisis often caused by command-line continuationbeing disabled. Remove the 'C' flag from the'cpoptions' option to enable it.Or use ":set nocp".E471 Argument requiredThis happens when anEx command with mandatory argument(s) was executed, butno argument has been specified.E474E475E983 Invalid argument Invalid argument: {arg} Duplicate argument: {arg}AnEx command or function has been executed, but an invalid argument has beenspecified.E488 Trailing characters Trailing characters: {text}An argument has been added to anEx command that does not permit one.Or the argument has invalid characters and has not been recognized.E477E478 No ! allowed Don't panic!You have addeda "!" after anEx command that doesn't permit one.E481 No range allowedA range was specified for anEx command that doesn't permit one. Seecmdline-ranges.E482E483 Can't create file {filename} Can't get temp file nameVim cannot createa temporary file.E484E485 Can't open file {filename} Can't read file {filename}Vim cannot reada temporary file. Especially on Windows, this can be causedby wrong escaping of special characters for cmd.exe; the approach waschanged with patch 7.3.443. Try usingshellescape() for all shell argumentsgiven tosystem(), or explicitly add escaping with ^. Also see'shellxquote' and'shellxescape'.E464 Ambiguous use of user-defined commandThere are two user-defined commands witha common name prefix, and you usedCommand-line completion to execute one of them.user-cmd-ambiguousExample::command MyCommand1 echo "one":command MyCommand2 echo "two":MyCommandE492 Not an editor commandYou tried to executea command thatis neither anEx command nora user-defined command.E943 Command table needs to be updated, run 'make cmdidxs'This can only happen whenchanging the source code, when addinga command insrc/ex_cmds.h. The lookup table then needs to be updated, by running:make cmdidxsE928E889 E928: String required E889: Number requiredThese happen whena value orexpressionis used that does not have theexpected type.==============================================================================3. MessagesmessagesThisis an (incomplete) overview ofvariousmessages that Vim gives:hit-enterpress-enterhit-returnpress-returnhit-enter-prompt Press ENTER or type command to continueThis messageis given when thereis something on the screen for you to read,and the screenis about to be redrawn:- After executing an external command (e.g., ":!ls" and "=").- Somethingis displayed on the status line thatis longer than the width of the window, or runs into the'showcmd' or'ruler' output.-> Press<Enter> or<Space> to redraw the screen and continue, without that key being used otherwise.-> Press ':' or any otherNormal mode command character to start that command.Note that after an external command some special keys, suchas the cursor keys, may not work normally, because theterminalis still set toa state for executing the external command.-> Press 'k',<Up>, 'u', 'b' or 'g' to scroll back in the messages. This works the same wayasat themore-prompt. Only works when'compatible'is off and'more'is on.-> Pressing 'j', 'f', 'd' or<Down>is ignored whenmessages scrolled off the top of the screen,'compatible'is off and'more'is on, to avoid that typing one 'j' or 'f' too many causes themessages to disappear.-> Press<C-Y> to copy (yank)a modeless selection to theclipboard register.-> Usea menu. The characters defined forCmdline-mode are used.-> When'mouse' contains the 'r' flag, clicking the left mouse button works like pressing<Space>. This makesit impossible to select text though.-> For theGUI clicking the left mouse button in the last line works like pressing<Space>.->q won't startrecording intoa register (rationale:itis often usedas "quit" prompt key by users)If you accidentally hit<Enter> or<Space> and you want to see the displayedtext then useg<. This only works when'more'is set.To reduce the number ofhit-enter prompts:- Set'messagesopt'.- Set'cmdheight' to 2 or higher.- Add flags to'shortmess'.- Reset'showcmd' and/or'ruler'.- Make sure:echo textis shorter than or equal tov:echospace screen cells.If yourscript causes thehit-enter prompt and you don't know why, you mayfind thev:scrollstart variable useful.Also see'mouse'. Thehit-enter messageis highlighted with thehl-Questiongroup.more-promptpager -- More -- -- More -- SPACE/d/j: screen/page/line down, b/u/k: up, q: quitThis messageis given when the screenis filled with messages. Itis onlygiven when the'more' optionis on. Itis highlighted with thehl-MoreMsggroup.Typeeffect<CR> or<NL> orj or<Down>one more lineddowna page (halfa screen)<Space> orf or<PageDown> orCTRL-Fdowna screenGdown all the way, until thehit-enter prompt<BS> ork or<Up>one line backuupa page (halfa screen)b or<PageUp> orCTRL-Bbacka screengback to the start q,<Esc> orCTRL-Cstop the listing:stop the listing and enteracommand-line<C-Y>yank (copy)a modelessselection to theclipboard("* and "+ registers){menu-entry}what the menuis defined toin Cmdline-mode.<LeftMouse>next page(*)Any other key causes the meaning of the keys to be displayed.(*) Clicking the left mouse button only works:- For the GUI: in the last line of the screen.- When 'r'is included in'mouse' (but then selecting text won't work).Note: The typed keyis directly obtained from the terminal,itis not mappedand typeaheadis ignored.Theg< command can be used to see the last page of previous command output.Thisis especially useful if you accidentally typed<Space>at thehit-enterprompt. vim:tw=78:ts=8:noet:ft=help:norl: