codekingpro/portable-devtools

1*message.txt*	For Vim version 9.2.  Last change: 2026 Feb 142 3 4		  VIM REFERENCE MANUAL	  by Bram Moolenaar5 6 7This file contains an alphabetical list of messages and error messages that8Vim produces.  You can use this if you don't understand what the message9means.  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.  This19is especially useful when messages have been overwritten or truncated.  This20depends on the 'shortmess' option.21 22	:mes[sages]		Show all messages.23 24	:{count}mes[sages]	Show the {count} most recent messages.25 26	:mes[sages] clear	Clear all messages.27 28	:{count}mes[sages] clear29				Clear messages, keeping only the {count} most30				recent ones.31 32The number of remembered messages is determined by the 'messagesopt' option.33 34								*g<*35The "g<" command can be used to see the last page of previous command output.36This is especially useful if you accidentally typed <Space> at the hit-enter37prompt.  You are then back at the hit-enter prompt and can then scroll further38back.39Note: If the output has been stopped with "q" at the more prompt, it will only40be displayed up to this point.41The previous command output is cleared when another command produces output.42The "g<" output is not redirected.43 44If you are using translated messages, the first printed line tells who45maintains the messages or the translations.  You can use this to contact the46maintainer when you spot a mistake.47 48If you want to find help on a specific (error) message, use the ID at the49start of the message.  For example, to get help on the message:50 51	E72: Close error on swap file ~52 53or (translated):54 55	E72: Errore durante chiusura swap file ~56 57Use: >58 59	:help E7260 61If you are lazy, it also works without the shift key: >62 63	:help e7264 65The number in this ID has no meaning.66 67==============================================================================682. Error messages				*error-messages* *errors*69 70When an error message is displayed, but it is removed before you could read71it, you can see it again with: >72  :echo errmsg73Or view a list of recent messages with: >74  :messages75See `:messages` above.76 77 78LIST OF MESSAGES79			*E222* *E228* *E232* *E292* *E293* *E298* *E304* *E316*80			*E317* *E318* *E320* *E322* *E323* *E341* *E356* *E438*81			*E439* *E440* *E473* *E570*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 ~94  ml_get: cannot find line {N} in buffer {nr} {name} ~95  line number out of range: {N} past the end ~96  line count wrong in block {N} ~97  Internal error: lalloc(0, ) ~98  Internal error: {function} ~99  Internal error in regexp ~100  fatal error in cs_manage_matches ~101  Invalid count for del_bytes(): {N} ~102						*E340* *E685* *internal-error*103This is an internal error.  If you can reproduce it, please send in a bug104report, see |bugs|.105 106 107  ATTENTION ~108  Found a swap file by the name ... ~109 110See |ATTENTION|.111 112							*E92*113  Buffer {N} not found ~114 115The buffer you requested does not exist.  This can also happen when you have116wiped out a buffer which contains a mark or is referenced in another way.117|:bwipeout|118 119							*E95*120  Buffer with this name already exists ~121 122You cannot have two buffers with exactly the same name.  This includes the123path leading to the file.124 125							*E1513*126  Cannot switch buffer. 'winfixbuf' is enabled ~127 128If a window has 'winfixbuf' enabled, you cannot change that window's current129buffer.  You need to set 'nowinfixbuf' before continuing.  You may use [!] to130force the window to switch buffers, if your command supports it.131 132							*E72*133  Close error on swap file ~134 135The |swap-file|, that is used to keep a copy of the edited text, could not be136closed properly.  Mostly harmless.137 138							*E169*139  Command too recursive ~140 141This happens when an Ex command executes an Ex command that executes an Ex142command, etc.  The limit is 200 or the value of 'maxfuncdepth', whatever is143larger.  When it's more there probably is an endless loop.  Probably a144|:execute| or |:source| command is involved.145 146							*E254*147  Cannot allocate color {name} ~148 149The color name {name} is unknown.  See |gui-colors| for a list of colors that150are available on most systems.151 152							*E1244*153  Bad color string: {str} ~154 155The provided color did not conform to the pattern #rrggbb156 157							*E458*158  Cannot allocate colormap entry, some colors may be incorrect ~159 160This means that there are not enough colors available for Vim.  It will still161run, but some of the colors will not appear in the specified color.  Try162stopping other applications that use many colors, or start them after starting163gvim.164Browsers are known to consume a lot of colors.  You can avoid this with165netscape by telling it to use its own colormap:166	netscape -install ~167Or tell it to limit to a certain number of colors (64 should work well):168	netscape -ncols 64 ~169This can also be done with a line in your Xdefaults file:170	Netscape*installColormap: Yes ~171or172	Netscape*maxImageColors:  64 ~173 174							*E79*175  Cannot expand wildcards ~176 177A filename contains a strange combination of characters, which causes Vim to178attempt expanding wildcards but this fails.  This does NOT mean that no179matching file names could be found, but that the pattern was illegal.180 181							*E459*182  Cannot go back to previous directory ~183 184While expanding a file name, Vim failed to go back to the previously used185directory.  All file names being used may be invalid now!  You need to have186execute permission on the current directory.187 188							*E190* *E212*189  Cannot open "{filename}" for writing ~190  Can't open file for writing ~191 192For some reason the file you are writing to cannot be created or overwritten.193The reason could be that you do not have permission to write in the directory194or the file name is not valid.195 196							*E166*197  Can't open linked file for writing ~198 199You are trying to write to a file which can't be overwritten, and the file is200a link (either a hard link or a symbolic link).  Writing might still be201possible if the directory that contains the link or the file is writable, but202Vim now doesn't know if you want to delete the link and write the file in its203place, or if you want to delete the file itself and write the new file in its204place.  If you really want to write the file under this name, you have to205manually delete the link or the file, or change the permissions so that Vim206can overwrite.207 208							*E46*209  Cannot change read-only variable "{name}" ~210 211You are trying to assign a value to an argument of a function |a:var| or a Vim212internal variable |v:var| which is read-only.213 214							*E90*215  Cannot unload last buffer ~216 217Vim always requires one buffer to be loaded, otherwise there would be nothing218to display in the window.219 220							*E40*221  Can't open errorfile <filename> ~222 223When using the ":make" or ":grep" commands: The file used to save the error224messages or grep output cannot be opened.  This can have several causes:225- 'shellredir' has a wrong value.226- The shell changes directory, causing the error file to be written in another227  directory.  This could be fixed by changing 'makeef', but then the make228  command is still executed in the wrong directory.229- 'makeef' has a wrong value.230- The 'grepprg' or 'makeprg' could not be executed.  This cannot always be231  detected (especially on MS-Windows).  Check your $PATH.232 233 234  Can't open file C:\TEMP\VIoD243.TMP ~235 236On MS-Windows, this message appears when the output of an external command was237to be read, but the command didn't run successfully.  This can be caused by238many things.  Check the 'shell', 'shellquote', 'shellxquote', 'shellslash' and239related options.  It might also be that the external command was not found,240there is no different error message for that.241 242							*E12*243  Command not allowed from exrc/vimrc in current dir or tag search ~244 245Some commands are not allowed for security reasons.  These commands mostly246come from a .exrc or .vimrc file in the current directory, or from a tags247file.  Also see 'secure'.248 249							*E74*250  Command too complex ~251 252A mapping resulted in a very long command string.  Could be caused by a253mapping that indirectly calls itself.254 255 256  CONVERSION ERROR ~257 258When writing a file and the text "CONVERSION ERROR" appears, this means that259some bits were lost when converting text from the internally used UTF-8 to the260format of the file.  The file will not be marked unmodified.  If you care261about the loss of information, set the 'fileencoding' option to another value262that can handle the characters in the buffer and write again.  If you don't263care, you can abandon the buffer or reset the 'modified' option.264If there is a backup file, when 'writebackup' or 'backup' is set, it will not265be deleted, so you can move it back into place if you want to discard the266changes.267 268							*E302*269  Could not rename swap file ~270 271When the file name changes, Vim tries to rename the |swap-file| as well.272This failed and the old swap file is now still used.  Mostly harmless.273 274							*E43* *E44*275  Damaged match string ~276  Corrupted regexp program ~277 278Something inside Vim went wrong and resulted in a corrupted regexp.  If you279know how to reproduce this problem, please report it. |bugs|280 281							*E208* *E209* *E210*282  Error writing to "{filename}" ~283  Error closing "{filename}" ~284  Error reading "{filename}" ~285 286This occurs when Vim is trying to rename a file, but a simple change of file287name doesn't work.  Then the file will be copied, but somehow this failed.288The result may be that both the original file and the destination file exist289and the destination file may be incomplete.290 291 292  Vim: Error reading input, exiting... ~293 294This occurs when Vim cannot read typed characters while input is required.295Vim got stuck, the only thing it can do is exit.  This can happen when both296stdin and stderr are redirected and executing a script that doesn't exit Vim.297 298							*E47*299  Error while reading errorfile ~300 301Reading the error file was not possible.  This is NOT caused by an error302message that was not recognized.303 304							*E80*305  Error while writing ~306 307Writing a file was not completed successfully.  The file is probably308incomplete.309 310							*E13* *E189*311  File exists (add ! to override) ~312  "{filename}" exists (add ! to override) ~313 314You are protected from accidentally overwriting a file.  When you want to315write anyway, use the same command, but add a "!" just after the command.316Example: >317	:w /tmp/test318changes to: >319	:w! /tmp/test320<321							*E768*322  Swap file exists: {filename} (:silent! overrides) ~323 324You are protected from overwriting a file that is being edited by Vim.  This325happens when you use ":w! filename" and a swapfile is found.326- If the swapfile was left over from an old crashed edit session you may want327  to delete the swapfile.  Edit {filename} to find out information about the328  swapfile.329- If you want to write anyway prepend ":silent!" to the command.  For example: >330	:silent! w! /tmp/test331< The special command is needed, since you already added the ! for overwriting332  an existing file.333 334							*E139*335  File is loaded in another buffer ~336 337You are trying to write a file under a name which is also used in another338buffer.  This would result in two versions of the same file.339 340							*E142*341  File not written: Writing is disabled by 'write' option ~342 343The 'write' option is off.  This makes all commands that try to write a file344generate this message.  This could be caused by a |-m| commandline argument.345You can switch the 'write' option on with ":set write".346 347							*E25*348  GUI cannot be used: Not enabled at compile time ~349 350You are running a version of Vim that doesn't include the GUI code.  Therefore351"gvim" and ":gui" don't work.352 353							*E49*354  Invalid scroll size ~355 356This is caused by setting an invalid value for the 'scroll', 'scrolljump' or357'scrolloff' options.358 359							*E17*360  "{filename}" is a directory ~361 362You tried to write a file with the name of a directory.  This is not possible.363You probably need to append a file name.364 365							*E19*366  Mark has invalid line number ~367 368You are using a mark that has a line number that doesn't exist.  This can369happen when you have a mark in another file, and some other program has370deleted lines from it.371 372							*E219* *E220*373  Missing {. ~374  Missing }. ~375 376Using a {} construct in a file name, but there is a { without a matching } or377the other way around.  It should be used like this: {foo,bar}.  This matches378"foo" and "bar".379 380							*E315*381  ml_get: invalid lnum: {number} ~382 383This is an internal Vim error.  Please try to find out how it can be384reproduced, and submit a bug report |bugreport.vim|.385 386							*E173*387  {number} more files to edit ~388 389You are trying to exit, while the last item in the argument list has not been390edited.  This protects you from accidentally exiting when you still have more391files to work on.  See |argument-list|.  If you do want to exit, just do it392again and it will work.393 394							*E23* *E194*395  No alternate file ~396  No alternate file name to substitute for '#' ~397 398The alternate file is not defined yet.  See |alternate-file|.399 400							*E32*401  No file name ~402 403The current buffer has no name.  To write it, use ":w fname".  Or give the404buffer a name with ":file fname".405 406							*E141*407  No file name for buffer {number} ~408 409One of the buffers that was changed does not have a file name.  Therefore it410cannot be written.  You need to give the buffer a file name: >411	:buffer {number}412	:file {filename}413<414							*E33*415  No previous substitute regular expression ~416 417When using the '~' character in a pattern, it is replaced with the previously418used pattern in a ":substitute" command.  This fails when no such command has419been used yet.  See |/~|.  This also happens when using ":s/pat/%/", where the420"%" stands for the previous substitute string.421 422							*E35*423  No previous regular expression ~424 425When using an empty search pattern, the previous search pattern is used.  But426that is not possible if there was no previous search.427 428							*E24*429  No such abbreviation ~430 431You have used an ":unabbreviate" command with an argument which is not an432existing abbreviation.  All variations of this command give the same message:433":cunabbrev", ":iunabbrev", etc.  Check for trailing white space.434 435 436  /dev/dsp: No such file or directory ~437 438Only given for GTK GUI with Gnome support.  Gnome tries to use the audio439device and it isn't present.  You can ignore this error.440 441							*E31*442  No such mapping ~443 444You have used an ":unmap" command with an argument which is not an existing445mapping.  All variations of this command give the same message: ":cunmap",446":unmap!", etc.  A few hints:447- Check for trailing white space.448- If the mapping is buffer-local you need to use ":unmap <buffer>".449  |:map-<buffer>|450 451							*E37* *E89*452  No write since last change (add ! to override) ~453  No write since last change for buffer {N} (add ! to override) ~454 455You are trying to |abandon| a file that has changes.  Vim protects you from456losing your work.  You can either write the changed file with ":w", or, if you457are sure, |abandon| it anyway, and lose all the changes.  This can be done by458adding a '!' character just after the command you used.  Example: >459	:e other_file460changes to: >461	:e! other_file462<463							*E162*464  No write since last change for buffer "{name}" ~465 466This appears when you try to exit Vim while some buffers are changed.  You467will either have to write the changed buffer (with |:w|), or use a command to468abandon the buffer forcefully, e.g., with ":qa!".  Careful, make sure you469don't throw away changes you really want to keep.  You might have forgotten470about a buffer, especially when 'hidden' is set.471 472 473  [No write since last change] ~474 475This appears when executing a shell command while at least one buffer was476changed.  To avoid the message reset the 'warn' option.477 478							*E38*479  Null argument ~480 481Something inside Vim went wrong and resulted in a NULL pointer.  If you know482how to reproduce this problem, please report it. |bugs|483 484						*E41* *E82* *E83* *E342*485  Out of memory! ~486  Out of memory!  (allocating {number} bytes) ~487  Cannot allocate any buffer, exiting... ~488  Cannot allocate buffer, using other one... ~489 490Oh, oh.  You must have been doing something complicated, or some other program491is consuming your memory.  Be careful!  Vim is not completely prepared for an492out-of-memory situation.  First make sure that any changes are saved.  Then493try to solve the memory shortage.  To stay on the safe side, exit Vim and494start again.495 496If this happens while Vim is still initializing, editing files is very497unlikely to work, therefore Vim will exit with value 123.498 499Buffers are only partly kept in memory, thus editing a very large file is500unlikely to cause an out-of-memory situation.  Undo information is completely501in memory, you can reduce that with these options:502- 'undolevels'  Set to a low value, or to -1 to disable undo completely.  This503  helps for a change that affects all lines.504- 'undoreload' Set to zero to disable.505 506							*E339*507  Pattern too long ~508 509This happens on systems with 16 bit ints: The compiled regexp pattern is510longer than about 65000 characters.  Try using a shorter pattern.511It also happens when the offset of a rule doesn't fit in the space available.512Try simplifying the pattern.513 514							*E45*515  'readonly' option is set (add ! to override) ~516 517You are trying to write a file that was marked as read-only.  To write the518file anyway, either reset the 'readonly' option, or add a '!' character just519after the command you used.  Example: >520	:w521changes to: >522	:w!523<524							*E294* *E295* *E301*525  Read error in swap file ~526  Seek error in swap file read ~527  Oops, lost the swap file!!! ~528 529Vim tried to read text from the |swap-file|, but something went wrong.  The530text in the related buffer may now be corrupted!  Check carefully before you531write a buffer.  You may want to write it in another file and check for532differences.533 534							*E192*535  Recursive use of :normal too deep ~536 537You are using a ":normal" command, whose argument again uses a ":normal"538command in a recursive way.  This is restricted to 'maxmapdepth' levels.  This539example illustrates how to get this message: >540	:map gq :normal gq<CR>541If you type "gq", it will execute this mapping, which will call "gq" again.542 543							*E22*544  Scripts nested too deep ~545 546Scripts can be read with the "-s" command-line argument and with the547`:source!` command.  The script can then again read another script.  This can548continue for about 14 levels.  When more nesting is done, Vim assumes that549there is a recursive loop and stops with this error message.550 551							*E319*552  Sorry, the command is not available in this version ~553 554You have used a command that is not present in the version of Vim you are555using.  When compiling Vim, many different features can be enabled or556disabled.  This depends on how big Vim has chosen to be and the operating557system.  See |+feature-list| for when which feature is available.  The558|:version| command shows which feature Vim was compiled with.559 560							*E300*561  Swap file already exists (symlink attack?) ~562 563This message appears when Vim is trying to open a swap file and finds it564already exists or finds a symbolic link in its place.  This shouldn't happen,565because Vim already checked that the file doesn't exist.  Either someone else566opened the same file at exactly the same moment (very unlikely) or someone is567attempting a symlink attack (could happen when editing a file in /tmp or when568'directory' starts with "/tmp", which is a bad choice).569 570							*E432*571  Tags file not sorted: {file name} ~572 573Vim (and Vi) expect tags files to be sorted in ASCII order.  Binary searching574can then be used, which is a lot faster than a linear search.  If your tags575files are not properly sorted, reset the 'tagbsearch' option.576This message is only given when Vim detects a problem when searching for a577tag.  Sometimes this message is not given, even though the tags file is not578properly sorted.579 580							*E424*581  Too many different highlighting attributes in use ~582 583Vim can only handle about 223 different kinds of highlighting.  If you run584into this limit, you have used too many |:highlight| commands with different585arguments.  A ":highlight link" is not counted.586 587							*E77*588  Too many file names ~589 590When expanding file names, more than one match was found.  Only one match is591allowed for the command that was used.592 593							*E303*594  Unable to open swap file for "{filename}", recovery impossible ~595 596Vim was not able to create a swap file.  You can still edit the file, but if597Vim unexpectedly exits the changes will be lost.  And Vim may consume a lot of598memory when editing a big file.  You may want to change the 'directory' option599to avoid this error.  This error is not given when 'directory' is empty.  See600|swap-file|.601 602							*E140*603  Use ! to write partial buffer ~604 605When using a range to write part of a buffer, it is unusual to overwrite the606original file.  It is probably a mistake (e.g., when Visual mode was active607when using ":w"), therefore Vim requires using a !  after the command, e.g.:608":3,10w!".609 610 611  Warning: Cannot convert string "<Key>Escape,_Key_Cancel" to type ~612  VirtualBinding ~613 614Messages like this appear when starting up.  This is not a Vim problem, your615X11 configuration is wrong.  You can find a hint on how to solve this here:616http://groups.yahoo.com/group/solarisonintel/message/12179.617[this URL is no longer valid]618 619							*W10*620  Warning: Changing a readonly file ~621 622The file is read-only and you are making a change to it anyway.  You can use623the |FileChangedRO| autocommand event to avoid this message (the autocommand624must reset the 'readonly' option).  See 'modifiable' to completely disallow625making changes to a file.626This message is only given for the first change after 'readonly' has been set.627 628							*W13*629  Warning: File "{filename}" has been created after editing started ~630 631You are editing a file in Vim when it didn't exist, but it does exist now.632You will have to decide if you want to keep the version in Vim or the newly633created file.  This message is not given when 'buftype' is not empty.634 635							*W11*636  Warning: File "{filename}" has changed since editing started ~637 638The file which you have started editing has got another timestamp and the639contents changed (more precisely: When reading the file again with the current640option settings and autocommands you would end up with different text).  This641probably means that some other program changed the file.  You will have to642find out what happened, and decide which version of the file you want to keep.643Set the 'autoread' option if you want to do this automatically.644This message is not given when 'buftype' is not empty.645Also see the |FileChangedShell| autocommand.646 647You will be given a dialog with the following options:648 649"OK":		Dismiss the warning and continue editing.  No changes are650		loaded, the buffer remains as it is.651 652"Load File":	Reload the file from disk, replacing the current buffer653		contents.  Any changes you made in Vim that haven't been saved654		will be lost.655 656"Load File and Options":657		Reload the file from disk and, in addition, apply relevant658		file settings, such as indentation, syntax highlighting, text659		width, and other filetype-specific options.  This ensures the660		buffer matches the file's intended configuration according to661		your current settings and autocommands.662 663There is one situation where you get this message even though there is nothing664wrong: If you save a file in Windows on the day the daylight saving time665starts.  It can be fixed in one of these ways:666- Add this line in your autoexec.bat: >667	   SET TZ=-1668< Adjust the "-1" for your time zone.669- Disable "automatically adjust clock for daylight saving changes".670- Just write the file again the next day.  Or set your clock to the next day,671  write the file twice and set the clock back.672 673If you get W11 all the time, you may need to disable "Acronis Active674Protection" or register Vim as a trusted service/application.675 676							*W12*677  Warning: File "{filename}" has changed and the buffer was changed in Vim as well ~678 679Like the above, and the buffer for the file was changed in this Vim as well.680You will have to decide if you want to keep the version in this Vim or the one681on disk.  This message is not given when 'buftype' is not empty.682 683							*W16*684  Warning: Mode of file "{filename}" has changed since editing started ~685 686When the timestamp for a buffer was changed and the contents are still the687same but the mode (permissions) have changed.  This usually occurs when688checking out a file from a version control system, which causes the read-only689bit to be reset.  It should be safe to reload the file.  Set 'autoread' to690automatically reload the file.691 692							*E211*693  File "{filename}" no longer available ~694 695The file which you have started editing has disappeared, or is no longer696accessible.  Make sure you write the buffer somewhere to avoid losing697changes.  This message is not given when 'buftype' is not empty.698 699							*W14*700  Warning: List of file names overflow ~701 702You must be using an awful lot of buffers.  It's now possible that two buffers703have the same number, which causes various problems.  You might want to exit704Vim and restart it.705 706							*E931*707  Buffer cannot be registered ~708 709Out of memory or a duplicate buffer number.  May happen after W14.  Looking up710a buffer will not always work, better restart Vim.711 712							*E296* *E297*713  Seek error in swap file write ~714  Write error in swap file ~715 716This mostly happens when the disk is full.  Vim could not write text into the717|swap-file|.  It's not directly harmful, but when Vim unexpectedly exits some718text may be lost without recovery being possible.  Vim might run out of memory719when this problem persists.720 721						*connection-refused*722  Xlib: connection to "<machine-name:0.0" refused by server ~723 724This happens when Vim tries to connect to the X server, but the X server does725not allow a connection.  The connection to the X server is needed to be able726to restore the title and for the xterm clipboard support.  Unfortunately this727error message cannot be avoided, except by disabling the |+xterm_clipboard|728and |+X11| features.729 730							*E10*731  \\ should be followed by /, ? or & ~732 733A command line started with a backslash or the range of a command contained a734backslash in a wrong place.  This is often caused by command-line continuation735being disabled.  Remove the 'C' flag from the 'cpoptions' option to enable it.736Or use ":set nocp".737 738							*E471*739  Argument required ~740 741This happens when an Ex command with mandatory argument(s) was executed, but742no argument has been specified.743 744							*E474* *E475* *E983*745  Invalid argument ~746  Invalid argument: {arg} ~747  Duplicate argument: {arg} ~748 749An Ex command or function has been executed, but an invalid argument has been750specified.751 752							*E488*753  Trailing characters ~754  Trailing characters: {text} ~755 756An argument has been added to an Ex command that does not permit one.757Or the argument has invalid characters and has not been recognized.758 759							*E477* *E478*760  No ! allowed ~761  Don't panic! ~762 763You have added a "!" after an Ex command that doesn't permit one.764 765							*E481*766  No range allowed ~767 768A range was specified for an Ex command that doesn't permit one.  See769|cmdline-ranges|.770 771							*E482* *E483*772  Can't create file {filename} ~773  Can't get temp file name ~774 775Vim cannot create a temporary file.776 777							*E484* *E485*778  Can't open file {filename} ~779  Can't read file {filename} ~780 781Vim cannot read a temporary file.  Especially on Windows, this can be caused782by wrong escaping of special characters for cmd.exe; the approach was783changed with patch 7.3.443.  Try using |shellescape()| for all shell arguments784given to |system()|, or explicitly add escaping with ^.  Also see785'shellxquote' and 'shellxescape'.786 787							*E464*788  Ambiguous use of user-defined command ~789 790There are two user-defined commands with a common name prefix, and you used791Command-line completion to execute one of them. |user-cmd-ambiguous|792Example: >793	:command MyCommand1 echo "one"794	:command MyCommand2 echo "two"795	:MyCommand796<797							*E492*798  Not an editor command ~799 800You tried to execute a command that is neither an Ex command nor801a user-defined command.802 803							*E943*804  Command table needs to be updated, run 'make cmdidxs' ~805 806This can only happen when changing the source code, when adding a command in807src/ex_cmds.h.  The lookup table then needs to be updated, by running: >808	make cmdidxs809<810						*E928* *E889*811  E928: String required ~812  E889: Number required ~813 814These happen when a value or expression is used that does not have the815expected type.816 817==============================================================================8183. Messages						*messages*819 820This is an (incomplete) overview of various messages that Vim gives:821 822			*hit-enter* *press-enter* *hit-return*823			*press-return* *hit-enter-prompt*824 825  Press ENTER or type command to continue ~826 827This message is given when there is something on the screen for you to read,828and the screen is about to be redrawn:829- After executing an external command (e.g., ":!ls" and "=").830- Something is displayed on the status line that is longer than the width of831  the window, or runs into the 'showcmd' or 'ruler' output.832 833-> Press <Enter> or <Space> to redraw the screen and continue, without that834   key being used otherwise.835-> Press ':' or any other Normal mode command character to start that command.836   Note that after an external command some special keys, such as the cursor837   keys, may not work normally, because the terminal is still set to a state838   for executing the external command.839-> Press 'k', <Up>, 'u', 'b' or 'g' to scroll back in the messages.  This840   works the same way as at the |more-prompt|.  Only works when 'compatible'841   is off and 'more' is on.842-> Pressing 'j', 'f', 'd' or <Down> is ignored when messages scrolled off the843   top of the screen, 'compatible' is off and 'more' is on, to avoid that844   typing one 'j' or 'f' too many causes the messages to disappear.845-> Press <C-Y> to copy (yank) a modeless selection to the clipboard register.846-> Use a menu.  The characters defined for Cmdline-mode are used.847-> When 'mouse' contains the 'r' flag, clicking the left mouse button works848   like pressing <Space>.  This makes it impossible to select text though.849-> For the GUI clicking the left mouse button in the last line works like850   pressing <Space>.851-> |q| won't start recording into a register (rationale: it is often used as852   "quit" prompt key by users)853 854If you accidentally hit <Enter> or <Space> and you want to see the displayed855text then use |g<|.  This only works when 'more' is set.856 857To reduce the number of hit-enter prompts:858- Set 'messagesopt'.859- Set 'cmdheight' to 2 or higher.860- Add flags to 'shortmess'.861- Reset 'showcmd' and/or 'ruler'.862- Make sure `:echo` text is shorter than or equal to |v:echospace| screen863  cells.864 865If your script causes the hit-enter prompt and you don't know why, you may866find the |v:scrollstart| variable useful.867 868Also see 'mouse'.  The hit-enter message is highlighted with the |hl-Question|869group.870 871 872						*more-prompt* *pager*873  -- More -- ~874  -- More -- SPACE/d/j: screen/page/line down, b/u/k: up, q: quit ~875 876This message is given when the screen is filled with messages.  It is only877given when the 'more' option is on.  It is highlighted with the |hl-MoreMsg|878group.879 880Type						effect ~881     <CR> or <NL> or j or <Down>		one more line882     d						down a page (half a screen)883     <Space> or f or <PageDown> or CTRL-F	down a screen884     G						down all the way, until the885						hit-enter prompt886 887     <BS> or k or <Up>				one line back888     u						up a page (half a screen)889     b or <PageUp> or CTRL-B			back a screen890     g						back to the start891 892     q, <Esc> or CTRL-C				stop the listing893     :						stop the listing and enter a894						command-line895    <C-Y>					yank (copy) a modeless896						selection to the clipboard897						("* and "+ registers)898    {menu-entry}				what the menu is defined to899						in Cmdline-mode.900    <LeftMouse>					next page (*)901 902Any other key causes the meaning of the keys to be displayed.903 904(*) Clicking the left mouse button only works:905     - For the GUI: in the last line of the screen.906     - When 'r' is included in 'mouse' (but then selecting text won't work).907 908 909Note: The typed key is directly obtained from the terminal, it is not mapped910and typeahead is ignored.911 912The |g<| command can be used to see the last page of previous command output.913This is especially useful if you accidentally typed <Space> at the hit-enter914prompt.915 916 vim:tw=78:ts=8:noet:ft=help:norl:917