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