Lines Matching refs:command
18 The ":messages" command can be used to view previously given messages. This
36 The "g<" command can be used to see the last page of previous command output.
42 The previous command output is cleared when another command produces output.
133 This happens when an Ex command executes an Ex command that executes an Ex
134 command, etc. The limit is 200 or the value of 'maxfuncdepth', whatever is
136 |:execute| or |:source| command is involved.
220 command is still executed in the wrong directory.
228 On MS-Windows, this message appears when the output of an external command was
229 to be read, but the command didn't run successfully. This can be caused by
231 related options. It might also be that the external command was not found,
244 A mapping resulted in a very long command string. Could be caused by a
307 write anyway, use the same command, but add a "!" just after the command.
321 - If you want to write anyway prepend ":silent!" to the command. For example: >
323 < The special command is needed, since you already added the ! for overwriting
410 used pattern in a ":substitute" command. This fails when no such command has
423 You have used an ":unabbreviate" command with an argument which is not an
424 existing abbreviation. All variations of this command give the same message:
436 You have used an ":unmap" command with an argument which is not an existing
437 mapping. All variations of this command give the same message: ":cunmap",
450 adding a '!' character just after the command you used. Example: >
459 will either have to write the changed buffer (with |:w|), or use a command to
467 This appears when executing a shell command while at least one buffer was
511 after the command you used. Example: >
529 You are using a ":normal" command, whose argument again uses a ":normal"
530 command in a recursive way. This is restricted to 'maxmapdepth' levels. This
538 Scripts can be read with the "-s" command-line argument and with the ":source"
539 command. The script can then again read another script. This can continue
544 Sorry, the command is not available in this version
546 You have used a command that is not present in the version of Vim you are
550 |:version| command shows which feature Vim was compiled with.
583 allowed for the command that was used.
599 when using ":w"), therefore Vim requires using a ! after the command, e.g.:
708 A command line started with a backslash or the range of a command contained a
709 backslash in a wrong place. This is often caused by command-line continuation
716 This happens when an Ex command with mandatory argument(s) was executed, but
724 An Ex command or function has been executed, but an invalid argument has been
730 An argument has been added to an Ex command that does not permit one.
736 You have added a "!" after an Ex command that doesn't permit one.
741 A range was specified for an Ex command that doesn't permit one. See
761 Ambiguous use of user-defined command
766 :command MyCommand1 echo "one"
767 :command MyCommand2 echo "two"
771 Not an editor command
773 You tried to execute a command that is neither an Ex command nor
774 a user-defined command.
779 This can only happen when changing the source code, when adding a command in
799 Press ENTER or type command to continue
803 - After executing an external command (e.g., ":!ls" and "=").
809 -> Press ':' or any other Normal mode command character to start that command.
810 Note that after an external command some special keys, such as the cursor
812 for executing the external command.
865 command-line
882 The |g<| command can be used to see the last page of previous command output.