Lines Matching refs:command
25 Also repeat a yank command, when the 'y' flag is
27 command-line command.
29 Simple changes can be repeated with the "." command. Without a count, the
37 Note that when repeating a command that used a Visual selection, the same SIZE
41 @: Repeat last command-line [count] times.
51 Execute the Ex command [cmd] (default ":p") on the
55 Execute the Ex command [cmd] (default ":p") on the
81 was in that line. For ":v" and ":g!" the command is executed for each not
84 the command. If an error message is given for a line, the command for that
85 line is aborted and the global command continues with the next marked or
88 When the command is used recursively, it only works on one line. Giving a
95 To execute a non-Ex command, you can use the `:normal` command: >
97 Make sure that {commands} ends with a whole command, otherwise Vim will wait
98 for you to type the rest of the command for each match. The screen will not
101 The undo/redo command will undo/redo the whole global command at once.
103 where the cursor was before the global command).
105 The global command sets both the last used search pattern and the last used
114 command. This will move to a matching line, go to Normal mode to let you
124 (uppercase to append). The 'q' command is disabled
160 command. First set cursor at line [addr] (default is
166 Ex command.
184 :[addr]@: Repeat last command-line. First set cursor at line
205 |:bufdo|, in a loop or when another command follows
243 starting up. This similar command: >
275 on" command in your .vimrc file), this will also look
304 after loading your .vimrc file. With this command it
309 When the optional ! is added this command will load
371 Must be the first command in the file.
375 See |:vim9cmd| for executing one command with Vim9
389 is not present, the command fails.
401 All commands and command sequences can be repeated by putting them in a named
404 - Use the record command "q". You type the commands once, and while they are
407 file, edit the command sequence, and then delete it into the register
410 - Delete or yank the command sequence into the register.
412 Often used command sequences can be put under a function key with the ':map'
413 command.
416 ':source!' command. Useful for long command sequences. Can be combined with
417 the ':map' command to put complicated commands under a function key.
419 The ':source' command reads Ex commands from a file line by line. You will
420 have to type any needed keyboard input. The ':source!' command reads from a
424 Example: When you give the ":!ls" command you get the |hit-enter| prompt. If
431 make a top-down hierarchy of script files. The ':source' command can be
433 15). The ':source!' command can be nested up to 15 levels deep.
439 it from your ".vimrc" file with this command: >
473 Long lines in a ":source"d Ex command script file can be split by inserting
489 inserted freely; it depends on the position where a command is split up
503 command: >
625 To load an optional plugin from a pack use the `:packadd` command: >
633 You can also load an optional plugin at startup, by putting this command in
682 start/foobar/autoload/foo.vim " loaded when foo command used
686 opt/fooextra/autoload/extra.vim " loaded when extra command used
702 You could add this packadd command in one of your plugins, to be executed when
705 Run the `:helptags` command to generate the doc/tags file. Including this
707 pack directory and the help command works right away. Don't forget to re-run
708 the command after changing the plugin help: >
755 ":gui" command in the vimrc file.
757 2. Run a command with ":debug" prepended. Debugging will only be done while
758 this command executes. Useful for debugging a specific script or user
763 the command line: >
768 In debugging mode every executed command is displayed before it is executed.
770 a line contains two commands, separated by "|", each command will be displayed
793 There is a separate command-line history for debug mode.
808 next Execute the command and come back to debug mode when
812 step Execute the command and come back to debug mode for
813 the next command. This steps into called user
817 back to debug mode for the next command that is
822 back to debug mode for the command after the one that
839 - There is no command-line completion for them, you get the completion for the
841 - You can shorten them, up to a single character, unless more than one command
843 - Hitting <CR> will repeat the previous one. When doing another command, this
845 - When you want to use the Ex command with the same name, prepend a colon:
853 When executing a command that is not a specific bytecode instruction but
854 executed like a normal Ex command, "step" will stop once in the compiled
856 executing the command.
870 no way to see the command at the current line yet.
959 command. "explorer", "*explorer.vim" and "*explorer*" are different.
1009 external command). Does not nest.
1026 after this command. A :profile command in the script itself
1035 You must always start with a ":profile start fname" command. The resulting
1068 "for" command in line 7 is executed one more time as the following lines.