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