Vim Error Messages and General Messages

but when Vim unexpectedly exits some text may be lost without recovery being possible. Vim might run out of memory when this problem persists. *E10* > \\ should be followed by /, ? or & A command line started with a backslash or the range of a command contained a backslash in a wrong place. This is often caused by command-line continuation being disabled. Remove the 'C' flag from the 'cpoptions' option to enable it. *E471* > Argument required Ex command was executed without a mandatory argument(s). *E474* *E475* *E983* > Invalid argument Invalid argument: {arg} Duplicate argument: {arg} Ex command or function was given an invalid argument. Or |jobstart()| or |system()| was given a non-executable command. *E488* > Trailing characters Trailing characters: {text} An argument was given to an Ex command that does not permit one. Or the argument has invalid characters and has not been recognized. *E477* *E478* > No ! allowed Don't panic! You have added a "!" after an Ex command that doesn't permit one. *E481* > No range allowed A range was specified for an Ex command that doesn't permit one. See |cmdline-ranges|. *E482* *E483* > Can't create file {filename} Can't get temp file name Vim cannot create a temporary file. *E484* *E485* > Can't open file {filename} Can't read file {filename} Vim cannot read a temporary file. Especially on Windows, this can be caused by wrong escaping of special characters for cmd.exe; the approach was changed with patch 7.3.443. Try using |shellescape()| for all shell arguments given to |system()|, or explicitly add escaping with ^. Also see 'shellxquote' and 'shellxescape'. *E464* > Ambiguous use of user-defined command There are two user-defined commands with a common name prefix, and you used Command-line completion to execute one of them. |user-cmd-ambiguous| Example: > :command MyCommand1 echo "one" :command MyCommand2 echo "two" :MyCommand < *E492* > Not an editor command You tried to execute a command that is neither an Ex command nor a user-defined command. *E905* > Cannot set this option after startup You tried to set an option after startup that only allows changes during startup. *E943* > Command table needs to be updated, run 'make' This can only happen when changing the source code, after adding a command in src/ex_cmds.lua. Update the lookup table by re-running the build. > ============================================================================== 3. Messages *messages* This is an (incomplete) overview of various messages that Vim gives: *hit-enter* *press-enter* *hit-return* *press-return* *hit-enter-prompt* > Press ENTER or type command to continue This message is given when there is something on the screen for you to read, and the screen is about to be redrawn: - After executing an external command (e.g., ":!ls" and "="). - Something is displayed on the status line that is longer than the width of the window, or runs into the 'showcmd' or 'ruler' output. -> Press

This section details various Vim error and informational messages. Error messages covered include swap file writing errors, backslash usage, missing or invalid arguments, trailing characters in commands, incorrect '!' usage, disallowed ranges, inability to create or open files, ambiguous user-defined commands, invalid commands, and attempting to set restricted options after startup. Additionally, it explains the "Press ENTER or type command to continue" prompt and conditions that trigger it.