Mercurial > vim
annotate runtime/doc/intro.txt @ 33299:4c975fa0a442 v9.0.1915
patch 9.0.1915: r_CTRL-C works differently in visual mode
Commit: https://github.com/vim/vim/commit/476733f3d06876c7ac105e064108c973a57984d3
Author: Christian Brabandt <cb@256bit.org>
Date: Tue Sep 19 20:41:51 2023 +0200
patch 9.0.1915: r_CTRL-C works differently in visual mode
Problem: r_CTRL-C works differently in visual mode
Solution: Make r_CTRL-C behave consistent in visual mode
in terminal and Windows GUI
in visual mode, r CTRL-C behaves strange in Unix like environments. It
seems to end visual mode, but still is waiting for few more chars,
however it never seems to replace it by any characters and eventually
just returns back into normal mode.
In contrast in Windows GUI mode, r_CTRL-C replaces in the selected area
all characters by a literal CTRL-C.
Not sure why it behaves like this. It seems in the Windows GUI, got_int
is not set and therefore behaves as if any other normal character has
been pressed.
So remove the special casing of what happens when got_int is set and
make it always behave like in Windows GUI mode. Add a test to verify it
always behaves like replacing in the selected area each selected
character by a literal CTRL-C.
closes: #13091
closes: #13112
Signed-off-by: Christian Brabandt <cb@256bit.org>
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Tue, 19 Sep 2023 21:00:03 +0200 |
| parents | 3bc84e3fd05c |
| children | 88cad94caef9 |
| rev | line source |
|---|---|
|
33253
3bc84e3fd05c
runtime(doc): documentation updates
Christian Brabandt <cb@256bit.org>
parents:
32770
diff
changeset
|
1 *intro.txt* For Vim version 9.0. Last change: 2023 Aug 15 |
| 7 | 2 |
| 3 | |
| 4 VIM REFERENCE MANUAL by Bram Moolenaar | |
| 5 | |
| 6 | |
| 7 Introduction to Vim *ref* *reference* | |
| 8 | |
| 9 1. Introduction |intro| | |
| 10 2. Vim on the internet |internet| | |
| 11 3. Credits |credits| | |
| 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| | |
| 17 | |
| 18 ============================================================================== | |
| 19 1. Introduction *intro* | |
| 20 | |
| 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|). | |
| 29 | |
| 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. | |
| 36 | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
15512
diff
changeset
|
37 The differences between Vi and Vim are mentioned in |vi_diff.txt|. |
| 7 | 38 |
| 39 This manual refers to Vim on various machines. There may be small differences | |
| 40 between different computers and terminals. Besides the remarks given in this | |
| 41 document, there is a separate document for each supported system, see | |
| 42 |sys-file-list|. | |
| 43 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
44 *pronounce* |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
45 Vim is pronounced as one word, like Jim, not vi-ai-em. It's written with a |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
46 capital, since it's a name, again like Jim. |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
47 |
| 7 | 48 This manual is a reference for all the Vim commands and options. This is not |
| 49 an introduction to the use of Vi or Vim, it gets a bit complicated here and | |
| 50 there. For beginners, there is a hands-on |tutor|. To learn using Vim, read | |
| 51 the user manual |usr_toc.txt|. | |
| 52 | |
| 15334 | 53 *book* *books* |
| 54 Most books on Vi and Vim contain a section for beginners. Others are spending | |
| 55 more words on specific functionality. You can find an overview of Vim books | |
| 56 here: | |
| 57 http://iccf-holland.org/vim_books.html | |
| 7 | 58 |
| 59 ============================================================================== | |
| 60 2. Vim on the internet *internet* | |
| 61 | |
| 838 | 62 *www* *WWW* *faq* *FAQ* *distribution* *download* |
| 7 | 63 The Vim pages contain the most recent information about Vim. They also |
| 64 contain links to the most recent version of Vim. The FAQ is a list of | |
| 65 Frequently Asked Questions. Read this if you have problems. | |
| 66 | |
| 15334 | 67 Vim home page: https://www.vim.org/ |
| 17161 | 68 Vim FAQ: https://vimhelp.org/vim_faq.txt.html |
| 15334 | 69 Downloading: https://www.vim.org/download.php |
| 7 | 70 |
| 71 | |
| 17261 | 72 Asking questions, finding answers: https://vi.stackexchange.com/ |
| 73 "Vi and Vim Stack Exchange is a question and answer site for people using the | |
| 74 vi and Vim families of text editors" | |
| 75 | |
| 76 | |
| 7 | 77 Usenet News group where Vim is discussed: *news* *usenet* |
| 78 comp.editors | |
| 79 This group is also for other editors. If you write about Vim, don't forget to | |
| 80 mention that. | |
| 17261 | 81 You can access it here: |
| 82 https://groups.google.com/forum/#!topic/comp.editors | |
| 7 | 83 |
| 84 *mail-list* *maillist* | |
| 85 There are several mailing lists for Vim: | |
|
10548
74effdaa369e
Updated runtime files.
Christian Brabandt <cb@256bit.org>
parents:
10228
diff
changeset
|
86 <vim@vim.org> *vim-use* *vim_use* |
| 7 | 87 For discussions about using existing versions of Vim: Useful mappings, |
| 824 | 88 questions, answers, where to get a specific version, etc. There are |
| 89 quite a few people watching this list and answering questions, also | |
| 90 for beginners. Don't hesitate to ask your question here. | |
|
10548
74effdaa369e
Updated runtime files.
Christian Brabandt <cb@256bit.org>
parents:
10228
diff
changeset
|
91 <vim-dev@vim.org> *vim-dev* *vim_dev* *vimdev* |
| 7 | 92 For discussions about changing Vim: New features, porting, patches, |
| 93 beta-test versions, etc. | |
|
10548
74effdaa369e
Updated runtime files.
Christian Brabandt <cb@256bit.org>
parents:
10228
diff
changeset
|
94 <vim-announce@vim.org> *vim-announce* *vim_announce* |
| 7 | 95 Announcements about new versions of Vim; also for beta-test versions |
| 824 | 96 and ports to different systems. This is a read-only list. |
|
10548
74effdaa369e
Updated runtime files.
Christian Brabandt <cb@256bit.org>
parents:
10228
diff
changeset
|
97 <vim-mac@vim.org> *vim-mac* *vim_mac* |
| 7 | 98 For discussions about using and improving the Macintosh version of |
| 99 Vim. | |
| 100 | |
| 101 See http://www.vim.org/maillist.php for the latest information. | |
| 102 | |
| 103 NOTE: | |
| 15334 | 104 - Anyone can see the archive, e.g. on Google groups. Search this if you have |
| 105 questions. | |
| 7 | 106 - You can only send messages to these lists if you have subscribed! |
| 15334 | 107 - The first message is moderated, thus it may take a few hours to show up. |
| 7 | 108 - You need to send the messages from the same location as where you subscribed |
| 109 from (to avoid spam mail). | |
| 110 | |
| 111 *subscribe-maillist* | |
| 112 If you want to join, send a message to | |
| 1624 | 113 <vim-subscribe@vim.org> |
| 7 | 114 Make sure that your "From:" address is correct. Then the list server will |
| 115 give you help on how to subscribe. | |
| 116 | |
| 1624 | 117 *maillist-archive* |
| 118 For more information and archives look on the Vim maillist page: | |
| 119 http://www.vim.org/maillist.php | |
| 7 | 120 |
| 121 | |
| 122 Bug reports: *bugs* *bug-reports* *bugreport.vim* | |
| 123 | |
| 20753 | 124 There are three ways to report bugs: |
| 30875 | 125 1. For issues with runtime files, look in the header for an email address or |
| 126 any other way to report it to the maintainer. | |
| 127 2. Open an issue on GitHub: https://github.com/vim/vim/issues | |
| 20753 | 128 The text will be forwarded to the vim-dev maillist. |
| 129 3. Send bug reports to: Vim Developers <vim-dev@vim.org> | |
|
10228
8a1481e59d64
commit https://github.com/vim/vim/commit/3e496b0ea31996b665824f45664dee1fdd73c4d0
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
130 This is a maillist, you need to become a member first and many people will |
|
8a1481e59d64
commit https://github.com/vim/vim/commit/3e496b0ea31996b665824f45664dee1fdd73c4d0
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
131 see the message. If you don't want that, e.g. because it is a security |
|
32770
4027cefc2aab
Farewell to Bram and dedicate upcoming Vim 9.1 to him (#12749)
Christian Brabandt <cb@256bit.org>
parents:
31200
diff
changeset
|
132 issue, please contact any of the current Vim maintainers |
|
4027cefc2aab
Farewell to Bram and dedicate upcoming Vim 9.1 to him (#12749)
Christian Brabandt <cb@256bit.org>
parents:
31200
diff
changeset
|
133 https://github.com/orgs/vim/people (but not Bram or the vim-dev ML). |
|
4027cefc2aab
Farewell to Bram and dedicate upcoming Vim 9.1 to him (#12749)
Christian Brabandt <cb@256bit.org>
parents:
31200
diff
changeset
|
134 In the future, a proper process for handling security issues will be setup. |
| 5968 | 135 |
| 7 | 136 Please be brief; all the time that is spent on answering mail is subtracted |
| 137 from the time that is spent on improving Vim! Always give a reproducible | |
|
11763
21f3930dfe6e
Documentation updates.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
138 example and try to find out which settings or other things trigger the bug. |
|
21f3930dfe6e
Documentation updates.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
139 |
|
21f3930dfe6e
Documentation updates.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
140 Preferably start Vim with: > |
|
21f3930dfe6e
Documentation updates.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
141 vim --clean -u reproduce.vim |
|
21f3930dfe6e
Documentation updates.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
142 Where reproduce.vim is a script that reproduces the problem. Try different |
|
21f3930dfe6e
Documentation updates.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
143 machines, if relevant (is this an MS-Windows specific bug perhaps?). |
|
21f3930dfe6e
Documentation updates.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
144 |
| 15334 | 145 Send me patches if you can! If you create a pull request on |
| 146 https://github.com/vim/vim then the automated checks will run and report any | |
| 147 obvious problems. But you can also send the patch by email (use an attachment | |
| 148 to avoid white space changes). | |
| 7 | 149 |
| 502 | 150 It will help to include information about the version of Vim you are using and |
| 151 your setup. You can get the information with this command: > | |
| 7 | 152 :so $VIMRUNTIME/bugreport.vim |
| 153 This will create a file "bugreport.txt" in the current directory, with a lot | |
| 154 of information of your environment. Before sending this out, check if it | |
| 155 doesn't contain any confidential information! | |
| 156 | |
| 502 | 157 If Vim crashes, please try to find out where. You can find help on this here: |
| 158 |debug.txt|. | |
| 7 | 159 |
| 502 | 160 In case of doubt or when you wonder if the problem has already been fixed but |
| 161 you can't find a fix for it, become a member of the vim-dev maillist and ask | |
| 162 your question there. |maillist| | |
| 7 | 163 |
| 164 *year-2000* *Y2K* | |
| 165 Since Vim internally doesn't use dates for editing, there is no year 2000 | |
| 166 problem to worry about. Vim does use the time in the form of seconds since | |
| 167 January 1st 1970. It is used for a time-stamp check of the edited file and | |
| 168 the swap file, which is not critical and should only cause warning messages. | |
| 169 | |
| 170 There might be a year 2038 problem, when the seconds don't fit in a 32 bit int | |
| 171 anymore. This depends on the compiler, libraries and operating system. | |
| 172 Specifically, time_t and the ctime() function are used. And the time_t is | |
| 173 stored in four bytes in the swap file. But that's only used for printing a | |
| 174 file date/time for recovery, it will never affect normal editing. | |
| 175 | |
| 176 The Vim strftime() function directly uses the strftime() system function. | |
| 177 localtime() uses the time() system function. getftime() uses the time | |
| 178 returned by the stat() system function. If your system libraries are year | |
| 179 2000 compliant, Vim is too. | |
| 180 | |
| 181 The user may create scripts for Vim that use external commands. These might | |
| 182 introduce Y2K problems, but those are not really part of Vim itself. | |
| 183 | |
| 184 ============================================================================== | |
|
32770
4027cefc2aab
Farewell to Bram and dedicate upcoming Vim 9.1 to him (#12749)
Christian Brabandt <cb@256bit.org>
parents:
31200
diff
changeset
|
185 3. Credits *credits* *author* |
| 7 | 186 |
|
32770
4027cefc2aab
Farewell to Bram and dedicate upcoming Vim 9.1 to him (#12749)
Christian Brabandt <cb@256bit.org>
parents:
31200
diff
changeset
|
187 Most of Vim was created by Bram Moolenaar <Bram@vim.org> |Bram-Moolenaar| |
| 7 | 188 |
| 189 Parts of the documentation come from several Vi manuals, written by: | |
| 190 W.N. Joy | |
| 191 Alan P.W. Hewett | |
| 192 Mark Horton | |
| 193 | |
| 194 The Vim editor is based on Stevie and includes (ideas from) other software, | |
| 195 worked on by the people mentioned here. Other people helped by sending me | |
| 196 patches, suggestions and giving feedback about what is good and bad in Vim. | |
| 197 | |
| 198 Vim would never have become what it is now, without the help of these people! | |
| 199 | |
| 200 Ron Aaron Win32 GUI changes | |
|
2246
1e48f569b03d
Move text from various.txt to a new helphelp.txt help file.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
201 Mohsin Ahmed encryption |
| 7 | 202 Zoltan Arpadffy work on VMS port |
| 203 Tony Andrews Stevie | |
| 204 Gert van Antwerpen changes for DJGPP on MS-DOS | |
| 205 Berkeley DB(3) ideas for swap file implementation | |
| 206 Keith Bostic Nvi | |
| 207 Walter Briscoe Makefile updates, various patches | |
| 208 Ralf Brown SPAWNO library for MS-DOS | |
| 209 Robert Colon many useful remarks | |
| 210 Marcin Dalecki GTK+ GUI port, toolbar icons, gettext() | |
| 211 Kayhan Demirel sent me news in Uganda | |
| 212 Chris & John Downey xvi (ideas for multi-windows version) | |
| 213 Henk Elbers first VMS port | |
| 29 | 214 Daniel Elstner GTK+ 2 port |
| 7 | 215 Eric Fischer Mac port, 'cindent', and other improvements |
| 216 Benji Fisher Answering lots of user questions | |
| 28379 | 217 Bill Foster Athena GUI port (later removed) |
|
33253
3bc84e3fd05c
runtime(doc): documentation updates
Christian Brabandt <cb@256bit.org>
parents:
32770
diff
changeset
|
218 Google Let Bram work on Vim one day a week |
| 7 | 219 Loic Grenie xvim (ideas for multi windows version) |
|
32770
4027cefc2aab
Farewell to Bram and dedicate upcoming Vim 9.1 to him (#12749)
Christian Brabandt <cb@256bit.org>
parents:
31200
diff
changeset
|
220 Sven Guckes Vim promoter and previous WWW page maintainer |Sven-Guckes| |
| 7 | 221 Darren Hiebert Exuberant ctags |
| 29 | 222 Jason Hildebrand GTK+ 2 port |
| 7 | 223 Bruce Hunsaker improvements for VMS port |
| 224 Andy Kahn Cscope support, GTK+ GUI port | |
| 225 Oezguer Kesim Maintainer of Vim Mailing Lists | |
| 226 Axel Kielhorn work on the Macintosh port | |
| 227 Steve Kirkendall Elvis | |
| 228 Roger Knobbe original port to Windows NT | |
| 229 Sergey Laskavy Vim's help from Moscow | |
| 1624 | 230 Felix von Leitner Previous maintainer of Vim Mailing Lists |
| 7 | 231 David Leonard Port of Python extensions to Unix |
| 232 Avner Lottem Edit in right-to-left windows | |
| 233 Flemming Madsen X11 client-server, various features and patches | |
|
2246
1e48f569b03d
Move text from various.txt to a new helphelp.txt help file.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
234 Tony Mechelynck answers many user questions |
| 7 | 235 Paul Moore Python interface extensions, many patches |
| 21991 | 236 Katsuhito Nagano Work on multibyte versions |
| 237 Sung-Hyun Nam Work on multibyte versions | |
| 7 | 238 Vince Negri Win32 GUI and generic console enhancements |
| 239 Steve Oualline Author of the first Vim book |frombook| | |
| 18615 | 240 Dominique Pelle Valgrind reports and many fixes |
| 1624 | 241 A.Politz Many bug reports and some fixes |
| 7 | 242 George V. Reilly Win32 port, Win32 GUI start-off |
| 243 Stephen Riehm bug collector | |
| 244 Stefan Roemer various patches and help to users | |
| 245 Ralf Schandl IBM OS/390 port | |
| 246 Olaf Seibert DICE and BeBox version, regexp improvements | |
| 247 Mortaza Shiran Farsi patches | |
| 248 Peter da Silva termlib | |
| 249 Paul Slootman OS/2 port | |
| 250 Henry Spencer regular expressions | |
| 251 Dany St-Amant Macintosh port | |
| 252 Tim Thompson Stevie | |
| 253 G. R. (Fred) Walter Stevie | |
| 254 Sven Verdoolaege Perl interface | |
| 255 Robert Webb Command-line completion, GUI versions, and | |
| 256 lots of patches | |
| 257 Ingo Wilken Tcl interface | |
| 258 Mike Williams PostScript printing | |
| 259 Juergen Weigert Lattice version, AUX improvements, UNIX and | |
| 260 MS-DOS ports, autoconf | |
| 261 Stefan 'Sec' Zehl Maintainer of vim.org | |
| 12499 | 262 Yasuhiro Matsumoto many MS-Windows improvements |
| 263 Ken Takata fixes and features | |
| 264 Kazunobu Kuriyama GTK 3 | |
| 265 Christian Brabandt many fixes, features, user support, etc. | |
| 15334 | 266 Yegappan Lakshmanan many quickfix features |
| 7 | 267 |
| 268 I wish to thank all the people that sent me bug reports and suggestions. The | |
| 269 list is too long to mention them all here. Vim would not be the same without | |
| 270 the ideas from all these people: They keep Vim alive! | |
| 4992 | 271 *love* *peace* *friendship* *gross-national-happiness* |
| 7 | 272 |
| 273 | |
| 274 In this documentation there are several references to other versions of Vi: | |
| 39 | 275 *Vi* *vi* |
| 7 | 276 Vi "the original". Without further remarks this is the version |
| 277 of Vi that appeared in Sun OS 4.x. ":version" returns | |
| 278 "Version 3.7, 6/7/85". Sometimes other versions are referred | |
| 15512 | 279 to. Only runs under Unix. Source code is now available under a |
| 280 BSD-style license. More information on Vi can be found through: | |
| 281 http://ex-vi.sourceforge.net/ | |
| 7 | 282 *Posix* |
| 283 Posix From the IEEE standard 1003.2, Part 2: Shell and utilities. | |
| 284 Generally known as "Posix". This is a textual description of | |
| 285 how Vi is supposed to work. | |
| 161 | 286 See |posix-compliance|. |
| 7 | 287 *Nvi* |
| 288 Nvi The "New" Vi. The version of Vi that comes with BSD 4.4 and FreeBSD. | |
| 289 Very good compatibility with the original Vi, with a few extensions. | |
| 290 The version used is 1.79. ":version" returns "Version 1.79 | |
| 291 (10/23/96)". There has been no release the last few years, although | |
| 292 there is a development version 1.81. | |
| 293 Source code is freely available. | |
| 294 *Elvis* | |
| 295 Elvis Another Vi clone, made by Steve Kirkendall. Very compact but isn't | |
| 15512 | 296 as flexible as Vim. Development has stalled, Elvis has left the |
| 297 building! Source code is freely available. | |
| 298 *Neovim* | |
| 299 Neovim A Vim clone. Forked the Vim source in 2014 and went a different way. | |
| 15334 | 300 Very much bound to github and has many more dependencies, making |
| 301 development more complex and limiting portability. Code has been | |
| 302 refactored, resulting in patches not being exchangeable with Vim. | |
| 303 Supports a remote GUI and integration with scripting languages. | |
| 7 | 304 |
| 305 ============================================================================== | |
| 306 4. Notation *notation* | |
| 307 | |
| 308 When syntax highlighting is used to read this, text that is not typed | |
| 309 literally is often highlighted with the Special group. These are items in [], | |
| 310 {} and <>, and CTRL-X. | |
| 311 | |
| 312 Note that Vim uses all possible characters in commands. Sometimes the [], {} | |
| 313 and <> are part of what you type, the context should make this clear. | |
| 314 | |
| 315 | |
| 316 [] Characters in square brackets are optional. | |
| 317 | |
| 2596 | 318 *count* *[count]* |
| 7 | 319 [count] An optional number that may precede the command to multiply |
| 320 or iterate the command. If no number is given, a count of one | |
| 321 is used, unless otherwise noted. Note that in this manual the | |
| 322 [count] is not mentioned in the description of the command, | |
| 323 but only in the explanation. This was done to make the | |
| 324 commands easier to look up. If the 'showcmd' option is on, | |
| 325 the (partially) entered count is shown at the bottom of the | |
| 326 window. You can use <Del> to erase the last digit (|N<Del>|). | |
| 327 | |
| 328 *[quotex]* | |
| 329 ["x] An optional register designation where text can be stored. | |
| 330 See |registers|. The x is a single character between 'a' and | |
| 331 'z' or 'A' and 'Z' or '"', and in some cases (with the put | |
| 237 | 332 command) between '0' and '9', '%', '#', or others. The |
| 7 | 333 uppercase and lowercase letter designate the same register, |
| 334 but the lowercase letter is used to overwrite the previous | |
| 335 register contents, while the uppercase letter is used to | |
| 237 | 336 append to the previous register contents. Without the ""x" or |
| 7 | 337 with """" the stored text is put into the unnamed register. |
| 338 | |
| 339 *{}* | |
| 340 {} Curly braces denote parts of the command which must appear, | |
| 341 but which can take a number of different values. The | |
| 342 differences between Vim and Vi are also given in curly braces | |
| 343 (this will be clear from the context). | |
| 344 | |
| 345 *{char1-char2}* | |
| 346 {char1-char2} A single character from the range char1 to char2. For | |
| 347 example: {a-z} is a lowercase letter. Multiple ranges may be | |
| 348 concatenated. For example, {a-zA-Z0-9} is any alphanumeric | |
| 349 character. | |
| 350 | |
| 36 | 351 *{motion}* *movement* |
| 7 | 352 {motion} A command that moves the cursor. These are explained in |
| 353 |motion.txt|. Examples: | |
| 354 w to start of next word | |
| 355 b to begin of current word | |
| 356 4j four lines down | |
| 357 /The<CR> to next occurrence of "The" | |
| 358 This is used after an |operator| command to move over the text | |
| 359 that is to be operated upon. | |
| 360 - If the motion includes a count and the operator also has a | |
| 361 count, the two counts are multiplied. For example: "2d3w" | |
| 362 deletes six words. | |
| 363 - The motion can be backwards, e.g. "db" to delete to the | |
| 364 start of the word. | |
| 365 - The motion can also be a mouse click. The mouse is not | |
| 366 supported in every terminal though. | |
| 367 - The ":omap" command can be used to map characters while an | |
| 368 operator is pending. | |
| 369 - Ex commands can be used to move the cursor. This can be | |
| 370 used to call a function that does some complicated motion. | |
| 371 The motion is always characterwise exclusive, no matter | |
| 372 what ":" command is used. This means it's impossible to | |
| 373 include the last character of a line without the line break | |
| 374 (unless 'virtualedit' is set). | |
| 375 If the Ex command changes the text before where the operator | |
| 376 starts or jumps to another buffer the result is | |
| 377 unpredictable. It is possible to change the text further | |
| 378 down. Jumping to another buffer is possible if the current | |
| 379 buffer is not unloaded. | |
| 380 | |
| 381 *{Visual}* | |
| 382 {Visual} A selected text area. It is started with the "v", "V", or | |
| 383 CTRL-V command, then any cursor movement command can be used | |
| 384 to change the end of the selected text. | |
| 385 This is used before an |operator| command to highlight the | |
| 386 text that is to be operated upon. | |
| 387 See |Visual-mode|. | |
| 388 | |
| 389 *<character>* | |
| 390 <character> A special character from the table below, optionally with | |
| 391 modifiers, or a single ASCII character with modifiers. | |
| 392 | |
| 393 *'character'* | |
| 394 'c' A single ASCII character. | |
| 395 | |
| 396 *CTRL-{char}* | |
| 397 CTRL-{char} {char} typed as a control character; that is, typing {char} | |
| 398 while holding the CTRL key down. The case of {char} does not | |
| 399 matter; thus CTRL-A and CTRL-a are equivalent. But on some | |
| 400 terminals, using the SHIFT key will produce another code, | |
| 401 don't use it then. | |
| 402 | |
| 403 *'option'* | |
| 404 'option' An option, or parameter, that can be set to a value, is | |
| 405 enclosed in single quotes. See |options|. | |
| 406 | |
| 407 *quotecommandquote* | |
| 408 "command" A reference to a command that you can type is enclosed in | |
| 409 double quotes. | |
| 4119 | 410 `command` New style command, this distinguishes it from other quoted |
| 411 text and strings. | |
| 7 | 412 |
| 413 *key-notation* *key-codes* *keycodes* | |
| 414 These names for keys are used in the documentation. They can also be used | |
| 415 with the ":map" command (insert the key name by pressing CTRL-K and then the | |
| 416 key you want the name for). | |
| 417 | |
| 418 notation meaning equivalent decimal value(s) ~ | |
| 419 ----------------------------------------------------------------------- | |
| 420 <Nul> zero CTRL-@ 0 (stored as 10) *<Nul>* | |
| 421 <BS> backspace CTRL-H 8 *backspace* | |
| 422 <Tab> tab CTRL-I 9 *tab* *Tab* | |
| 423 *linefeed* | |
| 424 <NL> linefeed CTRL-J 10 (used for <Nul>) | |
| 425 <CR> carriage return CTRL-M 13 *carriage-return* | |
| 426 <Return> same as <CR> *<Return>* | |
| 427 <Enter> same as <CR> *<Enter>* | |
| 428 <Esc> escape CTRL-[ 27 *escape* *<Esc>* | |
| 429 <Space> space 32 *space* | |
| 430 <lt> less-than < 60 *<lt>* | |
| 431 <Bslash> backslash \ 92 *backslash* *<Bslash>* | |
| 432 <Bar> vertical bar | 124 *<Bar>* | |
| 433 <Del> delete 127 | |
| 434 <CSI> command sequence intro ALT-Esc 155 *<CSI>* | |
| 435 <xCSI> CSI when typed in the GUI *<xCSI>* | |
| 436 | |
| 23305 | 437 <EOL> end-of-line (can be <CR>, <NL> or <CR><NL>, |
| 7 | 438 depends on system and 'fileformat') *<EOL>* |
| 439 | |
| 440 <Up> cursor-up *cursor-up* *cursor_up* | |
| 441 <Down> cursor-down *cursor-down* *cursor_down* | |
| 442 <Left> cursor-left *cursor-left* *cursor_left* | |
| 443 <Right> cursor-right *cursor-right* *cursor_right* | |
| 444 <S-Up> shift-cursor-up | |
| 445 <S-Down> shift-cursor-down | |
| 446 <S-Left> shift-cursor-left | |
| 447 <S-Right> shift-cursor-right | |
| 448 <C-Left> control-cursor-left | |
| 449 <C-Right> control-cursor-right | |
| 450 <F1> - <F12> function keys 1 to 12 *function_key* *function-key* | |
| 451 <S-F1> - <S-F12> shift-function keys 1 to 12 *<S-F1>* | |
| 452 <Help> help key | |
| 453 <Undo> undo key | |
| 454 <Insert> insert key | |
| 455 <Home> home *home* | |
| 456 <End> end *end* | |
| 457 <PageUp> page-up *page_up* *page-up* | |
| 458 <PageDown> page-down *page_down* *page-down* | |
| 459 <kHome> keypad home (upper left) *keypad-home* | |
| 460 <kEnd> keypad end (lower left) *keypad-end* | |
| 461 <kPageUp> keypad page-up (upper right) *keypad-page-up* | |
| 462 <kPageDown> keypad page-down (lower right) *keypad-page-down* | |
| 463 <kPlus> keypad + *keypad-plus* | |
| 464 <kMinus> keypad - *keypad-minus* | |
| 465 <kMultiply> keypad * *keypad-multiply* | |
| 466 <kDivide> keypad / *keypad-divide* | |
| 467 <kEnter> keypad Enter *keypad-enter* | |
| 468 <kPoint> keypad Decimal point *keypad-point* | |
| 469 <k0> - <k9> keypad 0 to 9 *keypad-0* *keypad-9* | |
| 470 <S-...> shift-key *shift* *<S-* | |
| 471 <C-...> control-key *control* *ctrl* *<C-* | |
| 472 <M-...> alt-key or meta-key *meta* *alt* *<M-* | |
| 473 <A-...> same as <M-...> *<A-* | |
| 474 <D-...> command-key (Macintosh only) *<D-* | |
| 475 <t_xx> key with "xx" entry in termcap | |
| 476 ----------------------------------------------------------------------- | |
| 477 | |
| 478 Note: The shifted cursor keys, the help key, and the undo key are only | |
| 479 available on a few terminals. On the Amiga, shifted function key 10 produces | |
| 480 a code (CSI) that is also used by key sequences. It will be recognized only | |
| 481 after typing another key. | |
| 482 | |
| 483 Note: There are two codes for the delete key. 127 is the decimal ASCII value | |
| 484 for the delete key, which is always recognized. Some delete keys send another | |
| 485 value, in which case this value is obtained from the termcap entry "kD". Both | |
| 486 values have the same effect. Also see |:fixdel|. | |
| 487 | |
| 488 Note: The keypad keys are used in the same way as the corresponding "normal" | |
| 489 keys. For example, <kHome> has the same effect as <Home>. If a keypad key | |
| 490 sends the same raw key code as its non-keypad equivalent, it will be | |
| 491 recognized as the non-keypad code. For example, when <kHome> sends the same | |
| 492 code as <Home>, when pressing <kHome> Vim will think <Home> was pressed. | |
| 493 Mapping <kHome> will not work then. | |
| 494 | |
| 495 *<>* | |
| 496 Examples are often given in the <> notation. Sometimes this is just to make | |
| 497 clear what you need to type, but often it can be typed literally, e.g., with | |
| 498 the ":map" command. The rules are: | |
| 499 1. Any printable characters are typed directly, except backslash and '<' | |
| 500 2. A backslash is represented with "\\", double backslash, or "<Bslash>". | |
| 501 3. A real '<' is represented with "\<" or "<lt>". When there is no | |
| 502 confusion possible, a '<' can be used directly. | |
| 503 4. "<key>" means the special key typed. This is the notation explained in | |
| 504 the table above. A few examples: | |
| 505 <Esc> Escape key | |
| 506 <C-G> CTRL-G | |
| 507 <Up> cursor up key | |
| 508 <C-LeftMouse> Control- left mouse click | |
| 509 <S-F11> Shifted function key 11 | |
| 510 <M-a> Meta- a ('a' with bit 8 set) | |
| 511 <M-A> Meta- A ('A' with bit 8 set) | |
| 512 <t_kd> "kd" termcap entry (cursor down key) | |
| 21991 | 513 Although you can specify <M-{char}> with {char} being a multibyte |
| 17758 | 514 character, Vim may not be able to know what byte sequence that is and then |
| 515 it won't work. | |
| 7 | 516 |
| 517 If you want to use the full <> notation in Vim, you have to make sure the '<' | |
| 518 flag is excluded from 'cpoptions' (when 'compatible' is not set, it already is | |
| 519 by default). > | |
| 520 :set cpo-=< | |
| 521 The <> notation uses <lt> to escape the special meaning of key names. Using a | |
| 522 backslash also works, but only when 'cpoptions' does not include the 'B' flag. | |
| 523 | |
| 524 Examples for mapping CTRL-H to the six characters "<Home>": > | |
| 525 :imap <C-H> \<Home> | |
| 526 :imap <C-H> <lt>Home> | |
| 527 The first one only works when the 'B' flag is not in 'cpoptions'. The second | |
| 528 one always works. | |
| 529 To get a literal "<lt>" in a mapping: > | |
| 530 :map <C-L> <lt>lt> | |
| 531 | |
| 532 For mapping, abbreviation and menu commands you can then copy-paste the | |
| 533 examples and use them directly. Or type them literally, including the '<' and | |
| 534 '>' characters. This does NOT work for other commands, like ":set" and | |
| 535 ":autocmd"! | |
| 536 | |
| 30324 | 537 The notation can be used in a double quoted strings, using "\<" at the start, |
| 538 e.g. "\<C-Space>". This results in a special key code. To convert this back | |
| 539 to readable text use `keytrans()`. | |
| 540 | |
| 7 | 541 ============================================================================== |
| 542 5. Modes, introduction *vim-modes-intro* *vim-modes* | |
| 543 | |
| 12045 | 544 Vim has seven BASIC modes: |
| 7 | 545 |
| 546 *Normal* *Normal-mode* *command-mode* | |
| 547 Normal mode In Normal mode you can enter all the normal editor | |
| 548 commands. If you start the editor you are in this | |
| 549 mode (unless you have set the 'insertmode' option, | |
| 550 see below). This is also known as command mode. | |
| 551 | |
| 552 Visual mode This is like Normal mode, but the movement commands | |
| 553 extend a highlighted area. When a non-movement | |
| 554 command is used, it is executed for the highlighted | |
| 555 area. See |Visual-mode|. | |
| 556 If the 'showmode' option is on "-- VISUAL --" is shown | |
| 557 at the bottom of the window. | |
| 558 | |
| 559 Select mode This looks most like the MS-Windows selection mode. | |
| 560 Typing a printable character deletes the selection | |
| 561 and starts Insert mode. See |Select-mode|. | |
| 562 If the 'showmode' option is on "-- SELECT --" is shown | |
| 563 at the bottom of the window. | |
| 564 | |
| 565 Insert mode In Insert mode the text you type is inserted into the | |
| 566 buffer. See |Insert-mode|. | |
| 567 If the 'showmode' option is on "-- INSERT --" is shown | |
| 568 at the bottom of the window. | |
| 569 | |
| 570 Command-line mode In Command-line mode (also called Cmdline mode) you | |
| 571 Cmdline mode can enter one line of text at the bottom of the | |
| 572 window. This is for the Ex commands, ":", the pattern | |
| 573 search commands, "?" and "/", and the filter command, | |
| 574 "!". |Cmdline-mode| | |
| 575 | |
| 576 Ex mode Like Command-line mode, but after entering a command | |
| 577 you remain in Ex mode. Very limited editing of the | |
| 578 command line. |Ex-mode| | |
| 579 | |
| 12045 | 580 Terminal-Job mode Interacting with a job in a terminal window. Typed |
| 581 keys go to the job and the job output is displayed in | |
| 582 the terminal window. See |terminal| about how to | |
| 583 switch to other modes. | |
| 584 | |
| 11914 | 585 There are seven ADDITIONAL modes. These are variants of the BASIC modes: |
| 7 | 586 |
| 587 *Operator-pending* *Operator-pending-mode* | |
| 588 Operator-pending mode This is like Normal mode, but after an operator | |
| 589 command has started, and Vim is waiting for a {motion} | |
| 590 to specify the text that the operator will work on. | |
| 591 | |
| 592 Replace mode Replace mode is a special case of Insert mode. You | |
| 593 can do the same things as in Insert mode, but for | |
| 594 each character you enter, one character of the existing | |
| 595 text is deleted. See |Replace-mode|. | |
| 596 If the 'showmode' option is on "-- REPLACE --" is | |
| 597 shown at the bottom of the window. | |
| 598 | |
| 1624 | 599 Virtual Replace mode Virtual Replace mode is similar to Replace mode, but |
| 600 instead of file characters you are replacing screen | |
| 601 real estate. See |Virtual-Replace-mode|. | |
| 602 If the 'showmode' option is on "-- VREPLACE --" is | |
| 603 shown at the bottom of the window. | |
| 604 | |
| 14519 | 605 Insert Normal mode Entered when CTRL-O is typed in Insert mode (see |
| 606 |i_CTRL-O|). This is like Normal mode, but after | |
| 607 executing one command Vim returns to Insert mode. | |
| 7 | 608 If the 'showmode' option is on "-- (insert) --" is |
| 609 shown at the bottom of the window. | |
| 610 | |
| 12045 | 611 Terminal-Normal mode Using Normal mode in a terminal window. Making |
| 612 changes is impossible. Use an insert command, such as | |
| 613 "a" or "i", to return to Terminal-Job mode. | |
| 11914 | 614 |
| 7 | 615 Insert Visual mode Entered when starting a Visual selection from Insert |
| 616 mode, e.g., by using CTRL-O and then "v", "V" or | |
| 617 CTRL-V. When the Visual selection ends, Vim returns | |
| 618 to Insert mode. | |
| 619 If the 'showmode' option is on "-- (insert) VISUAL --" | |
| 620 is shown at the bottom of the window. | |
| 621 | |
| 622 Insert Select mode Entered when starting Select mode from Insert mode. | |
| 623 E.g., by dragging the mouse or <S-Right>. | |
| 624 When the Select mode ends, Vim returns to Insert mode. | |
| 625 If the 'showmode' option is on "-- (insert) SELECT --" | |
| 626 is shown at the bottom of the window. | |
| 627 | |
| 628 ============================================================================== | |
| 629 6. Switching from mode to mode *mode-switching* | |
| 630 | |
| 631 If for any reason you do not know which mode you are in, you can always get | |
| 632 back to Normal mode by typing <Esc> twice. This doesn't work for Ex mode | |
| 633 though, use ":visual". | |
| 634 You will know you are back in Normal mode when you see the screen flash or | |
| 635 hear the bell after you type <Esc>. However, when pressing <Esc> after using | |
| 636 CTRL-O in Insert mode you get a beep but you are still in Insert mode, type | |
| 637 <Esc> again. | |
| 638 | |
| 639 *i_esc* | |
| 640 TO mode ~ | |
| 641 Normal Visual Select Insert Replace Cmd-line Ex ~ | |
| 642 FROM mode ~ | |
| 1624 | 643 Normal v V ^V *4 *1 R gR : / ? ! Q |
| 7 | 644 Visual *2 ^G c C -- : -- |
| 645 Select *5 ^O ^G *6 -- -- -- | |
| 646 Insert <Esc> -- -- <Insert> -- -- | |
| 647 Replace <Esc> -- -- <Insert> -- -- | |
| 648 Command-line *3 -- -- :start -- -- | |
| 649 Ex :vi -- -- -- -- -- | |
| 650 | |
| 651 -- not possible | |
| 652 | |
| 653 *1 Go from Normal mode to Insert mode by giving the command "i", "I", "a", | |
| 654 "A", "o", "O", "c", "C", "s" or S". | |
| 655 *2 Go from Visual mode to Normal mode by giving a non-movement command, which | |
| 656 causes the command to be executed, or by hitting <Esc> "v", "V" or "CTRL-V" | |
| 657 (see |v_v|), which just stops Visual mode without side effects. | |
| 658 *3 Go from Command-line mode to Normal mode by: | |
| 659 - Hitting <CR> or <NL>, which causes the entered command to be executed. | |
| 660 - Deleting the complete line (e.g., with CTRL-U) and giving a final <BS>. | |
| 661 - Hitting CTRL-C or <Esc>, which quits the command-line without executing | |
| 662 the command. | |
| 663 In the last case <Esc> may be the character defined with the 'wildchar' | |
| 664 option, in which case it will start command-line completion. You can | |
| 16610 | 665 ignore that and type <Esc> again. |
| 7 | 666 *4 Go from Normal to Select mode by: |
| 667 - use the mouse to select text while 'selectmode' contains "mouse" | |
| 668 - use a non-printable command to move the cursor while keeping the Shift | |
| 669 key pressed, and the 'selectmode' option contains "key" | |
| 670 - use "v", "V" or "CTRL-V" while 'selectmode' contains "cmd" | |
| 671 - use "gh", "gH" or "g CTRL-H" |g_CTRL-H| | |
| 672 *5 Go from Select mode to Normal mode by using a non-printable command to move | |
| 673 the cursor, without keeping the Shift key pressed. | |
| 674 *6 Go from Select mode to Insert mode by typing a printable character. The | |
| 675 selection is deleted and the character is inserted. | |
| 676 | |
| 677 If the 'insertmode' option is on, editing a file will start in Insert mode. | |
| 678 | |
| 679 *CTRL-\_CTRL-N* *i_CTRL-\_CTRL-N* *c_CTRL-\_CTRL-N* *v_CTRL-\_CTRL-N* | |
| 680 Additionally the command CTRL-\ CTRL-N or <C-\><C-N> can be used to go to | |
| 681 Normal mode from any other mode. This can be used to make sure Vim is in | |
| 682 Normal mode, without causing a beep like <Esc> would. However, this does not | |
| 683 work in Ex mode. When used after a command that takes an argument, such as | |
| 684 |f| or |m|, the timeout set with 'ttimeoutlen' applies. | |
| 23466 | 685 When focus is in a terminal window, CTRL-\ CTRL-N goes to Normal mode until an |
| 686 edit command is entered, see |t_CTRL-\_CTRL-N|. | |
| 7 | 687 |
| 688 *CTRL-\_CTRL-G* *i_CTRL-\_CTRL-G* *c_CTRL-\_CTRL-G* *v_CTRL-\_CTRL-G* | |
| 689 The command CTRL-\ CTRL-G or <C-\><C-G> can be used to go to Insert mode when | |
| 690 'insertmode' is set. Otherwise it goes to Normal mode. This can be used to | |
| 691 make sure Vim is in the mode indicated by 'insertmode', without knowing in | |
| 692 what mode Vim currently is. | |
| 693 | |
| 694 *Q* *mode-Ex* *Ex-mode* *Ex* *EX* *E501* | |
| 695 Q Switch to "Ex" mode. This is a bit like typing ":" | |
| 696 commands one after another, except: | |
| 697 - You don't have to keep pressing ":". | |
| 698 - The screen doesn't get updated after each command. | |
| 699 - There is no normal command-line editing. | |
| 700 - Mappings and abbreviations are not used. | |
| 701 In fact, you are editing the lines with the "standard" | |
| 702 line-input editing commands (<Del> or <BS> to erase, | |
| 703 CTRL-U to kill the whole line). | |
| 704 Vim will enter this mode by default if it's invoked as | |
| 29403 | 705 "ex" on the command-line or the |-e| command line |
| 706 argument was used. | |
| 7 | 707 Use the ":vi" command |:visual| to exit "Ex" mode. |
| 708 Note: In older versions of Vim "Q" formatted text, | |
| 709 that is now done with |gq|. But if you use the | |
| 28010 | 710 |vimrc_example.vim| script or |defaults.vim|, "Q" |
| 711 works like "gq". Except for Select mode. | |
| 7 | 712 |
| 713 *gQ* | |
| 161 | 714 gQ Switch to "Ex" mode like with "Q", but really behave |
| 715 like typing ":" commands after another. All command | |
| 716 line editing, completion etc. is available. | |
| 29403 | 717 Use the `:vi` command (`:visual`) to exit "Ex" mode. |
| 7 | 718 |
| 719 ============================================================================== | |
| 720 7. The window contents *window-contents* | |
| 721 | |
| 722 In Normal mode and Insert/Replace mode the screen window will show the current | |
| 723 contents of the buffer: What You See Is What You Get. There are two | |
| 724 exceptions: | |
| 725 - When the 'cpoptions' option contains '$', and the change is within one line, | |
| 726 the text is not directly deleted, but a '$' is put at the last deleted | |
| 727 character. | |
| 728 - When inserting text in one window, other windows on the same text are not | |
| 729 updated until the insert is finished. | |
| 730 | |
| 731 Lines longer than the window width will wrap, unless the 'wrap' option is off | |
| 732 (see below). The 'linebreak' option can be set to wrap at a blank character. | |
| 733 | |
| 734 If the window has room after the last line of the buffer, Vim will show '~' in | |
| 2642 | 735 the first column of the last lines in the window, like this: |
| 7 | 736 |
| 737 +-----------------------+ | |
| 738 |some line | | |
| 739 |last line | | |
| 740 |~ | | |
| 741 |~ | | |
| 742 +-----------------------+ | |
| 743 | |
| 744 Thus the '~' lines indicate that the end of the buffer was reached. | |
| 745 | |
| 746 If the last line in a window doesn't fit, Vim will indicate this with a '@' in | |
| 2642 | 747 the first column of the last lines in the window, like this: |
| 7 | 748 |
| 749 +-----------------------+ | |
| 750 |first line | | |
| 751 |second line | | |
| 752 |@ | | |
| 753 |@ | | |
| 754 +-----------------------+ | |
| 755 | |
| 756 Thus the '@' lines indicate that there is a line that doesn't fit in the | |
| 757 window. | |
| 758 | |
| 759 When the "lastline" flag is present in the 'display' option, you will not see | |
| 760 '@' characters at the left side of window. If the last line doesn't fit | |
| 761 completely, only the part that fits is shown, and the last three characters of | |
| 2662 | 762 the last line are replaced with "@@@", like this: |
| 7 | 763 |
| 764 +-----------------------+ | |
| 765 |first line | | |
| 766 |second line | | |
| 767 |a very long line that d| | |
| 768 |oesn't fit in the wi@@@| | |
| 769 +-----------------------+ | |
| 770 | |
| 771 If there is a single line that is too long to fit in the window, this is a | |
| 772 special situation. Vim will show only part of the line, around where the | |
| 773 cursor is. There are no special characters shown, so that you can edit all | |
| 774 parts of this line. | |
| 775 | |
| 776 The '@' occasion in the 'highlight' option can be used to set special | |
| 777 highlighting for the '@' and '~' characters. This makes it possible to | |
| 778 distinguish them from real characters in the buffer. | |
| 779 | |
| 780 The 'showbreak' option contains the string to put in front of wrapped lines. | |
| 781 | |
| 782 *wrap-off* | |
| 783 If the 'wrap' option is off, long lines will not wrap. Only the part that | |
| 784 fits on the screen is shown. If the cursor is moved to a part of the line | |
| 785 that is not shown, the screen is scrolled horizontally. The advantage of | |
| 786 this method is that columns are shown as they are and lines that cannot fit | |
| 787 on the screen can be edited. The disadvantage is that you cannot see all the | |
| 788 characters of a line at once. The 'sidescroll' option can be set to the | |
| 16610 | 789 minimal number of columns to scroll. |
| 7 | 790 |
| 791 All normal ASCII characters are displayed directly on the screen. The <Tab> | |
| 792 is replaced with the number of spaces that it represents. Other non-printing | |
| 793 characters are replaced with "^{char}", where {char} is the non-printing | |
| 794 character with 64 added. Thus character 7 (bell) will be shown as "^G". | |
| 795 Characters between 127 and 160 are replaced with "~{char}", where {char} is | |
| 796 the character with 64 subtracted. These characters occupy more than one | |
| 797 position on the screen. The cursor can only be positioned on the first one. | |
| 798 | |
| 799 If you set the 'number' option, all lines will be preceded with their | |
| 800 number. Tip: If you don't like wrapping lines to mix with the line numbers, | |
| 801 set the 'showbreak' option to eight spaces: | |
| 802 ":set showbreak=\ \ \ \ \ \ \ \ " | |
| 803 | |
| 804 If you set the 'list' option, <Tab> characters will not be shown as several | |
| 805 spaces, but as "^I". A '$' will be placed at the end of the line, so you can | |
| 806 find trailing blanks. | |
| 807 | |
| 808 In Command-line mode only the command-line itself is shown correctly. The | |
| 809 display of the buffer contents is updated as soon as you go back to Command | |
| 810 mode. | |
| 811 | |
| 812 The last line of the window is used for status and other messages. The | |
| 813 status messages will only be used if an option is on: | |
| 814 | |
| 815 status message option default Unix default ~ | |
| 816 current mode 'showmode' on on | |
| 817 command characters 'showcmd' on off | |
| 818 cursor position 'ruler' off off | |
| 819 | |
| 820 The current mode is "-- INSERT --" or "-- REPLACE --", see |'showmode'|. The | |
| 16610 | 821 command characters are those that you typed but were not used yet. |
| 7 | 822 |
| 823 If you have a slow terminal you can switch off the status messages to speed | |
| 824 up editing: | |
| 825 :set nosc noru nosm | |
| 826 | |
| 827 If there is an error, an error message will be shown for at least one second | |
| 16610 | 828 (in reverse video). |
| 7 | 829 |
| 830 Some commands show how many lines were affected. Above which threshold this | |
| 831 happens can be controlled with the 'report' option (default 2). | |
| 832 | |
| 833 On the Amiga Vim will run in a CLI window. The name Vim and the full name of | |
| 834 the current file name will be shown in the title bar. When the window is | |
| 835 resized, Vim will automatically redraw the window. You may make the window as | |
| 836 small as you like, but if it gets too small not a single line will fit in it. | |
| 837 Make it at least 40 characters wide to be able to read most messages on the | |
| 838 last line. | |
| 839 | |
| 840 On most Unix systems, resizing the window is recognized and handled correctly | |
| 16610 | 841 by Vim. |
| 7 | 842 |
| 843 ============================================================================== | |
| 844 8. Definitions *definitions* | |
| 845 | |
| 12254 | 846 buffer Contains lines of text, usually read from a file. |
| 7 | 847 screen The whole area that Vim uses to work in. This can be |
| 848 a terminal emulator window. Also called "the Vim | |
| 849 window". | |
| 12254 | 850 window A view on a buffer. There can be multiple windows for |
| 851 one buffer. | |
| 7 | 852 |
| 853 A screen contains one or more windows, separated by status lines and with the | |
| 854 command line at the bottom. | |
| 855 | |
| 856 +-------------------------------+ | |
| 857 screen | window 1 | window 2 | | |
| 858 | | | | |
| 859 | | | | |
| 860 |= status line =|= status line =| | |
| 861 | window 3 | | |
| 862 | | | |
| 863 | | | |
| 864 |==== status line ==============| | |
| 865 |command line | | |
| 866 +-------------------------------+ | |
| 867 | |
| 868 The command line is also used for messages. It scrolls up the screen when | |
| 869 there is not enough room in the command line. | |
| 870 | |
| 871 A difference is made between four types of lines: | |
| 872 | |
| 873 buffer lines The lines in the buffer. This is the same as the | |
| 874 lines as they are read from/written to a file. They | |
| 875 can be thousands of characters long. | |
| 876 logical lines The buffer lines with folding applied. Buffer lines | |
| 877 in a closed fold are changed to a single logical line: | |
| 878 "+-- 99 lines folded". They can be thousands of | |
| 879 characters long. | |
| 880 window lines The lines displayed in a window: A range of logical | |
| 881 lines with wrapping, line breaks, etc. applied. They | |
| 882 can only be as long as the width of the window allows, | |
| 883 longer lines are wrapped or truncated. | |
| 884 screen lines The lines of the screen that Vim uses. Consists of | |
| 885 the window lines of all windows, with status lines | |
| 886 and the command line added. They can only be as long | |
| 887 as the width of the screen allows. When the command | |
| 888 line gets longer it wraps and lines are scrolled to | |
| 889 make room. | |
| 890 | |
| 891 buffer lines logical lines window lines screen lines ~ | |
| 892 | |
| 893 1. one 1. one 1. +-- folded 1. +-- folded | |
| 894 2. two 2. +-- folded 2. five 2. five | |
| 895 3. three 3. five 3. six 3. six | |
| 896 4. four 4. six 4. seven 4. seven | |
| 897 5. five 5. seven 5. === status line === | |
| 898 6. six 6. aaa | |
| 899 7. seven 7. bbb | |
| 900 8. ccc ccc c | |
| 901 1. aaa 1. aaa 1. aaa 9. cc | |
| 902 2. bbb 2. bbb 2. bbb 10. ddd | |
| 903 3. ccc ccc ccc 3. ccc ccc ccc 3. ccc ccc c 11. ~ | |
| 904 4. ddd 4. ddd 4. cc 12. === status line === | |
| 905 5. ddd 13. (command line) | |
| 906 6. ~ | |
| 907 | |
| 908 ============================================================================== | |
| 14421 | 909 vim:tw=78:ts=8:noet:ft=help:norl: |