Mercurial > vim
annotate runtime/doc/cmdline.txt @ 17781:04245f071792 v8.1.1887
patch 8.1.1887: the +cmdline_compl feature is not in the tiny version
commit https://github.com/vim/vim/commit/0a52df50a0e8fce6f5e0eb5f5373dcd0fa24d83a
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Aug 18 22:26:31 2019 +0200
patch 8.1.1887: the +cmdline_compl feature is not in the tiny version
Problem: The +cmdline_compl feature is not in the tiny version.
Solution: Graduate the +cmdline_compl feature.
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Sun, 18 Aug 2019 22:30:04 +0200 |
| parents | 95c23e180022 |
| children | 834b7854aa3c |
| rev | line source |
|---|---|
|
17781
04245f071792
patch 8.1.1887: the +cmdline_compl feature is not in the tiny version
Bram Moolenaar <Bram@vim.org>
parents:
17667
diff
changeset
|
1 *cmdline.txt* For Vim version 8.1. Last change: 2019 Aug 18 |
| 7 | 2 |
| 3 | |
| 4 VIM REFERENCE MANUAL by Bram Moolenaar | |
| 5 | |
| 6 | |
| 7 *Cmdline-mode* *Command-line-mode* | |
| 8 Command-line mode *Cmdline* *Command-line* *mode-cmdline* *:* | |
| 9 | |
| 10 Command-line mode is used to enter Ex commands (":"), search patterns | |
| 11 ("/" and "?"), and filter commands ("!"). | |
| 12 | |
| 13 Basic command line editing is explained in chapter 20 of the user manual | |
| 14 |usr_20.txt|. | |
| 15 | |
| 16 1. Command-line editing |cmdline-editing| | |
| 17 2. Command-line completion |cmdline-completion| | |
| 18 3. Ex command-lines |cmdline-lines| | |
| 19 4. Ex command-line ranges |cmdline-ranges| | |
| 167 | 20 5. Ex command-line flags |ex-flags| |
| 21 6. Ex special characters |cmdline-special| | |
| 22 7. Command-line window |cmdline-window| | |
| 7 | 23 |
| 24 ============================================================================== | |
| 25 1. Command-line editing *cmdline-editing* | |
| 26 | |
| 27 Normally characters are inserted in front of the cursor position. You can | |
| 28 move around in the command-line with the left and right cursor keys. With the | |
| 29 <Insert> key, you can toggle between inserting and overstriking characters. | |
| 30 | |
| 31 Note that if your keyboard does not have working cursor keys or any of the | |
| 32 other special keys, you can use ":cnoremap" to define another key for them. | |
| 33 For example, to define tcsh style editing keys: *tcsh-style* > | |
| 34 :cnoremap <C-A> <Home> | |
| 35 :cnoremap <C-F> <Right> | |
| 36 :cnoremap <C-B> <Left> | |
| 37 :cnoremap <Esc>b <S-Left> | |
| 38 :cnoremap <Esc>f <S-Right> | |
| 39 (<> notation |<>|; type all this literally) | |
| 40 | |
| 41 *cmdline-too-long* | |
| 42 When the command line is getting longer than what fits on the screen, only the | |
| 43 part that fits will be shown. The cursor can only move in this visible part, | |
| 44 thus you cannot edit beyond that. | |
| 45 | |
| 46 *cmdline-history* *history* | |
| 47 The command-lines that you enter are remembered in a history table. You can | |
| 12 | 48 recall them with the up and down cursor keys. There are actually five |
| 7 | 49 history tables: |
| 50 - one for ':' commands | |
| 51 - one for search strings | |
| 52 - one for expressions | |
| 53 - one for input lines, typed for the |input()| function. | |
| 12 | 54 - one for debug mode commands |
| 7 | 55 These are completely separate. Each history can only be accessed when |
| 56 entering the same type of line. | |
| 57 Use the 'history' option to set the number of lines that are remembered | |
| 6213 | 58 (default: 50). |
| 7 | 59 Notes: |
| 60 - When you enter a command-line that is exactly the same as an older one, the | |
| 61 old one is removed (to avoid repeated commands moving older commands out of | |
| 62 the history). | |
| 63 - Only commands that are typed are remembered. Ones that completely come from | |
| 1620 | 64 mappings are not put in the history. |
| 7 | 65 - All searches are put in the search history, including the ones that come |
| 66 from commands like "*" and "#". But for a mapping, only the last search is | |
| 67 remembered (to avoid that long mappings trash the history). | |
| 68 {not available when compiled without the |+cmdline_hist| feature} | |
| 69 | |
| 70 There is an automatic completion of names on the command-line; see | |
| 71 |cmdline-completion|. | |
| 72 | |
| 73 *c_CTRL-V* | |
| 74 CTRL-V Insert next non-digit literally. Up to three digits form the | |
| 75 decimal value of a single byte. The non-digit and the three | |
| 76 digits are not considered for mapping. This works the same | |
| 77 way as in Insert mode (see above, |i_CTRL-V|). | |
| 78 Note: Under Windows CTRL-V is often mapped to paste text. | |
| 79 Use CTRL-Q instead then. | |
| 80 *c_CTRL-Q* | |
| 81 CTRL-Q Same as CTRL-V. But with some terminals it is used for | |
| 82 control flow, it doesn't work then. | |
| 83 | |
| 2751 | 84 *c_<Left>* *c_Left* |
| 7 | 85 <Left> cursor left |
| 2751 | 86 *c_<Right>* *c_Right* |
| 7 | 87 <Right> cursor right |
| 88 *c_<S-Left>* | |
| 89 <S-Left> or <C-Left> *c_<C-Left>* | |
| 90 cursor one WORD left | |
| 91 *c_<S-Right>* | |
| 92 <S-Right> or <C-Right> *c_<C-Right>* | |
| 93 cursor one WORD right | |
| 2751 | 94 CTRL-B or <Home> *c_CTRL-B* *c_<Home>* *c_Home* |
| 7 | 95 cursor to beginning of command-line |
| 2751 | 96 CTRL-E or <End> *c_CTRL-E* *c_<End>* *c_End* |
| 7 | 97 cursor to end of command-line |
| 98 | |
| 99 *c_<LeftMouse>* | |
| 1698 | 100 <LeftMouse> Move the cursor to the position of the mouse click. |
| 7 | 101 |
|
7384
aea5ebf352c4
commit https://github.com/vim/vim/commit/256972a9849b5d575b62a6a71be5b6934b5b0e8b
Christian Brabandt <cb@256bit.org>
parents:
7147
diff
changeset
|
102 *c_<MiddleMouse>* |
|
aea5ebf352c4
commit https://github.com/vim/vim/commit/256972a9849b5d575b62a6a71be5b6934b5b0e8b
Christian Brabandt <cb@256bit.org>
parents:
7147
diff
changeset
|
103 <MiddleMouse> Paste the contents of the clipboard (for X11 the primary |
|
aea5ebf352c4
commit https://github.com/vim/vim/commit/256972a9849b5d575b62a6a71be5b6934b5b0e8b
Christian Brabandt <cb@256bit.org>
parents:
7147
diff
changeset
|
104 selection). This is similar to using CTRL-R *, but no CR |
|
aea5ebf352c4
commit https://github.com/vim/vim/commit/256972a9849b5d575b62a6a71be5b6934b5b0e8b
Christian Brabandt <cb@256bit.org>
parents:
7147
diff
changeset
|
105 characters are inserted between lines. |
|
aea5ebf352c4
commit https://github.com/vim/vim/commit/256972a9849b5d575b62a6a71be5b6934b5b0e8b
Christian Brabandt <cb@256bit.org>
parents:
7147
diff
changeset
|
106 |
| 2751 | 107 CTRL-H *c_<BS>* *c_CTRL-H* *c_BS* |
| 1698 | 108 <BS> Delete the character in front of the cursor (see |:fixdel| if |
| 7 | 109 your <BS> key does not do what you want). |
| 2751 | 110 *c_<Del>* *c_Del* |
| 1698 | 111 <Del> Delete the character under the cursor (at end of line: |
| 7 | 112 character before the cursor) (see |:fixdel| if your <Del> |
| 113 key does not do what you want). | |
| 114 *c_CTRL-W* | |
| 1698 | 115 CTRL-W Delete the |word| before the cursor. This depends on the |
| 116 'iskeyword' option. | |
| 7 | 117 *c_CTRL-U* |
| 1698 | 118 CTRL-U Remove all characters between the cursor position and |
| 7 | 119 the beginning of the line. Previous versions of vim |
| 120 deleted all characters on the line. If that is the | |
| 121 preferred behavior, add the following to your .vimrc: > | |
| 122 :cnoremap <C-U> <C-E><C-U> | |
| 123 < | |
| 2751 | 124 *c_<Insert>* *c_Insert* |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
14999
diff
changeset
|
125 <Insert> Toggle between insert and overstrike. |
| 7 | 126 |
| 127 {char1} <BS> {char2} or *c_digraph* | |
| 128 CTRL-K {char1} {char2} *c_CTRL-K* | |
| 129 enter digraph (see |digraphs|). When {char1} is a special | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
14999
diff
changeset
|
130 key, the code for that key is inserted in <> form. |
| 7 | 131 |
| 132 CTRL-R {0-9a-z"%#:-=.} *c_CTRL-R* *c_<C-R>* | |
| 133 Insert the contents of a numbered or named register. Between | |
| 134 typing CTRL-R and the second character '"' will be displayed | |
| 135 to indicate that you are expected to enter the name of a | |
| 136 register. | |
| 137 The text is inserted as if you typed it, but mappings and | |
| 138 abbreviations are not used. Command-line completion through | |
| 139 'wildchar' is not triggered though. And characters that end | |
| 140 the command line are inserted literally (<Esc>, <CR>, <NL>, | |
| 141 <C-C>). A <BS> or CTRL-W could still end the command line | |
| 142 though, and remaining characters will then be interpreted in | |
| 143 another mode, which might not be what you intended. | |
| 144 Special registers: | |
| 145 '"' the unnamed register, containing the text of | |
| 146 the last delete or yank | |
| 147 '%' the current file name | |
| 148 '#' the alternate file name | |
| 149 '*' the clipboard contents (X11: primary selection) | |
| 150 '+' the clipboard contents | |
| 151 '/' the last search pattern | |
| 152 ':' the last command-line | |
| 153 '-' the last small (less than a line) delete | |
| 154 '.' the last inserted text | |
| 155 *c_CTRL-R_=* | |
| 156 '=' the expression register: you are prompted to | |
| 157 enter an expression (see |expression|) | |
| 631 | 158 (doesn't work at the expression prompt; some |
| 159 things such as changing the buffer or current | |
| 160 window are not allowed to avoid side effects) | |
| 1733 | 161 When the result is a |List| the items are used |
| 162 as lines. They can have line breaks inside | |
| 163 too. | |
| 164 When the result is a Float it's automatically | |
| 165 converted to a String. | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
14999
diff
changeset
|
166 See |registers| about registers. |
| 98 | 167 Implementation detail: When using the |expression| register |
| 168 and invoking setcmdpos(), this sets the position before | |
| 169 inserting the resulting string. Use CTRL-R CTRL-R to set the | |
| 170 position afterwards. | |
| 7 | 171 |
| 172 CTRL-R CTRL-F *c_CTRL-R_CTRL-F* *c_<C-R>_<C-F>* | |
| 173 CTRL-R CTRL-P *c_CTRL-R_CTRL-P* *c_<C-R>_<C-P>* | |
| 174 CTRL-R CTRL-W *c_CTRL-R_CTRL-W* *c_<C-R>_<C-W>* | |
| 175 CTRL-R CTRL-A *c_CTRL-R_CTRL-A* *c_<C-R>_<C-A>* | |
|
13831
1f95ec5de238
patch 8.0.1787: cannot insert the whole cursor line
Christian Brabandt <cb@256bit.org>
parents:
12756
diff
changeset
|
176 CTRL-R CTRL-L *c_CTRL-R_CTRL-L* *c_<C-R>_<C-L>* |
| 7 | 177 Insert the object under the cursor: |
| 178 CTRL-F the Filename under the cursor | |
| 179 CTRL-P the Filename under the cursor, expanded with | |
| 180 'path' as in |gf| | |
| 181 CTRL-W the Word under the cursor | |
| 182 CTRL-A the WORD under the cursor; see |WORD| | |
|
13831
1f95ec5de238
patch 8.0.1787: cannot insert the whole cursor line
Christian Brabandt <cb@256bit.org>
parents:
12756
diff
changeset
|
183 CTRL-L the line under the cursor |
| 771 | 184 |
| 185 When 'incsearch' is set the cursor position at the end of the | |
| 186 currently displayed match is used. With CTRL-W the part of | |
| 187 the word that was already typed is not inserted again. | |
| 188 | |
|
2570
71b56b4e7785
Make the references to features in the help more consistent. (Sylvain Hitier)
Bram Moolenaar <bram@vim.org>
parents:
2561
diff
changeset
|
189 CTRL-F and CTRL-P: {only when |+file_in_path| feature is |
| 7 | 190 included} |
| 191 | |
| 192 *c_CTRL-R_CTRL-R* *c_<C-R>_<C-R>* | |
| 193 *c_CTRL-R_CTRL-O* *c_<C-R>_<C-O>* | |
|
13831
1f95ec5de238
patch 8.0.1787: cannot insert the whole cursor line
Christian Brabandt <cb@256bit.org>
parents:
12756
diff
changeset
|
194 CTRL-R CTRL-R {0-9a-z"%#:-=. CTRL-F CTRL-P CTRL-W CTRL-A CTRL-L} |
|
1f95ec5de238
patch 8.0.1787: cannot insert the whole cursor line
Christian Brabandt <cb@256bit.org>
parents:
12756
diff
changeset
|
195 CTRL-R CTRL-O {0-9a-z"%#:-=. CTRL-F CTRL-P CTRL-W CTRL-A CTRL-L} |
| 7 | 196 Insert register or object under the cursor. Works like |
| 197 |c_CTRL-R| but inserts the text literally. For example, if | |
| 198 register a contains "xy^Hz" (where ^H is a backspace), | |
| 199 "CTRL-R a" will insert "xz" while "CTRL-R CTRL-R a" will | |
| 200 insert "xy^Hz". | |
| 201 | |
| 202 CTRL-\ e {expr} *c_CTRL-\_e* | |
| 203 Evaluate {expr} and replace the whole command line with the | |
| 204 result. You will be prompted for the expression, type <Enter> | |
| 205 to finish it. It's most useful in mappings though. See | |
| 206 |expression|. | |
| 207 See |c_CTRL-R_=| for inserting the result of an expression. | |
| 531 | 208 Useful functions are |getcmdtype()|, |getcmdline()| and |
| 209 |getcmdpos()|. | |
| 7 | 210 The cursor position is unchanged, except when the cursor was |
| 211 at the end of the line, then it stays at the end. | |
| 212 |setcmdpos()| can be used to set the cursor position. | |
| 625 | 213 The |sandbox| is used for evaluating the expression to avoid |
| 214 nasty side effects. | |
| 7 | 215 Example: > |
| 216 :cmap <F7> <C-\>eAppendSome()<CR> | |
| 217 :func AppendSome() | |
| 218 :let cmd = getcmdline() . " Some()" | |
| 219 :" place the cursor on the ) | |
| 220 :call setcmdpos(strlen(cmd)) | |
| 221 :return cmd | |
| 222 :endfunc | |
| 531 | 223 < This doesn't work recursively, thus not when already editing |
| 3893 | 224 an expression. But it is possible to use in a mapping. |
| 531 | 225 |
| 7 | 226 *c_CTRL-Y* |
| 227 CTRL-Y When there is a modeless selection, copy the selection into | |
| 228 the clipboard. |modeless-selection| | |
| 229 If there is no selection CTRL-Y is inserted as a character. | |
| 230 | |
|
10244
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
231 CTRL-M or CTRL-J *c_CTRL-M* *c_CTRL-J* *c_<NL>* *c_<CR>* *c_CR* |
| 7 | 232 <CR> or <NL> start entered command |
|
10244
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
233 |
|
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
234 CTRL-[ *c_CTRL-[* *c_<Esc>* *c_Esc* |
| 7 | 235 <Esc> When typed and 'x' not present in 'cpoptions', quit |
| 236 Command-line mode without executing. In macros or when 'x' | |
| 237 present in 'cpoptions', start entered command. | |
| 1620 | 238 Note: If your <Esc> key is hard to hit on your keyboard, train |
| 239 yourself to use CTRL-[. | |
| 7 | 240 *c_CTRL-C* |
| 241 CTRL-C quit command-line without executing | |
| 242 | |
| 2751 | 243 *c_<Up>* *c_Up* |
| 7 | 244 <Up> recall older command-line from history, whose beginning |
| 245 matches the current command-line (see below). | |
| 246 {not available when compiled without the |+cmdline_hist| | |
| 247 feature} | |
| 2751 | 248 *c_<Down>* *c_Down* |
| 7 | 249 <Down> recall more recent command-line from history, whose beginning |
| 250 matches the current command-line (see below). | |
| 251 {not available when compiled without the |+cmdline_hist| | |
| 252 feature} | |
| 253 | |
| 254 *c_<S-Up>* *c_<PageUp>* | |
| 255 <S-Up> or <PageUp> | |
| 256 recall older command-line from history | |
| 257 {not available when compiled without the |+cmdline_hist| | |
| 258 feature} | |
| 259 *c_<S-Down>* *c_<PageDown>* | |
| 260 <S-Down> or <PageDown> | |
| 261 recall more recent command-line from history | |
| 262 {not available when compiled without the |+cmdline_hist| | |
| 263 feature} | |
| 264 | |
| 265 CTRL-D command-line completion (see |cmdline-completion|) | |
| 266 'wildchar' option | |
| 267 command-line completion (see |cmdline-completion|) | |
| 268 CTRL-N command-line completion (see |cmdline-completion|) | |
| 269 CTRL-P command-line completion (see |cmdline-completion|) | |
| 270 CTRL-A command-line completion (see |cmdline-completion|) | |
| 271 CTRL-L command-line completion (see |cmdline-completion|) | |
| 272 | |
| 273 *c_CTRL-_* | |
| 274 CTRL-_ a - switch between Hebrew and English keyboard mode, which is | |
| 275 private to the command-line and not related to hkmap. | |
| 276 This is useful when Hebrew text entry is required in the | |
| 277 command-line, searches, abbreviations, etc. Applies only if | |
| 278 Vim is compiled with the |+rightleft| feature and the | |
| 279 'allowrevins' option is set. | |
| 280 See |rileft.txt|. | |
| 281 | |
| 282 b - switch between Farsi and English keyboard mode, which is | |
| 283 private to the command-line and not related to fkmap. In | |
| 284 Farsi keyboard mode the characters are inserted in reverse | |
| 285 insert manner. This is useful when Farsi text entry is | |
| 286 required in the command-line, searches, abbreviations, etc. | |
| 287 Applies only if Vim is compiled with the |+farsi| feature. | |
| 288 See |farsi.txt|. | |
| 289 | |
| 290 *c_CTRL-^* | |
| 291 CTRL-^ Toggle the use of language |:lmap| mappings and/or Input | |
| 292 Method. | |
| 293 When typing a pattern for a search command and 'imsearch' is | |
| 294 not -1, VAL is the value of 'imsearch', otherwise VAL is the | |
| 295 value of 'iminsert'. | |
| 296 When language mappings are defined: | |
| 297 - If VAL is 1 (langmap mappings used) it becomes 0 (no langmap | |
| 298 mappings used). | |
| 299 - If VAL was not 1 it becomes 1, thus langmap mappings are | |
| 300 enabled. | |
| 301 When no language mappings are defined: | |
| 302 - If VAL is 2 (Input Method is used) it becomes 0 (no input | |
| 303 method used) | |
| 304 - If VAL has another value it becomes 2, thus the Input Method | |
| 305 is enabled. | |
| 306 These language mappings are normally used to type characters | |
| 307 that are different from what the keyboard produces. The | |
| 308 'keymap' option can be used to install a whole number of them. | |
| 309 When entering a command line, langmap mappings are switched | |
| 310 off, since you are expected to type a command. After | |
| 311 switching it on with CTRL-^, the new state is not used again | |
| 312 for the next command or Search pattern. | |
| 313 | |
| 1121 | 314 *c_CTRL-]* |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
14999
diff
changeset
|
315 CTRL-] Trigger abbreviation, without inserting a character. |
| 1121 | 316 |
| 7 | 317 For Emacs-style editing on the command-line see |emacs-keys|. |
| 318 | |
| 319 The <Up> and <Down> keys take the current command-line as a search string. | |
| 320 The beginning of the next/previous command-lines are compared with this | |
| 321 string. The first line that matches is the new command-line. When typing | |
| 322 these two keys repeatedly, the same string is used again. For example, this | |
| 323 can be used to find the previous substitute command: Type ":s" and then <Up>. | |
| 324 The same could be done by typing <S-Up> a number of times until the desired | |
| 325 command-line is shown. (Note: the shifted arrow keys do not work on all | |
| 326 terminals) | |
| 327 | |
| 1484 | 328 *:his* *:history* |
| 7 | 329 :his[tory] Print the history of last entered commands. |
| 330 {not available when compiled without the |+cmdline_hist| | |
| 331 feature} | |
| 332 | |
| 333 :his[tory] [{name}] [{first}][, [{last}]] | |
| 334 List the contents of history {name} which can be: | |
| 3503 | 335 c[md] or : command-line history |
| 336 s[earch] or / or ? search string history | |
| 337 e[xpr] or = expression register history | |
| 338 i[nput] or @ input line history | |
| 339 d[ebug] or > debug command history | |
| 340 a[ll] all of the above | |
| 7 | 341 |
| 342 If the numbers {first} and/or {last} are given, the respective | |
| 343 range of entries from a history is listed. These numbers can | |
| 344 be specified in the following form: | |
| 345 *:history-indexing* | |
| 346 A positive number represents the absolute index of an entry | |
| 347 as it is given in the first column of a :history listing. | |
| 348 This number remains fixed even if other entries are deleted. | |
| 349 | |
| 350 A negative number means the relative position of an entry, | |
| 351 counted from the newest entry (which has index -1) backwards. | |
| 352 | |
| 353 Examples: | |
| 354 List entries 6 to 12 from the search history: > | |
| 355 :history / 6,12 | |
| 356 < | |
|
10434
f3bb76ec4155
commit https://github.com/vim/vim/commit/eebd84eb94ed7f59a06a52cb4863563642f58899
Christian Brabandt <cb@256bit.org>
parents:
10244
diff
changeset
|
357 List the penultimate entry from all histories: > |
|
f3bb76ec4155
commit https://github.com/vim/vim/commit/eebd84eb94ed7f59a06a52cb4863563642f58899
Christian Brabandt <cb@256bit.org>
parents:
10244
diff
changeset
|
358 :history all -2 |
|
f3bb76ec4155
commit https://github.com/vim/vim/commit/eebd84eb94ed7f59a06a52cb4863563642f58899
Christian Brabandt <cb@256bit.org>
parents:
10244
diff
changeset
|
359 < |
|
f3bb76ec4155
commit https://github.com/vim/vim/commit/eebd84eb94ed7f59a06a52cb4863563642f58899
Christian Brabandt <cb@256bit.org>
parents:
10244
diff
changeset
|
360 List the most recent two entries from all histories: > |
|
f3bb76ec4155
commit https://github.com/vim/vim/commit/eebd84eb94ed7f59a06a52cb4863563642f58899
Christian Brabandt <cb@256bit.org>
parents:
10244
diff
changeset
|
361 :history all -2, |
| 7 | 362 |
| 5467 | 363 :keepp[atterns] {command} *:keepp* *:keeppatterns* |
| 364 Execute {command}, without adding anything to the search | |
| 365 history | |
| 366 | |
| 7 | 367 ============================================================================== |
| 368 2. Command-line completion *cmdline-completion* | |
| 369 | |
| 370 When editing the command-line, a few commands can be used to complete the | |
| 371 word before the cursor. This is available for: | |
| 372 | |
| 373 - Command names: At the start of the command-line. | |
| 374 - Tags: Only after the ":tag" command. | |
| 375 - File names: Only after a command that accepts a file name or a setting for | |
| 376 an option that can be set to a file name. This is called file name | |
| 377 completion. | |
| 715 | 378 - Shell command names: After ":!cmd", ":r !cmd" and ":w !cmd". $PATH is used. |
| 7 | 379 - Options: Only after the ":set" command. |
| 380 - Mappings: Only after a ":map" or similar command. | |
| 381 - Variable and function names: Only after a ":if", ":call" or similar command. | |
| 382 | |
|
17781
04245f071792
patch 8.1.1887: the +cmdline_compl feature is not in the tiny version
Bram Moolenaar <Bram@vim.org>
parents:
17667
diff
changeset
|
383 The number of help item matches is limited (currently to 300) to avoid a long |
|
04245f071792
patch 8.1.1887: the +cmdline_compl feature is not in the tiny version
Bram Moolenaar <Bram@vim.org>
parents:
17667
diff
changeset
|
384 delay when there are very many matches. |
| 7 | 385 |
| 386 These are the commands that can be used: | |
| 387 | |
| 388 *c_CTRL-D* | |
| 389 CTRL-D List names that match the pattern in front of the cursor. | |
| 390 When showing file names, directories are highlighted (see | |
| 391 'highlight' option). Names where 'suffixes' matches are moved | |
| 392 to the end. | |
| 40 | 393 The 'wildoptions' option can be set to "tagfile" to list the |
| 394 file of matching tags. | |
| 7 | 395 *c_CTRL-I* *c_wildchar* *c_<Tab>* |
| 396 'wildchar' option | |
| 397 A match is done on the pattern in front of the cursor. The | |
| 398 match (if there are several, the first match) is inserted | |
| 399 in place of the pattern. (Note: does not work inside a | |
| 400 macro, because <Tab> or <Esc> are mostly used as 'wildchar', | |
| 401 and these have a special meaning in some macros.) When typed | |
| 402 again and there were multiple matches, the next | |
| 403 match is inserted. After the last match, the first is used | |
| 404 again (wrap around). | |
| 405 The behavior can be changed with the 'wildmode' option. | |
| 13912 | 406 *c_<S-Tab>* |
| 407 <S-Tab> Like 'wildchar' or <Tab>, but begin with the last match and | |
| 408 then go to the previous match. | |
| 409 <S-Tab> does not work everywhere. | |
| 7 | 410 *c_CTRL-N* |
| 411 CTRL-N After using 'wildchar' which got multiple matches, go to next | |
| 412 match. Otherwise recall more recent command-line from history. | |
| 13912 | 413 *c_CTRL-P* |
| 7 | 414 CTRL-P After using 'wildchar' which got multiple matches, go to |
| 415 previous match. Otherwise recall older command-line from | |
| 13912 | 416 history. |
| 7 | 417 *c_CTRL-A* |
| 418 CTRL-A All names that match the pattern in front of the cursor are | |
| 419 inserted. | |
| 420 *c_CTRL-L* | |
| 421 CTRL-L A match is done on the pattern in front of the cursor. If | |
| 422 there is one match, it is inserted in place of the pattern. | |
| 423 If there are multiple matches the longest common part is | |
| 424 inserted in place of the pattern. If the result is shorter | |
| 425 than the pattern, no completion is done. | |
|
9971
98b39d2eb895
commit https://github.com/vim/vim/commit/4d6f32cbfbaf324ac4a25c0206a5db0e9f7a48f7
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
426 */_CTRL-L* |
| 771 | 427 When 'incsearch' is set, entering a search pattern for "/" or |
| 428 "?" and the current match is displayed then CTRL-L will add | |
|
2302
488be8cbe19c
Make CTRL-L in command line mode respect 'ignorecase' and 'smartcase'. (Martin
Bram Moolenaar <bram@vim.org>
parents:
2214
diff
changeset
|
429 one character from the end of the current match. If |
|
488be8cbe19c
Make CTRL-L in command line mode respect 'ignorecase' and 'smartcase'. (Martin
Bram Moolenaar <bram@vim.org>
parents:
2214
diff
changeset
|
430 'ignorecase' and 'smartcase' are set and the command line has |
|
488be8cbe19c
Make CTRL-L in command line mode respect 'ignorecase' and 'smartcase'. (Martin
Bram Moolenaar <bram@vim.org>
parents:
2214
diff
changeset
|
431 no uppercase characters, the added character is converted to |
|
488be8cbe19c
Make CTRL-L in command line mode respect 'ignorecase' and 'smartcase'. (Martin
Bram Moolenaar <bram@vim.org>
parents:
2214
diff
changeset
|
432 lowercase. |
|
9990
6a1793d9c895
commit https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
Christian Brabandt <cb@256bit.org>
parents:
9971
diff
changeset
|
433 *c_CTRL-G* */_CTRL-G* |
|
6a1793d9c895
commit https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
Christian Brabandt <cb@256bit.org>
parents:
9971
diff
changeset
|
434 CTRL-G When 'incsearch' is set, entering a search pattern for "/" or |
|
6a1793d9c895
commit https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
Christian Brabandt <cb@256bit.org>
parents:
9971
diff
changeset
|
435 "?" and the current match is displayed then CTRL-G will move |
|
6a1793d9c895
commit https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
Christian Brabandt <cb@256bit.org>
parents:
9971
diff
changeset
|
436 to the next match (does not take |search-offset| into account) |
|
6a1793d9c895
commit https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
Christian Brabandt <cb@256bit.org>
parents:
9971
diff
changeset
|
437 Use CTRL-T to move to the previous match. Hint: on a regular |
|
6a1793d9c895
commit https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
Christian Brabandt <cb@256bit.org>
parents:
9971
diff
changeset
|
438 keyboard T is above G. |
|
6a1793d9c895
commit https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
Christian Brabandt <cb@256bit.org>
parents:
9971
diff
changeset
|
439 *c_CTRL-T* */_CTRL-T* |
|
6a1793d9c895
commit https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
Christian Brabandt <cb@256bit.org>
parents:
9971
diff
changeset
|
440 CTRL-T When 'incsearch' is set, entering a search pattern for "/" or |
|
6a1793d9c895
commit https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
Christian Brabandt <cb@256bit.org>
parents:
9971
diff
changeset
|
441 "?" and the current match is displayed then CTRL-T will move |
|
6a1793d9c895
commit https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
Christian Brabandt <cb@256bit.org>
parents:
9971
diff
changeset
|
442 to the previous match (does not take |search-offset| into |
|
6a1793d9c895
commit https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
Christian Brabandt <cb@256bit.org>
parents:
9971
diff
changeset
|
443 account). |
|
6a1793d9c895
commit https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
Christian Brabandt <cb@256bit.org>
parents:
9971
diff
changeset
|
444 Use CTRL-G to move to the next match. Hint: on a regular |
|
6a1793d9c895
commit https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
Christian Brabandt <cb@256bit.org>
parents:
9971
diff
changeset
|
445 keyboard T is above G. |
| 7 | 446 |
| 447 The 'wildchar' option defaults to <Tab> (CTRL-E when in Vi compatible mode; in | |
| 448 a previous version <Esc> was used). In the pattern standard wildcards '*' and | |
| 2581 | 449 '?' are accepted when matching file names. '*' matches any string, '?' |
| 450 matches exactly one character. | |
| 7 | 451 |
|
13950
741b1feeac9f
patch 8.0.1845: various comment updates needed, missing white space
Christian Brabandt <cb@256bit.org>
parents:
13912
diff
changeset
|
452 When repeating 'wildchar' or CTRL-N you cycle through the matches, eventually |
|
741b1feeac9f
patch 8.0.1845: various comment updates needed, missing white space
Christian Brabandt <cb@256bit.org>
parents:
13912
diff
changeset
|
453 ending up back to what was typed. If the first match is not what you wanted, |
|
741b1feeac9f
patch 8.0.1845: various comment updates needed, missing white space
Christian Brabandt <cb@256bit.org>
parents:
13912
diff
changeset
|
454 you can use <S-Tab> or CTRL-P to go straight back to what you typed. |
|
741b1feeac9f
patch 8.0.1845: various comment updates needed, missing white space
Christian Brabandt <cb@256bit.org>
parents:
13912
diff
changeset
|
455 |
| 3356 | 456 The 'wildignorecase' option can be set to ignore case in filenames. |
| 457 | |
|
11659
49c12c93abf3
Updated runtime files and translations.
Christian Brabandt <cb@256bit.org>
parents:
10498
diff
changeset
|
458 The 'wildmenu' option can be set to show the matches just above the command |
|
49c12c93abf3
Updated runtime files and translations.
Christian Brabandt <cb@256bit.org>
parents:
10498
diff
changeset
|
459 line. |
|
49c12c93abf3
Updated runtime files and translations.
Christian Brabandt <cb@256bit.org>
parents:
10498
diff
changeset
|
460 |
| 7 | 461 If you like tcsh's autolist completion, you can use this mapping: |
| 462 :cnoremap X <C-L><C-D> | |
| 463 (Where X is the command key to use, <C-L> is CTRL-L and <C-D> is CTRL-D) | |
| 464 This will find the longest match and then list all matching files. | |
| 465 | |
| 466 If you like tcsh's autolist completion, you can use the 'wildmode' option to | |
| 467 emulate it. For example, this mimics autolist=ambiguous: | |
| 468 :set wildmode=longest,list | |
| 469 This will find the longest match with the first 'wildchar', then list all | |
| 470 matching files with the next. | |
| 471 | |
| 472 *suffixes* | |
| 473 For file name completion you can use the 'suffixes' option to set a priority | |
| 474 between files with almost the same name. If there are multiple matches, | |
| 475 those files with an extension that is in the 'suffixes' option are ignored. | |
| 476 The default is ".bak,~,.o,.h,.info,.swp,.obj", which means that files ending | |
| 477 in ".bak", "~", ".o", ".h", ".info", ".swp" and ".obj" are sometimes ignored. | |
| 1937 | 478 |
| 479 An empty entry, two consecutive commas, match a file name that does not | |
| 480 contain a ".", thus has no suffix. This is useful to ignore "prog" and prefer | |
| 481 "prog.c". | |
| 482 | |
| 483 Examples: | |
| 7 | 484 |
| 485 pattern: files: match: ~ | |
| 486 test* test.c test.h test.o test.c | |
| 487 test* test.h test.o test.h and test.o | |
| 488 test* test.i test.h test.c test.i and test.c | |
| 489 | |
| 1937 | 490 It is impossible to ignore suffixes with two dots. |
| 491 | |
| 7 | 492 If there is more than one matching file (after ignoring the ones matching |
| 493 the 'suffixes' option) the first file name is inserted. You can see that | |
| 494 there is only one match when you type 'wildchar' twice and the completed | |
| 495 match stays the same. You can get to the other matches by entering | |
| 496 'wildchar', CTRL-N or CTRL-P. All files are included, also the ones with | |
| 497 extensions matching the 'suffixes' option. | |
| 498 | |
| 499 To completely ignore files with some extension use 'wildignore'. | |
| 500 | |
| 1484 | 501 To match only files that end at the end of the typed text append a "$". For |
| 502 example, to match only files that end in ".c": > | |
| 503 :e *.c$ | |
| 504 This will not match a file ending in ".cpp". Without the "$" it does match. | |
| 505 | |
| 7 | 506 The old value of an option can be obtained by hitting 'wildchar' just after |
| 507 the '='. For example, typing 'wildchar' after ":set dir=" will insert the | |
| 508 current value of 'dir'. This overrules file name completion for the options | |
| 509 that take a file name. | |
| 510 | |
| 511 If you would like using <S-Tab> for CTRL-P in an xterm, put this command in | |
| 512 your .cshrc: > | |
| 513 xmodmap -e "keysym Tab = Tab Find" | |
| 514 And this in your .vimrc: > | |
| 515 :cmap <Esc>[1~ <C-P> | |
| 516 | |
| 517 ============================================================================== | |
| 518 3. Ex command-lines *cmdline-lines* | |
| 519 | |
| 520 The Ex commands have a few specialties: | |
| 521 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1937
diff
changeset
|
522 *:quote* *:comment* |
| 7 | 523 '"' at the start of a line causes the whole line to be ignored. '"' |
| 524 after a command causes the rest of the line to be ignored. This can be used | |
| 525 to add comments. Example: > | |
| 526 :set ai "set 'autoindent' option | |
| 527 It is not possible to add a comment to a shell command ":!cmd" or to the | |
| 14945 | 528 ":map" command and a few others (mainly commands that expect expressions) |
| 529 that see the '"' as part of their argument: | |
| 530 | |
| 531 :argdo | |
| 532 :autocmd | |
| 533 :bufdo | |
| 534 :cexpr (and the like) | |
| 535 :cdo (and the like) | |
| 536 :command | |
| 537 :cscope (and the like) | |
| 538 :debug | |
| 539 :display | |
| 540 :echo (and the like) | |
| 541 :elseif | |
| 542 :execute | |
| 543 :folddoopen | |
| 544 :folddoclosed | |
| 545 :for | |
| 546 :grep (and the like) | |
| 547 :help (and the like) | |
| 548 :if | |
| 549 :let | |
| 550 :make | |
| 551 :map (and the like including :abbrev commands) | |
| 552 :menu (and the like) | |
| 553 :mkspell | |
| 554 :normal | |
| 555 :ownsyntax | |
| 556 :popup | |
| 557 :promptfind (and the like) | |
| 558 :registers | |
| 559 :return | |
| 560 :sort | |
| 561 :syntax | |
| 562 :tabdo | |
| 563 :tearoff | |
| 564 :vimgrep (and the like) | |
| 565 :while | |
| 566 :windo | |
| 7 | 567 |
| 568 *:bar* *:\bar* | |
| 569 '|' can be used to separate commands, so you can give multiple commands in one | |
| 570 line. If you want to use '|' in an argument, precede it with '\'. | |
| 571 | |
| 572 These commands see the '|' as their argument, and can therefore not be | |
| 1620 | 573 followed by another Vim command: |
| 7 | 574 :argdo |
| 575 :autocmd | |
| 576 :bufdo | |
|
7092
64e30831fa42
commit https://github.com/vim/vim/commit/aa23b379421aa214e6543b06c974594a25799b09
Christian Brabandt <cb@256bit.org>
parents:
7013
diff
changeset
|
577 :cdo |
|
64e30831fa42
commit https://github.com/vim/vim/commit/aa23b379421aa214e6543b06c974594a25799b09
Christian Brabandt <cb@256bit.org>
parents:
7013
diff
changeset
|
578 :cfdo |
| 7 | 579 :command |
| 580 :cscope | |
| 581 :debug | |
| 582 :folddoopen | |
| 583 :folddoclosed | |
| 584 :function | |
| 585 :global | |
| 586 :help | |
| 587 :helpfind | |
| 664 | 588 :lcscope |
|
7092
64e30831fa42
commit https://github.com/vim/vim/commit/aa23b379421aa214e6543b06c974594a25799b09
Christian Brabandt <cb@256bit.org>
parents:
7013
diff
changeset
|
589 :ldo |
|
64e30831fa42
commit https://github.com/vim/vim/commit/aa23b379421aa214e6543b06c974594a25799b09
Christian Brabandt <cb@256bit.org>
parents:
7013
diff
changeset
|
590 :lfdo |
| 7 | 591 :make |
| 592 :normal | |
| 593 :perl | |
| 594 :perldo | |
| 595 :promptfind | |
| 596 :promptrepl | |
| 597 :pyfile | |
| 598 :python | |
| 599 :registers | |
| 600 :read ! | |
| 601 :scscope | |
| 2152 | 602 :sign |
| 7 | 603 :tcl |
| 604 :tcldo | |
| 605 :tclfile | |
| 606 :vglobal | |
| 607 :windo | |
| 608 :write ! | |
| 609 :[range]! | |
| 610 a user defined command without the "-bar" argument |:command| | |
| 611 | |
| 612 Note that this is confusing (inherited from Vi): With ":g" the '|' is included | |
| 613 in the command, with ":s" it is not. | |
| 614 | |
| 615 To be able to use another command anyway, use the ":execute" command. | |
| 616 Example (append the output of "ls" and jump to the first line): > | |
| 617 :execute 'r !ls' | '[ | |
| 618 | |
| 619 There is one exception: When the 'b' flag is present in 'cpoptions', with the | |
| 620 ":map" and ":abbr" commands and friends CTRL-V needs to be used instead of | |
| 621 '\'. You can also use "<Bar>" instead. See also |map_bar|. | |
| 622 | |
| 623 Examples: > | |
| 624 :!ls | wc view the output of two commands | |
| 625 :r !ls | wc insert the same output in the text | |
| 626 :%g/foo/p|> moves all matching lines one shiftwidth | |
| 627 :%s/foo/bar/|> moves one line one shiftwidth | |
| 628 :map q 10^V| map "q" to "10|" | |
| 629 :map q 10\| map \ l map "q" to "10\" and map "\" to "l" | |
| 630 (when 'b' is present in 'cpoptions') | |
| 631 | |
| 632 You can also use <NL> to separate commands in the same way as with '|'. To | |
| 633 insert a <NL> use CTRL-V CTRL-J. "^@" will be shown. Using '|' is the | |
| 634 preferred method. But for external commands a <NL> must be used, because a | |
| 635 '|' is included in the external command. To avoid the special meaning of <NL> | |
| 636 it must be preceded with a backslash. Example: > | |
| 637 :r !date<NL>-join | |
| 638 This reads the current date into the file and joins it with the previous line. | |
| 639 | |
| 640 Note that when the command before the '|' generates an error, the following | |
| 641 commands will not be executed. | |
| 642 | |
| 643 | |
| 644 Because of Vi compatibility the following strange commands are supported: > | |
| 645 :| print current line (like ":p") | |
| 646 :3| print line 3 (like ":3p") | |
| 647 :3 goto line 3 | |
| 648 | |
| 649 A colon is allowed between the range and the command name. It is ignored | |
| 650 (this is Vi compatible). For example: > | |
| 651 :1,$:s/pat/string | |
| 652 | |
| 653 When the character '%' or '#' is used where a file name is expected, they are | |
| 654 expanded to the current and alternate file name (see the chapter "editing | |
| 655 files" |:_%| |:_#|). | |
| 656 | |
| 657 Embedded spaces in file names are allowed on the Amiga if one file name is | |
| 658 expected as argument. Trailing spaces will be ignored, unless escaped with a | |
| 659 backslash or CTRL-V. Note that the ":next" command uses spaces to separate | |
| 660 file names. Escape the spaces to include them in a file name. Example: > | |
| 661 :next foo\ bar goes\ to school\ | |
| 662 starts editing the three files "foo bar", "goes to" and "school ". | |
| 663 | |
| 664 When you want to use the special characters '"' or '|' in a command, or want | |
| 665 to use '%' or '#' in a file name, precede them with a backslash. The | |
| 666 backslash is not required in a range and in the ":substitute" command. | |
|
6951
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6213
diff
changeset
|
667 See also |`=|. |
| 7 | 668 |
| 669 *:_!* | |
| 670 The '!' (bang) character after an Ex command makes the command behave in a | |
| 671 different way. The '!' should be placed immediately after the command, without | |
| 672 any blanks in between. If you insert blanks the '!' will be seen as an | |
| 673 argument for the command, which has a different meaning. For example: | |
| 674 :w! name write the current buffer to file "name", overwriting | |
| 675 any existing file | |
| 676 :w !name send the current buffer as standard input to command | |
| 677 "name" | |
| 678 | |
| 679 ============================================================================== | |
| 557 | 680 4. Ex command-line ranges *cmdline-ranges* *[range]* *E16* |
| 7 | 681 |
| 682 Some Ex commands accept a line range in front of them. This is noted as | |
| 683 [range]. It consists of one or more line specifiers, separated with ',' or | |
| 684 ';'. | |
| 685 | |
| 686 The basics are explained in section |10.3| of the user manual. | |
| 687 | |
| 688 *:,* *:;* | |
| 689 When separated with ';' the cursor position will be set to that line | |
| 690 before interpreting the next line specifier. This doesn't happen for ','. | |
| 691 Examples: > | |
| 692 4,/this line/ | |
| 693 < from line 4 till match with "this line" after the cursor line. > | |
| 694 5;/that line/ | |
| 695 < from line 5 till match with "that line" after line 5. | |
| 696 | |
| 697 The default line specifier for most commands is the cursor position, but the | |
| 698 commands ":write" and ":global" have the whole file (1,$) as default. | |
| 699 | |
| 700 If more line specifiers are given than required for the command, the first | |
| 701 one(s) will be ignored. | |
| 702 | |
| 17667 | 703 Line numbers may be specified with: *:range* *{address}* |
| 7 | 704 {number} an absolute line number |
| 705 . the current line *:.* | |
| 706 $ the last line in the file *:$* | |
| 707 % equal to 1,$ (the entire file) *:%* | |
| 708 't position of mark t (lowercase) *:'* | |
| 709 'T position of mark T (uppercase); when the mark is in | |
| 710 another file it cannot be used in a range | |
| 711 /{pattern}[/] the next line where {pattern} matches *:/* | |
| 712 ?{pattern}[?] the previous line where {pattern} matches *:?* | |
| 713 \/ the next line where the previously used search | |
| 714 pattern matches | |
| 715 \? the previous line where the previously used search | |
| 716 pattern matches | |
| 717 \& the next line where the previously used substitute | |
| 718 pattern matches | |
| 719 | |
| 720 Each may be followed (several times) by '+' or '-' and an optional number. | |
| 721 This number is added or subtracted from the preceding line number. If the | |
| 722 number is omitted, 1 is used. | |
| 723 | |
| 724 The "/" and "?" after {pattern} are required to separate the pattern from | |
| 725 anything that follows. | |
| 726 | |
| 727 The "/" and "?" may be preceded with another address. The search starts from | |
| 728 there. The difference from using ';' is that the cursor isn't moved. | |
| 729 Examples: > | |
| 730 /pat1//pat2/ Find line containing "pat2" after line containing | |
| 731 "pat1", without moving the cursor. | |
| 732 7;/pat2/ Find line containing "pat2", after line 7, leaving | |
| 733 the cursor in line 7. | |
| 734 | |
| 735 The {number} must be between 0 and the number of lines in the file. When | |
| 736 using a 0 (zero) this is interpreted as a 1 by most commands. Commands that | |
| 737 use it as a count do use it as a zero (|:tag|, |:pop|, etc). Some commands | |
| 738 interpret the zero as "before the first line" (|:read|, search pattern, etc). | |
| 739 | |
| 740 Examples: > | |
| 741 .+3 three lines below the cursor | |
| 742 /that/+1 the line below the next line containing "that" | |
| 743 .,$ from current line until end of file | |
| 744 0;/that the first line containing "that", also matches in the | |
| 745 first line. | |
| 746 1;/that the first line after line 1 containing "that" | |
| 747 | |
| 748 Some commands allow for a count after the command. This count is used as the | |
| 749 number of lines to be used, starting with the line given in the last line | |
| 750 specifier (the default is the cursor line). The commands that accept a count | |
| 751 are the ones that use a range but do not have a file name argument (because | |
| 752 a file name can also be a number). | |
| 753 | |
| 754 Examples: > | |
| 755 :s/x/X/g 5 substitute 'x' by 'X' in the current line and four | |
| 756 following lines | |
| 757 :23d 4 delete lines 23, 24, 25 and 26 | |
| 758 | |
| 759 | |
| 760 Folds and Range | |
| 761 | |
| 762 When folds are active the line numbers are rounded off to include the whole | |
| 763 closed fold. See |fold-behavior|. | |
| 764 | |
| 765 | |
| 557 | 766 Reverse Range *E493* |
| 7 | 767 |
| 768 A range should have the lower line number first. If this is not the case, Vim | |
| 856 | 769 will ask you if it should swap the line numbers. |
| 557 | 770 Backwards range given, OK to swap ~ |
| 771 This is not done within the global command ":g". | |
| 772 | |
| 773 You can use ":silent" before a command to avoid the question, the range will | |
| 774 always be swapped then. | |
| 7 | 775 |
| 776 | |
| 777 Count and Range *N:* | |
| 778 | |
| 779 When giving a count before entering ":", this is translated into: | |
| 780 :.,.+(count - 1) | |
| 781 In words: The 'count' lines at and after the cursor. Example: To delete | |
| 782 three lines: > | |
| 783 3:d<CR> is translated into: .,.+2d<CR> | |
| 784 < | |
| 785 | |
| 786 Visual Mode and Range *v_:* | |
| 787 | |
| 788 {Visual}: Starts a command-line with the Visual selected lines as a | |
| 4073 | 789 range. The code `:'<,'>` is used for this range, which makes |
| 7 | 790 it possible to select a similar line from the command-line |
| 791 history for repeating a command on different Visually selected | |
| 792 lines. | |
| 4073 | 793 When Visual mode was already ended, a short way to use the |
| 794 Visual area for a range is `:*`. This requires that "*" does | |
| 795 not appear in 'cpo', see |cpo-star|. Otherwise you will have | |
| 796 to type `:'<,'>` | |
| 797 | |
| 7 | 798 |
| 799 ============================================================================== | |
| 167 | 800 5. Ex command-line flags *ex-flags* |
| 801 | |
| 802 These flags are supported by a selection of Ex commands. They print the line | |
| 803 that the cursor ends up after executing the command: | |
| 804 | |
| 805 l output like for |:list| | |
| 806 # add line number | |
| 807 p output like for |:print| | |
| 808 | |
| 809 The flags can be combined, thus "l#" uses both a line number and |:list| style | |
| 810 output. | |
| 811 | |
| 812 ============================================================================== | |
| 813 6. Ex special characters *cmdline-special* | |
| 7 | 814 |
| 617 | 815 Note: These are special characters in the executed command line. If you want |
| 816 to insert special things while typing you can use the CTRL-R command. For | |
| 817 example, "%" stands for the current file name, while CTRL-R % inserts the | |
| 818 current file name right away. See |c_CTRL-R|. | |
| 819 | |
| 7013 | 820 Note: If you want to avoid the effects of special characters in a Vim script |
| 821 you may want to use |fnameescape()|. Also see |`=|. | |
| 1620 | 822 |
| 617 | 823 |
| 7 | 824 In Ex commands, at places where a file name can be used, the following |
| 825 characters have a special meaning. These can also be used in the expression | |
| 7013 | 826 function |expand()|. |
| 1733 | 827 % Is replaced with the current file name. *:_%* *c_%* |
| 828 # Is replaced with the alternate file name. *:_#* *c_#* | |
| 5510 | 829 This is remembered for every window. |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1937
diff
changeset
|
830 #n (where n is a number) is replaced with *:_#0* *:_#n* |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1937
diff
changeset
|
831 the file name of buffer n. "#0" is the same as "#". *c_#n* |
| 1733 | 832 ## Is replaced with all names in the argument list *:_##* *c_##* |
| 7 | 833 concatenated, separated by spaces. Each space in a name |
| 834 is preceded with a backslash. | |
| 1733 | 835 #<n (where n is a number > 0) is replaced with old *:_#<* *c_#<* |
| 836 file name n. See |:oldfiles| or |v:oldfiles| to get the | |
| 837 number. *E809* | |
|
2570
71b56b4e7785
Make the references to features in the help more consistent. (Sylvain Hitier)
Bram Moolenaar <bram@vim.org>
parents:
2561
diff
changeset
|
838 {only when compiled with the |+eval| and |+viminfo| features} |
| 1733 | 839 |
| 840 Note that these, except "#<n", give the file name as it was typed. If an | |
| 841 absolute path is needed (when using the file name from a different directory), | |
| 842 you need to add ":p". See |filename-modifiers|. | |
| 843 | |
| 844 The "#<n" item returns an absolute path, but it will start with "~/" for files | |
| 845 below your home directory. | |
| 846 | |
| 7 | 847 Note that backslashes are inserted before spaces, so that the command will |
| 848 correctly interpret the file name. But this doesn't happen for shell | |
| 1733 | 849 commands. For those you probably have to use quotes (this fails for files |
| 850 that contain a quote and wildcards): > | |
| 7 | 851 :!ls "%" |
| 852 :r !spell "%" | |
| 853 | |
| 854 To avoid the special meaning of '%' and '#' insert a backslash before it. | |
| 855 Detail: The special meaning is always escaped when there is a backslash before | |
| 856 it, no matter how many backslashes. | |
| 857 you type: result ~ | |
| 858 # alternate.file | |
| 859 \# # | |
| 860 \\# \# | |
|
6951
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6213
diff
changeset
|
861 Also see |`=|. |
| 7013 | 862 |
|
14700
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
863 *:<cword>* *<cword>* *:<cWORD>* *<cWORD>* |
|
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
864 *:<cexpr>* *<cexpr>* *:<cfile>* *<cfile>* |
|
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
865 *:<afile>* *<afile>* *:<abuf>* *<abuf>* |
|
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
866 *:<amatch>* *<amatch>* |
|
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
867 *:<sfile>* *<sfile>* *:<slnum>* *<slnum>* |
|
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
868 *:<sflnum>* *<sflnum>* *E499* *E500* |
| 7 | 869 Note: these are typed literally, they are not special keys! |
| 870 <cword> is replaced with the word under the cursor (like |star|) | |
| 871 <cWORD> is replaced with the WORD under the cursor (see |WORD|) | |
|
12421
da55ea30842c
patch 8.0.1090: cannot get the text under the cursor like v:beval_text
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
872 <cexpr> is replaced with the word under the cursor, including more |
|
da55ea30842c
patch 8.0.1090: cannot get the text under the cursor like v:beval_text
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
873 to form a C expression. E.g., when the cursor is on "arg" |
|
da55ea30842c
patch 8.0.1090: cannot get the text under the cursor like v:beval_text
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
874 of "ptr->arg" then the result is "ptr->arg"; when the |
|
da55ea30842c
patch 8.0.1090: cannot get the text under the cursor like v:beval_text
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
875 cursor is on "]" of "list[idx]" then the result is |
|
da55ea30842c
patch 8.0.1090: cannot get the text under the cursor like v:beval_text
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
876 "list[idx]". This is used for |v:beval_text|. |
| 7 | 877 <cfile> is replaced with the path name under the cursor (like what |
| 878 |gf| uses) | |
| 2662 | 879 <afile> When executing autocommands, is replaced with the file name |
|
12756
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
12499
diff
changeset
|
880 of the buffer being manipulated, or the file for a read or |
|
14700
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
881 write. *E495* |
| 2662 | 882 <abuf> When executing autocommands, is replaced with the currently |
| 715 | 883 effective buffer number (for ":r file" and ":so file" it is |
| 884 the current buffer, the file being read/sourced is not in a | |
|
14700
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
885 buffer). *E496* |
| 2662 | 886 <amatch> When executing autocommands, is replaced with the match for |
|
14700
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
887 which this autocommand was executed. *E497* |
|
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
888 It differs from <afile> only when the file name isn't used |
|
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
889 to match with (for FileType, Syntax and SpellFileMissing |
|
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
890 events). |
| 2662 | 891 <sfile> When executing a ":source" command, is replaced with the |
| 7013 | 892 file name of the sourced file. *E498* |
|
7147
c590de398af9
commit https://github.com/vim/vim/commit/ca63501fbcd1cf9c8aa9ff12c093c95b62a89ed7
Christian Brabandt <cb@256bit.org>
parents:
7092
diff
changeset
|
893 When executing a function, is replaced with: |
|
c590de398af9
commit https://github.com/vim/vim/commit/ca63501fbcd1cf9c8aa9ff12c093c95b62a89ed7
Christian Brabandt <cb@256bit.org>
parents:
7092
diff
changeset
|
894 "function {function-name}[{lnum}]" |
|
c590de398af9
commit https://github.com/vim/vim/commit/ca63501fbcd1cf9c8aa9ff12c093c95b62a89ed7
Christian Brabandt <cb@256bit.org>
parents:
7092
diff
changeset
|
895 function call nesting is indicated like this: |
|
c590de398af9
commit https://github.com/vim/vim/commit/ca63501fbcd1cf9c8aa9ff12c093c95b62a89ed7
Christian Brabandt <cb@256bit.org>
parents:
7092
diff
changeset
|
896 "function {function-name1}[{lnum}]..{function-name2}[{lnum}]" |
|
c590de398af9
commit https://github.com/vim/vim/commit/ca63501fbcd1cf9c8aa9ff12c093c95b62a89ed7
Christian Brabandt <cb@256bit.org>
parents:
7092
diff
changeset
|
897 Note that filename-modifiers are useless when <sfile> is |
|
c590de398af9
commit https://github.com/vim/vim/commit/ca63501fbcd1cf9c8aa9ff12c093c95b62a89ed7
Christian Brabandt <cb@256bit.org>
parents:
7092
diff
changeset
|
898 used inside a function. |
| 2662 | 899 <slnum> When executing a ":source" command, is replaced with the |
|
14700
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
900 line number. *E842* |
| 2662 | 901 When executing a function it's the line number relative to |
| 902 the start of the function. | |
|
14700
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
903 <sflnum> When executing a script, is replaced with the line number. |
|
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
904 It differs from <slnum> in that <sflnum> is replaced with |
|
0a3b9ecf7cb8
patch 8.1.0362: cannot get the script line number when executing a function
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
905 the script line number in any situation. *E961* |
| 7 | 906 |
| 907 *filename-modifiers* | |
|
5692
80e5f9584b02
Update runtime files. Add Euphoria syntax files.
Bram Moolenaar <bram@vim.org>
parents:
5510
diff
changeset
|
908 *:_%:* *::8* *::p* *::.* *::~* *::h* *::t* *::r* *::e* *::s* *::gs* *::S* |
|
80e5f9584b02
Update runtime files. Add Euphoria syntax files.
Bram Moolenaar <bram@vim.org>
parents:
5510
diff
changeset
|
909 *%:8* *%:p* *%:.* *%:~* *%:h* *%:t* *%:r* *%:e* *%:s* *%:gs* *%:S* |
| 7 | 910 The file name modifiers can be used after "%", "#", "#n", "<cfile>", "<sfile>", |
| 911 "<afile>" or "<abuf>". They are also used with the |fnamemodify()| function. | |
| 912 These are not available when Vim has been compiled without the |+modify_fname| | |
| 913 feature. | |
| 914 These modifiers can be given, in this order: | |
| 915 :p Make file name a full path. Must be the first modifier. Also | |
| 916 changes "~/" (and "~user/" for Unix and VMS) to the path for | |
| 917 the home directory. If the name is a directory a path | |
| 918 separator is added at the end. For a file name that does not | |
| 919 exist and does not have an absolute path the result is | |
| 3682 | 920 unpredictable. On MS-Windows an 8.3 filename is expanded to |
| 921 the long name. | |
| 7 | 922 :8 Converts the path to 8.3 short format (currently only on |
| 3682 | 923 MS-Windows). Will act on as much of a path that is an |
| 924 existing path. | |
| 7 | 925 :~ Reduce file name to be relative to the home directory, if |
| 926 possible. File name is unmodified if it is not below the home | |
| 927 directory. | |
| 928 :. Reduce file name to be relative to current directory, if | |
| 929 possible. File name is unmodified if it is not below the | |
| 14123 | 930 current directory, but on MS-Windows the drive is removed if |
| 931 it is the current drive. | |
| 7 | 932 For maximum shortness, use ":~:.". |
| 933 :h Head of the file name (the last component and any separators | |
| 934 removed). Cannot be used with :e, :r or :t. | |
| 935 Can be repeated to remove several components at the end. | |
| 936 When the file name ends in a path separator, only the path | |
| 937 separator is removed. Thus ":p:h" on a directory name results | |
| 938 on the directory name itself (without trailing slash). | |
| 939 When the file name is an absolute path (starts with "/" for | |
| 940 Unix; "x:\" for MS-DOS, WIN32, OS/2; "drive:" for Amiga), that | |
| 941 part is not removed. When there is no head (path is relative | |
| 942 to current directory) the result is empty. | |
| 943 :t Tail of the file name (last component of the name). Must | |
| 944 precede any :r or :e. | |
| 945 :r Root of the file name (the last extension removed). When | |
| 946 there is only an extension (file name that starts with '.', | |
| 947 e.g., ".vimrc"), it is not removed. Can be repeated to remove | |
| 948 several extensions (last one first). | |
| 949 :e Extension of the file name. Only makes sense when used alone. | |
| 950 When there is no extension the result is empty. | |
| 951 When there is only an extension (file name that starts with | |
| 952 '.'), the result is empty. Can be repeated to include more | |
| 953 extensions. If there are not enough extensions (but at least | |
| 954 one) as much as possible are included. | |
| 955 :s?pat?sub? | |
| 956 Substitute the first occurrence of "pat" with "sub". This | |
| 957 works like the |:s| command. "pat" is a regular expression. | |
| 958 Any character can be used for '?', but it must not occur in | |
| 959 "pat" or "sub". | |
| 960 After this, the previous modifiers can be used again. For | |
| 961 example ":p", to make a full path after the substitution. | |
| 962 :gs?pat?sub? | |
| 2751 | 963 Substitute all occurrences of "pat" with "sub". Otherwise |
| 7 | 964 this works like ":s". |
| 7013 | 965 :S Escape special characters for use with a shell command (see |
|
5692
80e5f9584b02
Update runtime files. Add Euphoria syntax files.
Bram Moolenaar <bram@vim.org>
parents:
5510
diff
changeset
|
966 |shellescape()|). Must be the last one. Examples: > |
|
80e5f9584b02
Update runtime files. Add Euphoria syntax files.
Bram Moolenaar <bram@vim.org>
parents:
5510
diff
changeset
|
967 :!dir <cfile>:S |
|
80e5f9584b02
Update runtime files. Add Euphoria syntax files.
Bram Moolenaar <bram@vim.org>
parents:
5510
diff
changeset
|
968 :call system('chmod +w -- ' . expand('%:S')) |
| 7 | 969 |
| 970 Examples, when the file name is "src/version.c", current dir | |
| 971 "/home/mool/vim": > | |
| 972 :p /home/mool/vim/src/version.c | |
| 973 :p:. src/version.c | |
| 974 :p:~ ~/vim/src/version.c | |
| 975 :h src | |
| 976 :p:h /home/mool/vim/src | |
| 977 :p:h:h /home/mool/vim | |
| 978 :t version.c | |
| 979 :p:t version.c | |
| 980 :r src/version | |
| 981 :p:r /home/mool/vim/src/version | |
| 982 :t:r version | |
| 983 :e c | |
| 984 :s?version?main? src/main.c | |
| 985 :s?version?main?:p /home/mool/vim/src/main.c | |
| 986 :p:gs?/?\\? \home\mool\vim\src\version.c | |
| 987 | |
| 988 Examples, when the file name is "src/version.c.gz": > | |
| 989 :p /home/mool/vim/src/version.c.gz | |
| 990 :e gz | |
| 991 :e:e c.gz | |
| 992 :e:e:e c.gz | |
| 993 :e:e:r c | |
| 994 :r src/version.c | |
| 995 :r:e c | |
| 996 :r:r src/version | |
| 997 :r:r:r src/version | |
| 998 < | |
| 999 *extension-removal* *:_%<* | |
| 1000 If a "<" is appended to "%", "#", "#n" or "CTRL-V p" the extension of the file | |
| 1001 name is removed (everything after and including the last '.' in the file | |
| 1002 name). This is included for backwards compatibility with version 3.0, the | |
| 1003 ":r" form is preferred. Examples: > | |
| 1004 | |
| 1005 % current file name | |
| 1006 %< current file name without extension | |
| 1007 # alternate file name for current window | |
| 1008 #< idem, without extension | |
| 1009 #31 alternate file number 31 | |
| 1010 #31< idem, without extension | |
| 1011 <cword> word under the cursor | |
| 1012 <cWORD> WORD under the cursor (see |WORD|) | |
| 1013 <cfile> path name under the cursor | |
| 1014 <cfile>< idem, without extension | |
| 1015 | |
| 1016 Note: Where a file name is expected wildcards expansion is done. On Unix the | |
| 1017 shell is used for this, unless it can be done internally (for speed). | |
| 7013 | 1018 Unless in |restricted-mode|, backticks work also, like in > |
| 7 | 1019 :n `echo *.c` |
| 1020 But expansion is only done if there are any wildcards before expanding the | |
| 1021 '%', '#', etc.. This avoids expanding wildcards inside a file name. If you | |
| 1022 want to expand the result of <cfile>, add a wildcard character to it. | |
| 1023 Examples: (alternate file name is "?readme?") | |
| 1024 command expands to ~ | |
| 1025 :e # :e ?readme? | |
| 1026 :e `ls #` :e {files matching "?readme?"} | |
| 1027 :e #.* :e {files matching "?readme?.*"} | |
| 1028 :cd <cfile> :cd {file name under cursor} | |
| 1029 :cd <cfile>* :cd {file name under cursor plus "*" and then expanded} | |
|
6951
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6213
diff
changeset
|
1030 Also see |`=|. |
| 7 | 1031 |
| 1032 When the expanded argument contains a "!" and it is used for a shell command | |
| 1620 | 1033 (":!cmd", ":r !cmd" or ":w !cmd"), the "!" is escaped with a backslash to |
| 1034 avoid it being expanded into a previously used command. When the 'shell' | |
| 1035 option contains "sh", this is done twice, to avoid the shell trying to expand | |
| 1036 the "!". | |
| 7 | 1037 |
| 1038 *filename-backslash* | |
| 1039 For filesystems that use a backslash as directory separator (MS-DOS, Windows, | |
| 1040 OS/2), it's a bit difficult to recognize a backslash that is used to escape | |
| 1041 the special meaning of the next character. The general rule is: If the | |
| 1042 backslash is followed by a normal file name character, it does not have a | |
| 1043 special meaning. Therefore "\file\foo" is a valid file name, you don't have | |
| 1044 to type the backslash twice. | |
| 1045 | |
| 1046 An exception is the '$' sign. It is a valid character in a file name. But | |
| 1047 to avoid a file name like "$home" to be interpreted as an environment variable, | |
| 1048 it needs to be preceded by a backslash. Therefore you need to use "/\$home" | |
| 1049 for the file "$home" in the root directory. A few examples: | |
| 1050 | |
| 1051 FILE NAME INTERPRETED AS ~ | |
| 1052 $home expanded to value of environment var $home | |
| 1053 \$home file "$home" in current directory | |
| 1054 /\$home file "$home" in root directory | |
| 1055 \\$home file "\\", followed by expanded $home | |
| 7013 | 1056 |
|
6951
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6213
diff
changeset
|
1057 Also see |`=|. |
| 7 | 1058 |
| 1059 ============================================================================== | |
| 4229 | 1060 7. Command-line window *cmdline-window* *cmdwin* |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1937
diff
changeset
|
1061 *command-line-window* |
| 7 | 1062 In the command-line window the command line can be edited just like editing |
| 1063 text in any window. It is a special kind of window, because you cannot leave | |
| 1064 it in a normal way. | |
| 17571 | 1065 {not available when compiled without the |+cmdline_hist| feature} |
| 7 | 1066 |
| 1067 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1937
diff
changeset
|
1068 OPEN *c_CTRL-F* *q:* *q/* *q?* |
| 7 | 1069 |
| 1070 There are two ways to open the command-line window: | |
| 1071 1. From Command-line mode, use the key specified with the 'cedit' option. | |
| 1072 The default is CTRL-F when 'compatible' is not set. | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1937
diff
changeset
|
1073 2. From Normal mode, use the "q:", "q/" or "q?" command. |
| 7 | 1074 This starts editing an Ex command-line ("q:") or search string ("q/" or |
| 1075 "q?"). Note that this is not possible while recording is in progress (the | |
| 1076 "q" stops recording then). | |
| 1077 | |
| 1078 When the window opens it is filled with the command-line history. The last | |
| 1079 line contains the command as typed so far. The left column will show a | |
| 1080 character that indicates the type of command-line being edited, see | |
| 1081 |cmdwin-char|. | |
| 1082 | |
| 1083 Vim will be in Normal mode when the editor is opened, except when 'insertmode' | |
| 1084 is set. | |
| 1085 | |
| 1086 The height of the window is specified with 'cmdwinheight' (or smaller if there | |
| 1087 is no room). The window is always full width and is positioned just above the | |
| 1088 command-line. | |
| 1089 | |
| 1090 | |
| 1091 EDIT | |
| 1092 | |
| 1093 You can now use commands to move around and edit the text in the window. Both | |
| 1094 in Normal mode and Insert mode. | |
| 1095 | |
| 1096 It is possible to use ":", "/" and other commands that use the command-line, | |
| 1097 but it's not possible to open another command-line window then. There is no | |
| 1098 nesting. | |
| 1099 *E11* | |
| 1100 The command-line window is not a normal window. It is not possible to move to | |
| 1101 another window or edit another buffer. All commands that would do this are | |
| 1102 disabled in the command-line window. Of course it _is_ possible to execute | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1937
diff
changeset
|
1103 any command that you entered in the command-line window. Other text edits are |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1937
diff
changeset
|
1104 discarded when closing the window. |
| 7 | 1105 |
| 1106 | |
| 1107 CLOSE *E199* | |
| 1108 | |
| 1109 There are several ways to leave the command-line window: | |
| 1110 | |
| 1111 <CR> Execute the command-line under the cursor. Works both in | |
| 1112 Insert and in Normal mode. | |
| 1113 CTRL-C Continue in Command-line mode. The command-line under the | |
| 1114 cursor is used as the command-line. Works both in Insert and | |
|
10498
883396809b45
commit https://github.com/vim/vim/commit/bc2eada5424bff06f7eb77c032ecc067da52b846
Christian Brabandt <cb@256bit.org>
parents:
10434
diff
changeset
|
1115 in Normal mode. There is no redraw, thus the window will |
|
883396809b45
commit https://github.com/vim/vim/commit/bc2eada5424bff06f7eb77c032ecc067da52b846
Christian Brabandt <cb@256bit.org>
parents:
10434
diff
changeset
|
1116 remain visible. |
| 7 | 1117 :quit Discard the command line and go back to Normal mode. |
|
10498
883396809b45
commit https://github.com/vim/vim/commit/bc2eada5424bff06f7eb77c032ecc067da52b846
Christian Brabandt <cb@256bit.org>
parents:
10434
diff
changeset
|
1118 ":close", ":exit", ":xit" and CTRL-\ CTRL-N also work. |
| 7 | 1119 :qall Quit Vim, unless there are changes in some buffer. |
| 1120 :qall! Quit Vim, discarding changes to any buffer. | |
| 1121 | |
| 1122 Once the command-line window is closed the old window sizes are restored. The | |
| 1123 executed command applies to the window and buffer where the command-line was | |
| 1124 started from. This works as if the command-line window was not there, except | |
| 1125 that there will be an extra screen redraw. | |
| 1126 The buffer used for the command-line window is deleted. Any changes to lines | |
| 1127 other than the one that is executed with <CR> are lost. | |
| 1128 | |
| 711 | 1129 If you would like to execute the command under the cursor and then have the |
| 1130 command-line window open again, you may find this mapping useful: > | |
| 1131 | |
| 1698 | 1132 :autocmd CmdwinEnter * map <buffer> <F5> <CR>q: |
| 711 | 1133 |
| 7 | 1134 |
| 1135 VARIOUS | |
| 1136 | |
| 1137 The command-line window cannot be used: | |
| 1138 - when there already is a command-line window (no nesting) | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1937
diff
changeset
|
1139 - for entering an encryption key or when using inputsecret() |
| 7 | 1140 |
| 1141 Some options are set when the command-line window is opened: | |
| 1142 'filetype' "vim", when editing an Ex command-line; this starts Vim syntax | |
| 1143 highlighting if it was enabled | |
| 1144 'rightleft' off | |
| 1145 'modifiable' on | |
| 1146 'buftype' "nofile" | |
| 1147 'swapfile' off | |
| 1148 | |
| 1149 It is allowed to write the buffer contents to a file. This is an easy way to | |
| 1150 save the command-line history and read it back later. | |
| 1151 | |
| 1152 If the 'wildchar' option is set to <Tab>, and the command-line window is used | |
| 1153 for an Ex command, then two mappings will be added to use <Tab> for completion | |
| 1154 in the command-line window, like this: > | |
| 1155 :imap <buffer> <Tab> <C-X><C-V> | |
| 1156 :nmap <buffer> <Tab> a<C-X><C-V> | |
| 1157 Note that hitting <Tab> in Normal mode will do completion on the next | |
| 1158 character. That way it works at the end of the line. | |
| 1159 If you don't want these mappings, disable them with: > | |
| 1160 au CmdwinEnter [:>] iunmap <Tab> | |
| 1161 au CmdwinEnter [:>] nunmap <Tab> | |
| 1162 You could put these lines in your vimrc file. | |
| 1163 | |
| 1164 While in the command-line window you cannot use the mouse to put the cursor in | |
| 1165 another window, or drag statuslines of other windows. You can drag the | |
| 1166 statusline of the command-line window itself and the statusline above it. | |
| 1167 Thus you can resize the command-line window, but not others. | |
| 1168 | |
| 6153 | 1169 The |getcmdwintype()| function returns the type of the command-line being |
| 1170 edited as described in |cmdwin-char|. | |
| 1171 | |
| 7 | 1172 |
| 1173 AUTOCOMMANDS | |
| 1174 | |
| 1175 Two autocommand events are used: |CmdwinEnter| and |CmdwinLeave|. Since this | |
| 1176 window is of a special type, the WinEnter, WinLeave, BufEnter and BufLeave | |
| 1177 events are not triggered. You can use the Cmdwin events to do settings | |
| 1178 specifically for the command-line window. Be careful not to cause side | |
| 1179 effects! | |
| 1180 Example: > | |
| 1698 | 1181 :au CmdwinEnter : let b:cpt_save = &cpt | set cpt=. |
| 7 | 1182 :au CmdwinLeave : let &cpt = b:cpt_save |
| 1698 | 1183 This sets 'complete' to use completion in the current window for |i_CTRL-N|. |
| 7 | 1184 Another example: > |
| 1185 :au CmdwinEnter [/?] startinsert | |
| 1186 This will make Vim start in Insert mode in the command-line window. | |
| 1187 | |
| 1188 *cmdwin-char* | |
| 1189 The character used for the pattern indicates the type of command-line: | |
| 1190 : normal Ex command | |
| 1191 > debug mode command |debug-mode| | |
| 1192 / forward search string | |
| 1193 ? backward search string | |
| 1194 = expression for "= |expr-register| | |
| 1195 @ string for |input()| | |
| 1196 - text for |:insert| or |:append| | |
| 1197 | |
| 14421 | 1198 vim:tw=78:ts=8:noet:ft=help:norl: |