1 *intro.txt* For Vim version 7.1. Last change: 2007 May 07
4 VIM REFERENCE MANUAL by Bram Moolenaar
7 Introduction to Vim *ref* *reference*
9 1. Introduction |intro|
10 2. Vim on the internet |internet|
12 4. Notation |notation|
13 5. Modes, introduction |vim-modes-intro|
14 6. Switching from mode to mode |mode-switching|
15 7. The window contents |window-contents|
16 8. Definitions |definitions|
18 ==============================================================================
19 1. Introduction *intro*
21 Vim stands for Vi IMproved. It used to be Vi IMitation, but there are so many
22 improvements that a name change was appropriate. Vim is a text editor which
23 includes almost all the commands from the Unix program "Vi" and a lot of new
24 ones. It is very useful for editing programs and other plain text.
25 All commands are given with the keyboard. This has the advantage that you
26 can keep your fingers on the keyboard and your eyes on the screen. For those
27 who want it, there is mouse support and a GUI version with scrollbars and
28 menus (see |gui.txt|).
30 An overview of this manual can be found in the file "help.txt", |help.txt|.
31 It can be accessed from within Vim with the <Help> or <F1> key and with the
32 |:help| command (just type ":help", without the bars or quotes).
33 The 'helpfile' option can be set to the name of the help file, in case it
34 is not located in the default place. You can jump to subjects like with tags:
35 Use CTRL-] to jump to a subject under the cursor, use CTRL-T to jump back.
37 Throughout this manual the differences between Vi and Vim are mentioned in
38 curly braces, like this: {Vi does not have on-line help}. See |vi_diff.txt|
39 for a summary of the differences between Vim and Vi.
41 This manual refers to Vim on various machines. There may be small differences
42 between different computers and terminals. Besides the remarks given in this
43 document, there is a separate document for each supported system, see
46 This manual is a reference for all the Vim commands and options. This is not
47 an introduction to the use of Vi or Vim, it gets a bit complicated here and
48 there. For beginners, there is a hands-on |tutor|. To learn using Vim, read
49 the user manual |usr_toc.txt|.
52 There are many books on Vi that contain a section for beginners. There are
53 two books I can recommend:
55 "Vim - Vi Improved" by Steve Oualline
57 This is the very first book completely dedicated to Vim. It is very good for
58 beginners. The most often used commands are explained with pictures and
59 examples. The less often used commands are also explained, the more advanced
60 features are summarized. There is a comprehensive index and a quick
61 reference. Parts of this book have been included in the user manual
63 Published by New Riders Publishing. ISBN: 0735710015
64 For more information try one of these:
65 http://iccf-holland.org/click5.html
66 http://www.vim.org/iccf/click5.html
68 "Learning the Vi editor" by Linda Lamb and Arnold Robbins
70 This is a book about Vi that includes a chapter on Vim (in the sixth edition).
71 The first steps in Vi are explained very well. The commands that Vim adds are
72 only briefly mentioned. There is also a German translation.
73 Published by O'Reilly. ISBN: 1-56592-426-6.
75 ==============================================================================
76 2. Vim on the internet *internet*
78 *www* *WWW* *faq* *FAQ* *distribution* *download*
79 The Vim pages contain the most recent information about Vim. They also
80 contain links to the most recent version of Vim. The FAQ is a list of
81 Frequently Asked Questions. Read this if you have problems.
83 VIM home page: http://www.vim.org/
84 VIM FAQ: http://vimdoc.sf.net/
85 Downloading: ftp://ftp.vim.org/pub/vim/MIRRORS
88 Usenet News group where Vim is discussed: *news* *usenet*
90 This group is also for other editors. If you write about Vim, don't forget to
93 *mail-list* *maillist*
94 There are several mailing lists for Vim:
96 For discussions about using existing versions of Vim: Useful mappings,
97 questions, answers, where to get a specific version, etc. There are
98 quite a few people watching this list and answering questions, also
99 for beginners. Don't hesitate to ask your question here.
100 <vim-dev@vim.org> *vim-dev* *vimdev*
101 For discussions about changing Vim: New features, porting, patches,
102 beta-test versions, etc.
103 <vim-announce@vim.org> *vim-announce*
104 Announcements about new versions of Vim; also for beta-test versions
105 and ports to different systems. This is a read-only list.
106 <vim-multibyte@vim.org> *vim-multibyte*
107 For discussions about using and improving the multi-byte aspects of
109 <vim-mac@vim.org> *vim-mac*
110 For discussions about using and improving the Macintosh version of
113 See http://www.vim.org/maillist.php for the latest information.
116 - You can only send messages to these lists if you have subscribed!
117 - You need to send the messages from the same location as where you subscribed
118 from (to avoid spam mail).
119 - Maximum message size is 40000 characters.
122 If you want to join, send a message to
124 Make sure that your "From:" address is correct. Then the list server will
125 give you help on how to subscribe.
127 You can retrieve old messages from the maillist software, and an index of
128 messages. Ask vim-help for instructions.
130 Archives are kept at: *maillist-archive*
131 http://groups.yahoo.com/group/vim
132 http://groups.yahoo.com/group/vimdev
133 http://groups.yahoo.com/group/vimannounce
134 http://groups.yahoo.com/group/vim-multibyte
135 http://groups.yahoo.com/group/vim-mac
138 Additional maillists:
140 <vim-fr@club.voila.fr> *french-maillist*
141 Vim list in the French language. Subscribe by sending a message to
142 <vim-fr-subscribe@club.voila.fr>
143 Or go to http://groups.yahoo.com/group/vim-fr.
146 Bug reports: *bugs* *bug-reports* *bugreport.vim*
148 Send bug reports to: Vim bugs <bugs@vim.org>
149 This is not a maillist but the message is redirected to the Vim maintainer.
150 Please be brief; all the time that is spent on answering mail is subtracted
151 from the time that is spent on improving Vim! Always give a reproducible
152 example and try to find out which settings or other things influence the
153 appearance of the bug. Try different machines, if possible. Send me patches
156 It will help to include information about the version of Vim you are using and
157 your setup. You can get the information with this command: >
158 :so $VIMRUNTIME/bugreport.vim
159 This will create a file "bugreport.txt" in the current directory, with a lot
160 of information of your environment. Before sending this out, check if it
161 doesn't contain any confidential information!
163 If Vim crashes, please try to find out where. You can find help on this here:
166 In case of doubt or when you wonder if the problem has already been fixed but
167 you can't find a fix for it, become a member of the vim-dev maillist and ask
168 your question there. |maillist|
171 Since Vim internally doesn't use dates for editing, there is no year 2000
172 problem to worry about. Vim does use the time in the form of seconds since
173 January 1st 1970. It is used for a time-stamp check of the edited file and
174 the swap file, which is not critical and should only cause warning messages.
176 There might be a year 2038 problem, when the seconds don't fit in a 32 bit int
177 anymore. This depends on the compiler, libraries and operating system.
178 Specifically, time_t and the ctime() function are used. And the time_t is
179 stored in four bytes in the swap file. But that's only used for printing a
180 file date/time for recovery, it will never affect normal editing.
182 The Vim strftime() function directly uses the strftime() system function.
183 localtime() uses the time() system function. getftime() uses the time
184 returned by the stat() system function. If your system libraries are year
185 2000 compliant, Vim is too.
187 The user may create scripts for Vim that use external commands. These might
188 introduce Y2K problems, but those are not really part of Vim itself.
190 ==============================================================================
191 3. Credits *credits* *author* *Bram* *Moolenaar*
193 Most of Vim was written by Bram Moolenaar <Bram@vim.org>.
195 Parts of the documentation come from several Vi manuals, written by:
200 The Vim editor is based on Stevie and includes (ideas from) other software,
201 worked on by the people mentioned here. Other people helped by sending me
202 patches, suggestions and giving feedback about what is good and bad in Vim.
204 Vim would never have become what it is now, without the help of these people!
206 Ron Aaron Win32 GUI changes
207 Zoltan Arpadffy work on VMS port
209 Gert van Antwerpen changes for DJGPP on MS-DOS
210 Berkeley DB(3) ideas for swap file implementation
212 Walter Briscoe Makefile updates, various patches
213 Ralf Brown SPAWNO library for MS-DOS
214 Robert Colon many useful remarks
215 Marcin Dalecki GTK+ GUI port, toolbar icons, gettext()
216 Kayhan Demirel sent me news in Uganda
217 Chris & John Downey xvi (ideas for multi-windows version)
218 Henk Elbers first VMS port
219 Daniel Elstner GTK+ 2 port
220 Eric Fischer Mac port, 'cindent', and other improvements
221 Benji Fisher Answering lots of user questions
222 Bill Foster Athena GUI port
223 Loic Grenie xvim (ideas for multi windows version)
224 Sven Guckes Vim promotor and previous WWW page maintainer
225 Darren Hiebert Exuberant ctags
226 Jason Hildebrand GTK+ 2 port
227 Bruce Hunsaker improvements for VMS port
228 Andy Kahn Cscope support, GTK+ GUI port
229 Oezguer Kesim Maintainer of Vim Mailing Lists
230 Axel Kielhorn work on the Macintosh port
231 Steve Kirkendall Elvis
232 Roger Knobbe original port to Windows NT
233 Sergey Laskavy Vim's help from Moscow
234 Felix von Leitner Maintainer of Vim Mailing Lists
235 David Leonard Port of Python extensions to Unix
236 Avner Lottem Edit in right-to-left windows
237 Flemming Madsen X11 client-server, various features and patches
238 Microsoft Gave me a copy of DevStudio to compile Vim with
239 Paul Moore Python interface extensions, many patches
240 Katsuhito Nagano Work on multi-byte versions
241 Sung-Hyun Nam Work on multi-byte versions
242 Vince Negri Win32 GUI and generic console enhancements
243 Steve Oualline Author of the first Vim book |frombook|
244 George V. Reilly Win32 port, Win32 GUI start-off
245 Stephen Riehm bug collector
246 Stefan Roemer various patches and help to users
247 Ralf Schandl IBM OS/390 port
248 Olaf Seibert DICE and BeBox version, regexp improvements
249 Mortaza Shiran Farsi patches
250 Peter da Silva termlib
251 Paul Slootman OS/2 port
252 Henry Spencer regular expressions
253 Dany St-Amant Macintosh port
255 G. R. (Fred) Walter Stevie
256 Sven Verdoolaege Perl interface
257 Robert Webb Command-line completion, GUI versions, and
259 Ingo Wilken Tcl interface
260 Mike Williams PostScript printing
261 Juergen Weigert Lattice version, AUX improvements, UNIX and
262 MS-DOS ports, autoconf
263 Stefan 'Sec' Zehl Maintainer of vim.org
265 I wish to thank all the people that sent me bug reports and suggestions. The
266 list is too long to mention them all here. Vim would not be the same without
267 the ideas from all these people: They keep Vim alive!
270 In this documentation there are several references to other versions of Vi:
272 Vi "the original". Without further remarks this is the version
273 of Vi that appeared in Sun OS 4.x. ":version" returns
274 "Version 3.7, 6/7/85". Sometimes other versions are referred
275 to. Only runs under Unix. Source code only available with a
276 license. More information on Vi can be found through:
277 http://vi-editor.org [doesn't currently work...]
279 Posix From the IEEE standard 1003.2, Part 2: Shell and utilities.
280 Generally known as "Posix". This is a textual description of
281 how Vi is supposed to work.
282 See |posix-compliance|.
284 Nvi The "New" Vi. The version of Vi that comes with BSD 4.4 and FreeBSD.
285 Very good compatibility with the original Vi, with a few extensions.
286 The version used is 1.79. ":version" returns "Version 1.79
287 (10/23/96)". There has been no release the last few years, although
288 there is a development version 1.81.
289 Source code is freely available.
291 Elvis Another Vi clone, made by Steve Kirkendall. Very compact but isn't
293 The version used is 2.1. It is still being developed. Source code is
296 ==============================================================================
297 4. Notation *notation*
299 When syntax highlighting is used to read this, text that is not typed
300 literally is often highlighted with the Special group. These are items in [],
301 {} and <>, and CTRL-X.
303 Note that Vim uses all possible characters in commands. Sometimes the [], {}
304 and <> are part of what you type, the context should make this clear.
307 [] Characters in square brackets are optional.
309 *count* *[count]* *E489*
310 [count] An optional number that may precede the command to multiply
311 or iterate the command. If no number is given, a count of one
312 is used, unless otherwise noted. Note that in this manual the
313 [count] is not mentioned in the description of the command,
314 but only in the explanation. This was done to make the
315 commands easier to look up. If the 'showcmd' option is on,
316 the (partially) entered count is shown at the bottom of the
317 window. You can use <Del> to erase the last digit (|N<Del>|).
320 ["x] An optional register designation where text can be stored.
321 See |registers|. The x is a single character between 'a' and
322 'z' or 'A' and 'Z' or '"', and in some cases (with the put
323 command) between '0' and '9', '%', '#', or others. The
324 uppercase and lowercase letter designate the same register,
325 but the lowercase letter is used to overwrite the previous
326 register contents, while the uppercase letter is used to
327 append to the previous register contents. Without the ""x" or
328 with """" the stored text is put into the unnamed register.
331 {} Curly braces denote parts of the command which must appear,
332 but which can take a number of different values. The
333 differences between Vim and Vi are also given in curly braces
334 (this will be clear from the context).
337 {char1-char2} A single character from the range char1 to char2. For
338 example: {a-z} is a lowercase letter. Multiple ranges may be
339 concatenated. For example, {a-zA-Z0-9} is any alphanumeric
342 *{motion}* *movement*
343 {motion} A command that moves the cursor. These are explained in
344 |motion.txt|. Examples:
345 w to start of next word
346 b to begin of current word
348 /The<CR> to next occurrence of "The"
349 This is used after an |operator| command to move over the text
350 that is to be operated upon.
351 - If the motion includes a count and the operator also has a
352 count, the two counts are multiplied. For example: "2d3w"
354 - The motion can be backwards, e.g. "db" to delete to the
356 - The motion can also be a mouse click. The mouse is not
357 supported in every terminal though.
358 - The ":omap" command can be used to map characters while an
360 - Ex commands can be used to move the cursor. This can be
361 used to call a function that does some complicated motion.
362 The motion is always characterwise exclusive, no matter
363 what ":" command is used. This means it's impossible to
364 include the last character of a line without the line break
365 (unless 'virtualedit' is set).
366 If the Ex command changes the text before where the operator
367 starts or jumps to another buffer the result is
368 unpredictable. It is possible to change the text further
369 down. Jumping to another buffer is possible if the current
370 buffer is not unloaded.
373 {Visual} A selected text area. It is started with the "v", "V", or
374 CTRL-V command, then any cursor movement command can be used
375 to change the end of the selected text.
376 This is used before an |operator| command to highlight the
377 text that is to be operated upon.
381 <character> A special character from the table below, optionally with
382 modifiers, or a single ASCII character with modifiers.
385 'c' A single ASCII character.
388 CTRL-{char} {char} typed as a control character; that is, typing {char}
389 while holding the CTRL key down. The case of {char} does not
390 matter; thus CTRL-A and CTRL-a are equivalent. But on some
391 terminals, using the SHIFT key will produce another code,
395 'option' An option, or parameter, that can be set to a value, is
396 enclosed in single quotes. See |options|.
399 "command" A reference to a command that you can type is enclosed in
402 *key-notation* *key-codes* *keycodes*
403 These names for keys are used in the documentation. They can also be used
404 with the ":map" command (insert the key name by pressing CTRL-K and then the
405 key you want the name for).
407 notation meaning equivalent decimal value(s) ~
408 -----------------------------------------------------------------------
409 <Nul> zero CTRL-@ 0 (stored as 10) *<Nul>*
410 <BS> backspace CTRL-H 8 *backspace*
411 <Tab> tab CTRL-I 9 *tab* *Tab*
413 <NL> linefeed CTRL-J 10 (used for <Nul>)
414 <FF> formfeed CTRL-L 12 *formfeed*
415 <CR> carriage return CTRL-M 13 *carriage-return*
416 <Return> same as <CR> *<Return>*
417 <Enter> same as <CR> *<Enter>*
418 <Esc> escape CTRL-[ 27 *escape* *<Esc>*
419 <Space> space 32 *space*
420 <lt> less-than < 60 *<lt>*
421 <Bslash> backslash \ 92 *backslash* *<Bslash>*
422 <Bar> vertical bar | 124 *<Bar>*
424 <CSI> command sequence intro ALT-Esc 155 *<CSI>*
425 <xCSI> CSI when typed in the GUI *<xCSI>*
427 <EOL> end-of-line (can be <CR>, <LF> or <CR><LF>,
428 depends on system and 'fileformat') *<EOL>*
430 <Up> cursor-up *cursor-up* *cursor_up*
431 <Down> cursor-down *cursor-down* *cursor_down*
432 <Left> cursor-left *cursor-left* *cursor_left*
433 <Right> cursor-right *cursor-right* *cursor_right*
434 <S-Up> shift-cursor-up
435 <S-Down> shift-cursor-down
436 <S-Left> shift-cursor-left
437 <S-Right> shift-cursor-right
438 <C-Left> control-cursor-left
439 <C-Right> control-cursor-right
440 <F1> - <F12> function keys 1 to 12 *function_key* *function-key*
441 <S-F1> - <S-F12> shift-function keys 1 to 12 *<S-F1>*
447 <PageUp> page-up *page_up* *page-up*
448 <PageDown> page-down *page_down* *page-down*
449 <kHome> keypad home (upper left) *keypad-home*
450 <kEnd> keypad end (lower left) *keypad-end*
451 <kPageUp> keypad page-up (upper right) *keypad-page-up*
452 <kPageDown> keypad page-down (lower right) *keypad-page-down*
453 <kPlus> keypad + *keypad-plus*
454 <kMinus> keypad - *keypad-minus*
455 <kMultiply> keypad * *keypad-multiply*
456 <kDivide> keypad / *keypad-divide*
457 <kEnter> keypad Enter *keypad-enter*
458 <kPoint> keypad Decimal point *keypad-point*
459 <k0> - <k9> keypad 0 to 9 *keypad-0* *keypad-9*
460 <S-...> shift-key *shift* *<S-*
461 <C-...> control-key *control* *ctrl* *<C-*
462 <M-...> alt-key or meta-key *meta* *alt* *<M-*
463 <A-...> same as <M-...> *<A-*
464 <D-...> command-key (Macintosh only) *<D-*
465 <t_xx> key with "xx" entry in termcap
466 -----------------------------------------------------------------------
468 Note: The shifted cursor keys, the help key, and the undo key are only
469 available on a few terminals. On the Amiga, shifted function key 10 produces
470 a code (CSI) that is also used by key sequences. It will be recognized only
471 after typing another key.
473 Note: There are two codes for the delete key. 127 is the decimal ASCII value
474 for the delete key, which is always recognized. Some delete keys send another
475 value, in which case this value is obtained from the termcap entry "kD". Both
476 values have the same effect. Also see |:fixdel|.
478 Note: The keypad keys are used in the same way as the corresponding "normal"
479 keys. For example, <kHome> has the same effect as <Home>. If a keypad key
480 sends the same raw key code as its non-keypad equivalent, it will be
481 recognized as the non-keypad code. For example, when <kHome> sends the same
482 code as <Home>, when pressing <kHome> Vim will think <Home> was pressed.
483 Mapping <kHome> will not work then.
486 Examples are often given in the <> notation. Sometimes this is just to make
487 clear what you need to type, but often it can be typed literally, e.g., with
488 the ":map" command. The rules are:
489 1. Any printable characters are typed directly, except backslash and '<'
490 2. A backslash is represented with "\\", double backslash, or "<Bslash>".
491 3. A real '<' is represented with "\<" or "<lt>". When there is no
492 confusion possible, a '<' can be used directly.
493 4. "<key>" means the special key typed. This is the notation explained in
494 the table above. A few examples:
498 <C-LeftMouse> Control- left mouse click
499 <S-F11> Shifted function key 11
500 <M-a> Meta- a ('a' with bit 8 set)
501 <M-A> Meta- A ('A' with bit 8 set)
502 <t_kd> "kd" termcap entry (cursor down key)
504 If you want to use the full <> notation in Vim, you have to make sure the '<'
505 flag is excluded from 'cpoptions' (when 'compatible' is not set, it already is
508 The <> notation uses <lt> to escape the special meaning of key names. Using a
509 backslash also works, but only when 'cpoptions' does not include the 'B' flag.
511 Examples for mapping CTRL-H to the six characters "<Home>": >
513 :imap <C-H> <lt>Home>
514 The first one only works when the 'B' flag is not in 'cpoptions'. The second
516 To get a literal "<lt>" in a mapping: >
519 For mapping, abbreviation and menu commands you can then copy-paste the
520 examples and use them directly. Or type them literally, including the '<' and
521 '>' characters. This does NOT work for other commands, like ":set" and
524 ==============================================================================
525 5. Modes, introduction *vim-modes-intro* *vim-modes*
527 Vim has six BASIC modes:
529 *Normal* *Normal-mode* *command-mode*
530 Normal mode In Normal mode you can enter all the normal editor
531 commands. If you start the editor you are in this
532 mode (unless you have set the 'insertmode' option,
533 see below). This is also known as command mode.
535 Visual mode This is like Normal mode, but the movement commands
536 extend a highlighted area. When a non-movement
537 command is used, it is executed for the highlighted
538 area. See |Visual-mode|.
539 If the 'showmode' option is on "-- VISUAL --" is shown
540 at the bottom of the window.
542 Select mode This looks most like the MS-Windows selection mode.
543 Typing a printable character deletes the selection
544 and starts Insert mode. See |Select-mode|.
545 If the 'showmode' option is on "-- SELECT --" is shown
546 at the bottom of the window.
548 Insert mode In Insert mode the text you type is inserted into the
549 buffer. See |Insert-mode|.
550 If the 'showmode' option is on "-- INSERT --" is shown
551 at the bottom of the window.
553 Command-line mode In Command-line mode (also called Cmdline mode) you
554 Cmdline mode can enter one line of text at the bottom of the
555 window. This is for the Ex commands, ":", the pattern
556 search commands, "?" and "/", and the filter command,
559 Ex mode Like Command-line mode, but after entering a command
560 you remain in Ex mode. Very limited editing of the
561 command line. |Ex-mode|
563 There are five ADDITIONAL modes. These are variants of the BASIC modes:
565 *Operator-pending* *Operator-pending-mode*
566 Operator-pending mode This is like Normal mode, but after an operator
567 command has started, and Vim is waiting for a {motion}
568 to specify the text that the operator will work on.
570 Replace mode Replace mode is a special case of Insert mode. You
571 can do the same things as in Insert mode, but for
572 each character you enter, one character of the existing
573 text is deleted. See |Replace-mode|.
574 If the 'showmode' option is on "-- REPLACE --" is
575 shown at the bottom of the window.
577 Insert Normal mode Entered when CTRL-O given in Insert mode. This is
578 like Normal mode, but after executing one command Vim
579 returns to Insert mode.
580 If the 'showmode' option is on "-- (insert) --" is
581 shown at the bottom of the window.
583 Insert Visual mode Entered when starting a Visual selection from Insert
584 mode, e.g., by using CTRL-O and then "v", "V" or
585 CTRL-V. When the Visual selection ends, Vim returns
587 If the 'showmode' option is on "-- (insert) VISUAL --"
588 is shown at the bottom of the window.
590 Insert Select mode Entered when starting Select mode from Insert mode.
591 E.g., by dragging the mouse or <S-Right>.
592 When the Select mode ends, Vim returns to Insert mode.
593 If the 'showmode' option is on "-- (insert) SELECT --"
594 is shown at the bottom of the window.
596 ==============================================================================
597 6. Switching from mode to mode *mode-switching*
599 If for any reason you do not know which mode you are in, you can always get
600 back to Normal mode by typing <Esc> twice. This doesn't work for Ex mode
601 though, use ":visual".
602 You will know you are back in Normal mode when you see the screen flash or
603 hear the bell after you type <Esc>. However, when pressing <Esc> after using
604 CTRL-O in Insert mode you get a beep but you are still in Insert mode, type
609 Normal Visual Select Insert Replace Cmd-line Ex ~
611 Normal v V ^V *4 *1 R : / ? ! Q
612 Visual *2 ^G c C -- : --
613 Select *5 ^O ^G *6 -- -- --
614 Insert <Esc> -- -- <Insert> -- --
615 Replace <Esc> -- -- <Insert> -- --
616 Command-line *3 -- -- :start -- --
617 Ex :vi -- -- -- -- --
622 *1 Go from Normal mode to Insert mode by giving the command "i", "I", "a",
623 "A", "o", "O", "c", "C", "s" or S".
624 *2 Go from Visual mode to Normal mode by giving a non-movement command, which
625 causes the command to be executed, or by hitting <Esc> "v", "V" or "CTRL-V"
626 (see |v_v|), which just stops Visual mode without side effects.
627 *3 Go from Command-line mode to Normal mode by:
628 - Hitting <CR> or <NL>, which causes the entered command to be executed.
629 - Deleting the complete line (e.g., with CTRL-U) and giving a final <BS>.
630 - Hitting CTRL-C or <Esc>, which quits the command-line without executing
632 In the last case <Esc> may be the character defined with the 'wildchar'
633 option, in which case it will start command-line completion. You can
634 ignore that and type <Esc> again. {Vi: when hitting <Esc> the command-line
635 is executed. This is unexpected for most people; therefore it was changed
636 in Vim. But when the <Esc> is part of a mapping, the command-line is
637 executed. If you want the Vi behaviour also when typing <Esc>, use ":cmap
639 *4 Go from Normal to Select mode by:
640 - use the mouse to select text while 'selectmode' contains "mouse"
641 - use a non-printable command to move the cursor while keeping the Shift
642 key pressed, and the 'selectmode' option contains "key"
643 - use "v", "V" or "CTRL-V" while 'selectmode' contains "cmd"
644 - use "gh", "gH" or "g CTRL-H" |g_CTRL-H|
645 *5 Go from Select mode to Normal mode by using a non-printable command to move
646 the cursor, without keeping the Shift key pressed.
647 *6 Go from Select mode to Insert mode by typing a printable character. The
648 selection is deleted and the character is inserted.
650 If the 'insertmode' option is on, editing a file will start in Insert mode.
652 *CTRL-\_CTRL-N* *i_CTRL-\_CTRL-N* *c_CTRL-\_CTRL-N* *v_CTRL-\_CTRL-N*
653 Additionally the command CTRL-\ CTRL-N or <C-\><C-N> can be used to go to
654 Normal mode from any other mode. This can be used to make sure Vim is in
655 Normal mode, without causing a beep like <Esc> would. However, this does not
656 work in Ex mode. When used after a command that takes an argument, such as
657 |f| or |m|, the timeout set with 'ttimeoutlen' applies.
659 *CTRL-\_CTRL-G* *i_CTRL-\_CTRL-G* *c_CTRL-\_CTRL-G* *v_CTRL-\_CTRL-G*
660 The command CTRL-\ CTRL-G or <C-\><C-G> can be used to go to Insert mode when
661 'insertmode' is set. Otherwise it goes to Normal mode. This can be used to
662 make sure Vim is in the mode indicated by 'insertmode', without knowing in
663 what mode Vim currently is.
665 *Q* *mode-Ex* *Ex-mode* *Ex* *EX* *E501*
666 Q Switch to "Ex" mode. This is a bit like typing ":"
667 commands one after another, except:
668 - You don't have to keep pressing ":".
669 - The screen doesn't get updated after each command.
670 - There is no normal command-line editing.
671 - Mappings and abbreviations are not used.
672 In fact, you are editing the lines with the "standard"
673 line-input editing commands (<Del> or <BS> to erase,
674 CTRL-U to kill the whole line).
675 Vim will enter this mode by default if it's invoked as
676 "ex" on the command-line.
677 Use the ":vi" command |:visual| to exit "Ex" mode.
678 Note: In older versions of Vim "Q" formatted text,
679 that is now done with |gq|. But if you use the
680 |vimrc_example.vim| script "Q" works like "gq".
683 gQ Switch to "Ex" mode like with "Q", but really behave
684 like typing ":" commands after another. All command
685 line editing, completion etc. is available.
686 Use the ":vi" command |:visual| to exit "Ex" mode.
689 ==============================================================================
690 7. The window contents *window-contents*
692 In Normal mode and Insert/Replace mode the screen window will show the current
693 contents of the buffer: What You See Is What You Get. There are two
695 - When the 'cpoptions' option contains '$', and the change is within one line,
696 the text is not directly deleted, but a '$' is put at the last deleted
698 - When inserting text in one window, other windows on the same text are not
699 updated until the insert is finished.
700 {Vi: The screen is not always updated on slow terminals}
702 Lines longer than the window width will wrap, unless the 'wrap' option is off
703 (see below). The 'linebreak' option can be set to wrap at a blank character.
705 If the window has room after the last line of the buffer, Vim will show '~' in
706 the first column of the last lines in the window, like this: >
708 +-----------------------+
713 +-----------------------+
715 Thus the '~' lines indicate that the end of the buffer was reached.
717 If the last line in a window doesn't fit, Vim will indicate this with a '@' in
718 the first column of the last lines in the window, like this: >
720 +-----------------------+
725 +-----------------------+
727 Thus the '@' lines indicate that there is a line that doesn't fit in the
730 When the "lastline" flag is present in the 'display' option, you will not see
731 '@' characters at the left side of window. If the last line doesn't fit
732 completely, only the part that fits is shown, and the last three characters of
733 the last line are replaced with "@@@", like this: >
735 +-----------------------+
738 |a very long line that d|
739 |oesn't fit in the wi@@@|
740 +-----------------------+
742 If there is a single line that is too long to fit in the window, this is a
743 special situation. Vim will show only part of the line, around where the
744 cursor is. There are no special characters shown, so that you can edit all
746 {Vi: gives an "internal error" on lines that do not fit in the window}
748 The '@' occasion in the 'highlight' option can be used to set special
749 highlighting for the '@' and '~' characters. This makes it possible to
750 distinguish them from real characters in the buffer.
752 The 'showbreak' option contains the string to put in front of wrapped lines.
755 If the 'wrap' option is off, long lines will not wrap. Only the part that
756 fits on the screen is shown. If the cursor is moved to a part of the line
757 that is not shown, the screen is scrolled horizontally. The advantage of
758 this method is that columns are shown as they are and lines that cannot fit
759 on the screen can be edited. The disadvantage is that you cannot see all the
760 characters of a line at once. The 'sidescroll' option can be set to the
761 minimal number of columns to scroll. {Vi: has no 'wrap' option}
763 All normal ASCII characters are displayed directly on the screen. The <Tab>
764 is replaced with the number of spaces that it represents. Other non-printing
765 characters are replaced with "^{char}", where {char} is the non-printing
766 character with 64 added. Thus character 7 (bell) will be shown as "^G".
767 Characters between 127 and 160 are replaced with "~{char}", where {char} is
768 the character with 64 subtracted. These characters occupy more than one
769 position on the screen. The cursor can only be positioned on the first one.
771 If you set the 'number' option, all lines will be preceded with their
772 number. Tip: If you don't like wrapping lines to mix with the line numbers,
773 set the 'showbreak' option to eight spaces:
774 ":set showbreak=\ \ \ \ \ \ \ \ "
776 If you set the 'list' option, <Tab> characters will not be shown as several
777 spaces, but as "^I". A '$' will be placed at the end of the line, so you can
778 find trailing blanks.
780 In Command-line mode only the command-line itself is shown correctly. The
781 display of the buffer contents is updated as soon as you go back to Command
784 The last line of the window is used for status and other messages. The
785 status messages will only be used if an option is on:
787 status message option default Unix default ~
788 current mode 'showmode' on on
789 command characters 'showcmd' on off
790 cursor position 'ruler' off off
792 The current mode is "-- INSERT --" or "-- REPLACE --", see |'showmode'|. The
793 command characters are those that you typed but were not used yet. {Vi: does
794 not show the characters you typed or the cursor position}
796 If you have a slow terminal you can switch off the status messages to speed
800 If there is an error, an error message will be shown for at least one second
801 (in reverse video). {Vi: error messages may be overwritten with other
802 messages before you have a chance to read them}
804 Some commands show how many lines were affected. Above which threshold this
805 happens can be controlled with the 'report' option (default 2).
807 On the Amiga Vim will run in a CLI window. The name Vim and the full name of
808 the current file name will be shown in the title bar. When the window is
809 resized, Vim will automatically redraw the window. You may make the window as
810 small as you like, but if it gets too small not a single line will fit in it.
811 Make it at least 40 characters wide to be able to read most messages on the
814 On most Unix systems, resizing the window is recognized and handled correctly
817 ==============================================================================
818 8. Definitions *definitions*
820 screen The whole area that Vim uses to work in. This can be
821 a terminal emulator window. Also called "the Vim
823 window A view on a buffer.
825 A screen contains one or more windows, separated by status lines and with the
826 command line at the bottom.
828 +-------------------------------+
829 screen | window 1 | window 2 |
832 |= status line =|= status line =|
836 |==== status line ==============|
838 +-------------------------------+
840 The command line is also used for messages. It scrolls up the screen when
841 there is not enough room in the command line.
843 A difference is made between four types of lines:
845 buffer lines The lines in the buffer. This is the same as the
846 lines as they are read from/written to a file. They
847 can be thousands of characters long.
848 logical lines The buffer lines with folding applied. Buffer lines
849 in a closed fold are changed to a single logical line:
850 "+-- 99 lines folded". They can be thousands of
852 window lines The lines displayed in a window: A range of logical
853 lines with wrapping, line breaks, etc. applied. They
854 can only be as long as the width of the window allows,
855 longer lines are wrapped or truncated.
856 screen lines The lines of the screen that Vim uses. Consists of
857 the window lines of all windows, with status lines
858 and the command line added. They can only be as long
859 as the width of the screen allows. When the command
860 line gets longer it wraps and lines are scrolled to
863 buffer lines logical lines window lines screen lines ~
865 1. one 1. one 1. +-- folded 1. +-- folded
866 2. two 2. +-- folded 2. five 2. five
867 3. three 3. five 3. six 3. six
868 4. four 4. six 4. seven 4. seven
869 5. five 5. seven 5. === status line ===
873 1. aaa 1. aaa 1. aaa 9. cc
874 2. bbb 2. bbb 2. bbb 10. ddd
875 3. ccc ccc ccc 3. ccc ccc ccc 3. ccc ccc c 11. ~
876 4. ddd 4. ddd 4. cc 12. === status line ===
877 5. ddd 13. (command line)
880 ==============================================================================
881 vim:tw=78:ts=8:ft=help:norl: