usr_20.txt (14100B)
1 *usr_20.txt* For Vim version 9.2. Last change: 2026 Jun 02 2 3 4 VIM USER MANUAL by Bram Moolenaar 5 6 7 Typing command-line commands quickly 8 9 10 Vim has a few generic features that makes it easier to enter commands. Colon 11 commands can be abbreviated, edited and repeated. Completion is available for 12 nearly everything. 13 14 |20.1| Command line editing 15 |20.2| Command line abbreviations 16 |20.3| Command line completion 17 |20.4| Command line history 18 |20.5| Command line window 19 20 Next chapter: |usr_21.txt| Go away and come back 21 Previous chapter: |usr_12.txt| Clever tricks 22 Table of contents: |usr_toc.txt| 23 24 ============================================================================== 25 *20.1* Command line editing 26 27 When you use a colon (:) command or search for a string with / or ?, Vim puts 28 the cursor on the bottom of the screen. There you type the command or search 29 pattern. This is called the Command line. Also when it's used for entering a 30 search command. 31 32 The most obvious way to edit the command you type is by pressing the <BS> key. 33 This erases the character before the cursor. To erase another character, 34 typed earlier, first move the cursor with the cursor keys. 35 For example, you have typed this: > 36 37 :s/col/pig/ 38 39 Before you hit <Enter>, you notice that "col" should be "cow". To correct 40 this, you type <Left> five times. The cursor is now just after "col". Type 41 <BS> and "w" to correct: > 42 43 :s/cow/pig/ 44 45 Now you can press <Enter> directly. You don't have to move the cursor to the 46 end of the line before executing the command. 47 48 The most often used keys to move around in the command line: 49 50 <Left> one character left 51 <Right> one character right 52 <S-Left> or <C-Left> one word left 53 <S-Right> or <C-Right> one word right 54 CTRL-B or <Home> to begin of command line 55 CTRL-E or <End> to end of command line 56 57 Note: 58 <S-Left> (cursor left key with Shift key pressed) and <C-Left> (cursor 59 left key with Control pressed) will not work on all keyboards. Same 60 for the other Shift and Control combinations. 61 62 You can also use the mouse to move the cursor. 63 64 65 DELETING 66 67 As mentioned, <BS> deletes the character before the cursor. To delete a whole 68 word use CTRL-W. 69 70 /the fine pig ~ 71 72 CTRL-W 73 74 /the fine ~ 75 76 CTRL-U removes all text, thus allows you to start all over again. 77 78 79 OVERSTRIKE 80 81 The <Insert> key toggles between inserting characters and replacing the 82 existing ones. Start with this text: 83 84 /the fine pig ~ 85 86 Move the cursor to the start of "fine" with <S-Left> twice (or <Left> eight 87 times, if <S-Left> doesn't work). Now press <Insert> to switch to overstrike 88 and type "great": 89 90 /the greatpig ~ 91 92 Oops, we lost the space. Now, don't use <BS>, because it would delete the 93 "t" (this is different from Replace mode). Instead, press <Insert> to switch 94 from overstrike to inserting, and type the space: 95 96 /the great pig ~ 97 98 99 CANCELLING 100 101 You thought of executing a : or / command, but changed your mind. To get rid 102 of what you already typed, without executing it, press CTRL-C or <Esc>. 103 104 Note: 105 <Esc> is the universal "get out" key. Unfortunately, in the good old 106 Vi pressing <Esc> in a command line executed the command! Since that 107 might be considered to be a bug, Vim uses <Esc> to cancel the command. 108 But with the 'cpoptions' option it can be made Vi compatible. And 109 when using a mapping (which might be written for Vi) <Esc> also works 110 Vi compatible. Therefore, using CTRL-C is a method that always works. 111 112 If you are at the start of the command line, pressing <BS> will cancel the 113 command. It's like deleting the ":" or "/" that the line starts with. 114 115 ============================================================================== 116 *20.2* Command line abbreviations 117 118 Some of the ":" commands are really long. We already mentioned that 119 ":substitute" can be abbreviated to ":s". This is a generic mechanism, and 120 most ":" commands can be abbreviated. However, in Vim9 script some commands 121 cannot be shortened to improve readability - see |vim9-no-shorten|. 122 123 The builtin function |fullcommand()| can be used to return an abbreviated 124 command's full name. For example, the following commands echo "edit", "echo", 125 and "echowindow": 126 >vim 127 :echo fullcommand('e') 128 :echo fullcommand('ec') 129 :echo fullcommand('echow') 130 < 131 How short can a command get? There are 26 letters, and many more commands. 132 For example, ":set" also starts with ":s", but ":s" doesn't start a ":set" 133 command. Instead ":set" can be abbreviated to ":se". 134 When the shorter form of a command could be used for two commands, it 135 stands for only one of them. There is no logic behind which one, you have to 136 learn them. In the help files the shortest form that works is mentioned. For 137 example: > 138 139 :s[ubstitute] 140 141 This means that the shortest form of ":substitute" is ":s". The following 142 characters are optional. Thus ":su" and ":sub" also work. 143 144 In the user manual we will either use the full name of command, or a short 145 version that is still readable. For example, ":function" can be abbreviated 146 to ":fu". But since most people don't understand what that stands for, we 147 will use ":fun". (Vim doesn't have a ":funny" command, otherwise ":fun" would 148 be confusing too.) 149 150 It is recommended that in Vim scripts you write the full command name. That 151 makes it easier to read back when you make later changes. Except for some 152 often used commands like ":w" (":write") and ":r" (":read"). 153 A particularly confusing one is ":end", which could stand for ":endif", 154 ":endwhile" or ":endfunction". Therefore, always use the full name. 155 156 157 SHORT OPTION NAMES 158 159 In the user manual the long version of the option names is used. Many options 160 also have a short name. Unlike ":" commands, there is only one short name 161 that works. For example, the short name of 'autoindent' is 'ai'. Thus these 162 two commands do the same thing: > 163 164 :set autoindent 165 :set ai 166 167 You can find the full list of long and short names here: |option-list|. 168 169 ============================================================================== 170 *20.3* Command line completion 171 172 This is one of those Vim features that, by itself, is a reason to switch from 173 Vi to Vim. Once you have used this, you can't do without. 174 175 Suppose you have a directory that contains these files: 176 177 info.txt 178 intro.txt 179 bodyofthepaper.txt 180 181 To edit the last one, you use the command: > 182 183 :edit bodyofthepaper.txt 184 185 It's easy to type this wrong. A much quicker way is: > 186 187 :edit b<Tab> 188 189 Which will result in the same command. What happened? The <Tab> key does 190 completion of the word before the cursor. In this case "b". Vim looks in the 191 directory and finds only one file that starts with a "b". That must be the 192 one you are looking for, thus Vim completes the file name for you. 193 194 Now type: > 195 196 :edit i<Tab> 197 198 Vim will beep, and give you: > 199 200 :edit info.txt 201 202 The beep means that Vim has found more than one match. It then uses the first 203 match it found (alphabetically). If you press <Tab> again, you get: > 204 205 :edit intro.txt 206 207 Thus, if the first <Tab> doesn't give you the file you were looking for, press 208 it again. If there are more matches, you will see them all, one at a time. 209 If you press <Tab> on the last matching entry, you will go back to what you 210 first typed: > 211 212 :edit i 213 214 Then it starts all over again. Thus Vim cycles through the list of matches. 215 Use CTRL-P to go through the list in the other direction: 216 217 <------------------- <Tab> -------------------------+ 218 | 219 <Tab> --> <Tab> --> 220 :edit i :edit info.txt :edit intro.txt 221 <-- CTRL-P <-- CTRL-P 222 | 223 +---------------------- CTRL-P ------------------------> 224 225 226 CONTEXT 227 228 When you type ":set i" instead of ":edit i" and press <Tab> you get: > 229 230 :set icon 231 232 Hey, why didn't you get ":set info.txt"? That's because Vim has context 233 sensitive completion. The kind of words Vim will look for depends on the 234 command before it. Vim knows that you cannot use a file name just after a 235 ":set" command, but you can use an option name. 236 Again, if you repeat typing the <Tab>, Vim will cycle through all matches. 237 There are quite a few, it's better to type more characters first: > 238 239 :set isk<Tab> 240 241 Gives: > 242 243 :set iskeyword 244 245 Now type "=" and press <Tab>: > 246 247 :set iskeyword=@,48-57,_,192-255 248 249 What happens here is that Vim inserts the old value of the option. Now you 250 can edit it. 251 What is completed with <Tab> is what Vim expects in that place. Just try 252 it out to see how it works. In some situations you will not get what you 253 want. That's either because Vim doesn't know what you want, or because 254 completion was not implemented for that situation. In that case you will get 255 a <Tab> inserted (displayed as ^I). 256 257 258 LIST MATCHES 259 260 When there are many matches, you would like to see an overview. Do this by 261 pressing CTRL-D. For example, pressing CTRL-D after: > 262 263 :set is 264 265 results in: > 266 267 :set is 268 incsearch isfname isident iskeyword isprint 269 :set is 270 271 Vim lists the matches and then comes back with the text you typed. You can 272 now check the list for the item you wanted. If it isn't there, you can use 273 <BS> to correct the word. If there are many matches, type a few more 274 characters before pressing <Tab> to complete the rest. 275 If you have watched carefully, you will have noticed that "incsearch" 276 doesn't start with "is". In this case "is" stands for the short name of 277 "incsearch". (Many options have a short and a long name.) Vim is clever 278 enough to know that you might have wanted to expand the short name of the 279 option into the long name. 280 281 282 THERE IS MORE 283 284 The CTRL-L command completes the word to the longest unambiguous string. If 285 you type ":edit i" and there are files "info.txt" and "info_backup.txt" you 286 will get ":edit info". 287 288 The 'wildmode' option can be used to change the way completion works. 289 The 'wildmenu' option can be used to get a menu-like list of matches. 290 Use the 'suffixes' option to specify files that are less important and appear 291 at the end of the list of files. 292 The 'wildignore' option specifies files that are not listed at all. 293 294 More about all of this here: |cmdline-completion| 295 296 ============================================================================== 297 *20.4* Command line history 298 299 In chapter 3 we briefly mentioned the history. The basics are that you can 300 use the <Up> key to recall an older command line. <Down> then takes you back 301 to newer commands. 302 303 There are actually five histories. The ones we will mention here are for ":" 304 commands and for "/" and "?" search commands. The "/" and "?" commands share 305 the same history, because they are both search commands. The three other 306 histories are for expressions, debug mode commands and input lines for the 307 input() function. |cmdline-history| 308 309 Suppose you have done a ":set" command, typed ten more colon commands and then 310 want to repeat that ":set" command again. You could press ":" and then ten 311 times <Up>. There is a quicker way: > 312 313 :se<Up> 314 315 Vim will now go back to the previous command that started with "se". You have 316 a good chance that this is the ":set" command you were looking for. At least 317 you should not have to press <Up> very often (unless ":set" commands is all 318 you have done). 319 320 The <Up> key will use the text typed so far and compare it with the lines in 321 the history. Only matching lines will be used. 322 If you do not find the line you were looking for, use <Down> to go back to 323 what you typed and correct that. Or use CTRL-U to start all over again. 324 325 To see all the lines in the history: > 326 327 :history 328 329 That's the history of ":" commands. The search history is displayed with this 330 command: > 331 332 :history / 333 334 CTRL-P will work like <Up>, except that it doesn't matter what you already 335 typed. Similarly for CTRL-N and <Down>. CTRL-P stands for previous, CTRL-N 336 for next. 337 338 ============================================================================== 339 *20.5* Command line window 340 341 Typing the text in the command line works differently from typing text in 342 Insert mode. It doesn't allow many commands to change the text. For most 343 commands that's OK, but sometimes you have to type a complicated command. 344 That's where the command line window is useful. 345 346 Open the command line window with this command: > 347 348 q: 349 350 Vim now opens a (small) window at the bottom. It contains the command line 351 history, and an empty line at the end: 352 353 +-------------------------------------+ 354 |other window | 355 |~ | 356 |file.txt=============================| 357 |:e c | 358 |:e config.h.in | 359 |:set path=.,/usr/include,, | 360 |:set iskeyword=@,48-57,_,192-255 | 361 |:set is | 362 |:q | 363 |: | 364 |command-line=========================| 365 | | 366 +-------------------------------------+ 367 368 You are now in Normal mode. You can use the "hjkl" keys to move around. For 369 example, move up with "5k" to the ":e config.h.in" line. Type "$h" to go to 370 the "i" of "in" and type "cwout". Now you have changed the line to: 371 372 :e config.h.out ~ 373 374 Now press <Enter> and this command will be executed. The command line window 375 will close. 376 The <Enter> command will execute the line under the cursor. It doesn't 377 matter whether Vim is in Insert mode or in Normal mode. 378 Changes in the command line window are lost. They do not result in the 379 history to be changed. Except that the command you execute will be added to 380 the end of the history, like with all executed commands. 381 382 The command line window is very useful when you want to have overview of the 383 history, lookup a similar command, change it a bit and execute it. A search 384 command can be used to find something. 385 In the previous example the "?config" search command could have been used 386 to find the previous command that contains "config". It's a bit strange, 387 because you are using a command line to search in the command line window. 388 While typing that search command you can't open another command line window, 389 there can be only one. 390 391 ============================================================================== 392 393 Next chapter: |usr_21.txt| Go away and come back 394 395 Copyright: see |manual-copyright| vim:tw=78:ts=8:noet:ft=help:norl: