Mercurial > vim
annotate runtime/doc/usr_05.txt @ 4687:79797c8534b5
Added tag v7-3-1090 for changeset 8db697ae406a
author | Bram Moolenaar <bram@vim.org> |
---|---|
date | Sat, 01 Jun 2013 23:02:55 +0200 |
parents | fdb8a9c7bd91 |
children | 6ec6b7ff2d43 |
rev | line source |
---|---|
3967 | 1 *usr_05.txt* For Vim version 7.3. Last change: 2012 Nov 20 |
7 | 2 |
3 VIM USER MANUAL - by Bram Moolenaar | |
4 | |
5 Set your settings | |
6 | |
7 | |
8 Vim can be tuned to work like you want it to. This chapter shows you how to | |
9 make Vim start with options set to different values. Add plugins to extend | |
164 | 10 Vim's capabilities. Or define your own macros. |
7 | 11 |
12 |05.1| The vimrc file | |
13 |05.2| The example vimrc file explained | |
14 |05.3| Simple mappings | |
15 |05.4| Adding a plugin | |
16 |05.5| Adding a help file | |
17 |05.6| The option window | |
18 |05.7| Often used options | |
19 | |
20 Next chapter: |usr_06.txt| Using syntax highlighting | |
21 Previous chapter: |usr_04.txt| Making small changes | |
22 Table of contents: |usr_toc.txt| | |
23 | |
24 ============================================================================== | |
25 *05.1* The vimrc file *vimrc-intro* | |
26 | |
27 You probably got tired of typing commands that you use very often. To start | |
819 | 28 Vim with all your favorite option settings and mappings, you write them in |
29 what is called the vimrc file. Vim executes the commands in this file when it | |
30 starts up. | |
7 | 31 |
819 | 32 If you already have a vimrc file (e.g., when your sysadmin has one setup for |
33 you), you can edit it this way: > | |
7 | 34 |
819 | 35 :edit $MYVIMRC |
36 | |
37 If you don't have a vimrc file yet, see |vimrc| to find out where you can | |
7 | 38 create a vimrc file. Also, the ":version" command mentions the name of the |
39 "user vimrc file" Vim looks for. | |
40 | |
819 | 41 For Unix and Macintosh this file is always used and is recommended: |
7 | 42 |
819 | 43 ~/.vimrc ~ |
7 | 44 |
819 | 45 For MS-DOS and MS-Windows you can use one of these: |
7 | 46 |
819 | 47 $HOME/_vimrc ~ |
48 $VIM/_vimrc ~ | |
7 | 49 |
50 The vimrc file can contain all the commands that you type after a colon. The | |
51 most simple ones are for setting options. For example, if you want Vim to | |
3967 | 52 always start with the 'incsearch' option on, add this line your vimrc file: > |
7 | 53 |
54 set incsearch | |
55 | |
56 For this new line to take effect you need to exit Vim and start it again. | |
57 Later you will learn how to do this without exiting Vim. | |
58 | |
59 This chapter only explains the most basic items. For more information on how | |
60 to write a Vim script file: |usr_41.txt|. | |
61 | |
62 ============================================================================== | |
63 *05.2* The example vimrc file explained *vimrc_example.vim* | |
64 | |
65 In the first chapter was explained how the example vimrc (included in the | |
66 Vim distribution) file can be used to make Vim startup in not-compatible mode | |
67 (see |not-compatible|). The file can be found here: | |
68 | |
69 $VIMRUNTIME/vimrc_example.vim ~ | |
70 | |
71 In this section we will explain the various commands used in this file. This | |
72 will give you hints about how to set up your own preferences. Not everything | |
73 will be explained though. Use the ":help" command to find out more. | |
74 | |
75 > | |
76 set nocompatible | |
77 | |
78 As mentioned in the first chapter, these manuals explain Vim working in an | |
79 improved way, thus not completely Vi compatible. Setting the 'compatible' | |
80 option off, thus 'nocompatible' takes care of this. | |
81 | |
82 > | |
83 set backspace=indent,eol,start | |
84 | |
85 This specifies where in Insert mode the <BS> is allowed to delete the | |
86 character in front of the cursor. The three items, separated by commas, tell | |
87 Vim to delete the white space at the start of the line, a line break and the | |
88 character before where Insert mode started. | |
89 > | |
90 | |
91 set autoindent | |
92 | |
93 This makes Vim use the indent of the previous line for a newly created line. | |
94 Thus there is the same amount of white space before the new line. For example | |
95 when pressing <Enter> in Insert mode, and when using the "o" command to open a | |
96 new line. | |
97 > | |
98 | |
99 if has("vms") | |
100 set nobackup | |
101 else | |
102 set backup | |
103 endif | |
104 | |
105 This tells Vim to keep a backup copy of a file when overwriting it. But not | |
106 on the VMS system, since it keeps old versions of files already. The backup | |
107 file will have the same name as the original file with "~" added. See |07.4| | |
108 > | |
109 | |
110 set history=50 | |
111 | |
112 Keep 50 commands and 50 search patterns in the history. Use another number if | |
113 you want to remember fewer or more lines. | |
114 > | |
115 | |
116 set ruler | |
117 | |
118 Always display the current cursor position in the lower right corner of the | |
119 Vim window. | |
120 | |
121 > | |
122 set showcmd | |
123 | |
124 Display an incomplete command in the lower right corner of the Vim window, | |
125 left of the ruler. For example, when you type "2f", Vim is waiting for you to | |
126 type the character to find and "2f" is displayed. When you press "w" next, | |
127 the "2fw" command is executed and the displayed "2f" is removed. | |
128 | |
129 +-------------------------------------------------+ | |
130 |text in the Vim window | | |
131 |~ | | |
132 |~ | | |
133 |-- VISUAL -- 2f 43,8 17% | | |
134 +-------------------------------------------------+ | |
135 ^^^^^^^^^^^ ^^^^^^^^ ^^^^^^^^^^ | |
136 'showmode' 'showcmd' 'ruler' | |
137 | |
138 > | |
139 set incsearch | |
140 | |
141 Display the match for a search pattern when halfway typing it. | |
142 | |
143 > | |
144 map Q gq | |
145 | |
146 This defines a key mapping. More about that in the next section. This | |
147 defines the "Q" command to do formatting with the "gq" operator. This is how | |
148 it worked before Vim 5.0. Otherwise the "Q" command starts Ex mode, but you | |
149 will not need it. | |
150 | |
151 > | |
43 | 152 vnoremap _g y:exe "grep /" . escape(@", '\\/') . "/ *.c *.h"<CR> |
7 | 153 |
43 | 154 This mapping yanks the visually selected text and searches for it in C files. |
155 This is a complicated mapping. You can see that mappings can be used to do | |
156 quite complicated things. Still, it is just a sequence of commands that are | |
7 | 157 executed like you typed them. |
158 | |
159 > | |
160 if &t_Co > 2 || has("gui_running") | |
161 syntax on | |
162 set hlsearch | |
163 endif | |
164 | |
165 This switches on syntax highlighting, but only if colors are available. And | |
166 the 'hlsearch' option tells Vim to highlight matches with the last used search | |
167 pattern. The "if" command is very useful to set options only when some | |
168 condition is met. More about that in |usr_41.txt|. | |
169 | |
170 *vimrc-filetype* > | |
171 filetype plugin indent on | |
172 | |
173 This switches on three very clever mechanisms: | |
174 1. Filetype detection. | |
175 Whenever you start editing a file, Vim will try to figure out what kind of | |
176 file this is. When you edit "main.c", Vim will see the ".c" extension and | |
177 recognize this as a "c" filetype. When you edit a file that starts with | |
178 "#!/bin/sh", Vim will recognize it as a "sh" filetype. | |
179 The filetype detection is used for syntax highlighting and the other two | |
180 items below. | |
181 See |filetypes|. | |
182 | |
183 2. Using filetype plugin files | |
184 Many different filetypes are edited with different options. For example, | |
185 when you edit a "c" file, it's very useful to set the 'cindent' option to | |
186 automatically indent the lines. These commonly useful option settings are | |
187 included with Vim in filetype plugins. You can also add your own, see | |
188 |write-filetype-plugin|. | |
189 | |
190 3. Using indent files | |
191 When editing programs, the indent of a line can often be computed | |
192 automatically. Vim comes with these indent rules for a number of | |
193 filetypes. See |:filetype-indent-on| and 'indentexpr'. | |
194 | |
195 > | |
196 autocmd FileType text setlocal textwidth=78 | |
197 | |
198 This makes Vim break text to avoid lines getting longer than 78 characters. | |
199 But only for files that have been detected to be plain text. There are | |
200 actually two parts here. "autocmd FileType text" is an autocommand. This | |
201 defines that when the file type is set to "text" the following command is | |
202 automatically executed. "setlocal textwidth=78" sets the 'textwidth' option | |
203 to 78, but only locally in one file. | |
204 | |
1125 | 205 *restore-cursor* > |
7 | 206 autocmd BufReadPost * |
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
207 \ if line("'\"") > 1 && line("'\"") <= line("$") | |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
208 \ exe "normal! g`\"" | |
7 | 209 \ endif |
210 | |
211 Another autocommand. This time it is used after reading any file. The | |
212 complicated stuff after it checks if the '" mark is defined, and jumps to it | |
213 if so. The backslash at the start of a line is used to continue the command | |
214 from the previous line. That avoids a line getting very long. | |
215 See |line-continuation|. This only works in a Vim script file, not when | |
216 typing commands at the command-line. | |
217 | |
218 ============================================================================== | |
219 *05.3* Simple mappings | |
220 | |
221 A mapping enables you to bind a set of Vim commands to a single key. Suppose, | |
222 for example, that you need to surround certain words with curly braces. In | |
223 other words, you need to change a word such as "amount" into "{amount}". With | |
224 the :map command, you can tell Vim that the F5 key does this job. The command | |
225 is as follows: > | |
226 | |
227 :map <F5> i{<Esc>ea}<Esc> | |
228 < | |
229 Note: | |
230 When entering this command, you must enter <F5> by typing four | |
231 characters. Similarly, <Esc> is not entered by pressing the <Esc> | |
232 key, but by typing five characters. Watch out for this difference | |
233 when reading the manual! | |
234 | |
235 Let's break this down: | |
236 <F5> The F5 function key. This is the trigger key that causes the | |
237 command to be executed as the key is pressed. | |
238 | |
239 i{<Esc> Insert the { character. The <Esc> key ends Insert mode. | |
240 | |
241 e Move to the end of the word. | |
242 | |
243 a}<Esc> Append the } to the word. | |
244 | |
245 After you execute the ":map" command, all you have to do to put {} around a | |
246 word is to put the cursor on the first character and press F5. | |
247 | |
248 In this example, the trigger is a single key; it can be any string. But when | |
249 you use an existing Vim command, that command will no longer be available. | |
250 You better avoid that. | |
251 One key that can be used with mappings is the backslash. Since you | |
252 probably want to define more than one mapping, add another character. You | |
164 | 253 could map "\p" to add parentheses around a word, and "\c" to add curly braces, |
254 for example: > | |
7 | 255 |
256 :map \p i(<Esc>ea)<Esc> | |
257 :map \c i{<Esc>ea}<Esc> | |
258 | |
259 You need to type the \ and the p quickly after another, so that Vim knows they | |
260 belong together. | |
261 | |
262 The ":map" command (with no arguments) lists your current mappings. At | |
263 least the ones for Normal mode. More about mappings in section |40.1|. | |
264 | |
265 ============================================================================== | |
266 *05.4* Adding a plugin *add-plugin* *plugin* | |
267 | |
268 Vim's functionality can be extended by adding plugins. A plugin is nothing | |
269 more than a Vim script file that is loaded automatically when Vim starts. You | |
270 can add a plugin very easily by dropping it in your plugin directory. | |
271 {not available when Vim was compiled without the |+eval| feature} | |
272 | |
273 There are two types of plugins: | |
274 | |
275 global plugin: Used for all kinds of files | |
276 filetype plugin: Only used for a specific type of file | |
277 | |
278 The global plugins will be discussed first, then the filetype ones | |
279 |add-filetype-plugin|. | |
280 | |
281 | |
282 GLOBAL PLUGINS *standard-plugin* | |
283 | |
284 When you start Vim, it will automatically load a number of global plugins. | |
285 You don't have to do anything for this. They add functionality that most | |
286 people will want to use, but which was implemented as a Vim script instead of | |
287 being compiled into Vim. You can find them listed in the help index | |
288 |standard-plugin-list|. Also see |load-plugins|. | |
289 | |
290 *add-global-plugin* | |
291 You can add a global plugin to add functionality that will always be present | |
292 when you use Vim. There are only two steps for adding a global plugin: | |
293 1. Get a copy of the plugin. | |
294 2. Drop it in the right directory. | |
295 | |
296 | |
297 GETTING A GLOBAL PLUGIN | |
298 | |
299 Where can you find plugins? | |
300 - Some come with Vim. You can find them in the directory $VIMRUNTIME/macros | |
301 and its sub-directories. | |
800 | 302 - Download from the net. There is a large collection on http://www.vim.org. |
7 | 303 - They are sometimes posted in a Vim |maillist|. |
304 - You could write one yourself, see |write-plugin|. | |
305 | |
800 | 306 Some plugins come as a vimball archive, see |vimball|. |
307 Some plugins can be updated automatically, see |getscript|. | |
308 | |
7 | 309 |
310 USING A GLOBAL PLUGIN | |
311 | |
312 First read the text in the plugin itself to check for any special conditions. | |
313 Then copy the file to your plugin directory: | |
314 | |
315 system plugin directory ~ | |
316 Unix ~/.vim/plugin/ | |
317 PC and OS/2 $HOME/vimfiles/plugin or $VIM/vimfiles/plugin | |
318 Amiga s:vimfiles/plugin | |
319 Macintosh $VIM:vimfiles:plugin | |
320 Mac OS X ~/.vim/plugin/ | |
321 RISC-OS Choices:vimfiles.plugin | |
322 | |
323 Example for Unix (assuming you didn't have a plugin directory yet): > | |
324 | |
325 mkdir ~/.vim | |
326 mkdir ~/.vim/plugin | |
327 cp /usr/local/share/vim/vim60/macros/justify.vim ~/.vim/plugin | |
328 | |
329 That's all! Now you can use the commands defined in this plugin to justify | |
330 text. | |
331 | |
548 | 332 Instead of putting plugins directly into the plugin/ directory, you may |
333 better organize them by putting them into subdirectories under plugin/. | |
334 As an example, consider using "~/.vim/plugin/perl/*.vim" for all your Perl | |
335 plugins. | |
541 | 336 |
7 | 337 |
338 FILETYPE PLUGINS *add-filetype-plugin* *ftplugins* | |
339 | |
340 The Vim distribution comes with a set of plugins for different filetypes that | |
341 you can start using with this command: > | |
342 | |
343 :filetype plugin on | |
344 | |
345 That's all! See |vimrc-filetype|. | |
346 | |
347 If you are missing a plugin for a filetype you are using, or you found a | |
348 better one, you can add it. There are two steps for adding a filetype plugin: | |
349 1. Get a copy of the plugin. | |
350 2. Drop it in the right directory. | |
351 | |
352 | |
353 GETTING A FILETYPE PLUGIN | |
354 | |
355 You can find them in the same places as the global plugins. Watch out if the | |
356 type of file is mentioned, then you know if the plugin is a global or a | |
357 filetype one. The scripts in $VIMRUNTIME/macros are global ones, the filetype | |
358 plugins are in $VIMRUNTIME/ftplugin. | |
359 | |
360 | |
361 USING A FILETYPE PLUGIN *ftplugin-name* | |
362 | |
363 You can add a filetype plugin by dropping it in the right directory. The | |
364 name of this directory is in the same directory mentioned above for global | |
365 plugins, but the last part is "ftplugin". Suppose you have found a plugin for | |
366 the "stuff" filetype, and you are on Unix. Then you can move this file to the | |
367 ftplugin directory: > | |
368 | |
369 mv thefile ~/.vim/ftplugin/stuff.vim | |
370 | |
371 If that file already exists you already have a plugin for "stuff". You might | |
372 want to check if the existing plugin doesn't conflict with the one you are | |
373 adding. If it's OK, you can give the new one another name: > | |
374 | |
375 mv thefile ~/.vim/ftplugin/stuff_too.vim | |
376 | |
377 The underscore is used to separate the name of the filetype from the rest, | |
10 | 378 which can be anything. If you use "otherstuff.vim" it wouldn't work, it would |
379 be loaded for the "otherstuff" filetype. | |
7 | 380 |
381 On MS-DOS you cannot use long filenames. You would run into trouble if you | |
382 add a second plugin and the filetype has more than six characters. You can | |
383 use an extra directory to get around this: > | |
384 | |
385 mkdir $VIM/vimfiles/ftplugin/fortran | |
386 copy thefile $VIM/vimfiles/ftplugin/fortran/too.vim | |
387 | |
388 The generic names for the filetype plugins are: > | |
389 | |
390 ftplugin/<filetype>.vim | |
391 ftplugin/<filetype>_<name>.vim | |
392 ftplugin/<filetype>/<name>.vim | |
393 | |
394 Here "<name>" can be any name that you prefer. | |
395 Examples for the "stuff" filetype on Unix: > | |
396 | |
397 ~/.vim/ftplugin/stuff.vim | |
398 ~/.vim/ftplugin/stuff_def.vim | |
399 ~/.vim/ftplugin/stuff/header.vim | |
400 | |
401 The <filetype> part is the name of the filetype the plugin is to be used for. | |
402 Only files of this filetype will use the settings from the plugin. The <name> | |
403 part of the plugin file doesn't matter, you can use it to have several plugins | |
404 for the same filetype. Note that it must end in ".vim". | |
405 | |
406 | |
407 Further reading: | |
408 |filetype-plugins| Documentation for the filetype plugins and information | |
409 about how to avoid that mappings cause problems. | |
410 |load-plugins| When the global plugins are loaded during startup. | |
411 |ftplugin-overrule| Overruling the settings from a global plugin. | |
412 |write-plugin| How to write a plugin script. | |
413 |plugin-details| For more information about using plugins or when your | |
414 plugin doesn't work. | |
415 |new-filetype| How to detect a new file type. | |
416 | |
417 ============================================================================== | |
418 *05.5* Adding a help file *add-local-help* *matchit-install* | |
419 | |
420 If you are lucky, the plugin you installed also comes with a help file. We | |
421 will explain how to install the help file, so that you can easily find help | |
422 for your new plugin. | |
423 Let us use the "matchit.vim" plugin as an example (it is included with | |
424 Vim). This plugin makes the "%" command jump to matching HTML tags, | |
425 if/else/endif in Vim scripts, etc. Very useful, although it's not backwards | |
426 compatible (that's why it is not enabled by default). | |
427 This plugin comes with documentation: "matchit.txt". Let's first copy the | |
428 plugin to the right directory. This time we will do it from inside Vim, so | |
429 that we can use $VIMRUNTIME. (You may skip some of the "mkdir" commands if | |
430 you already have the directory.) > | |
431 | |
432 :!mkdir ~/.vim | |
433 :!mkdir ~/.vim/plugin | |
434 :!cp $VIMRUNTIME/macros/matchit.vim ~/.vim/plugin | |
435 | |
22 | 436 The "cp" command is for Unix, on MS-DOS you can use "copy". |
437 | |
7 | 438 Now create a "doc" directory in one of the directories in 'runtimepath'. > |
439 | |
440 :!mkdir ~/.vim/doc | |
441 | |
442 Copy the help file to the "doc" directory. > | |
443 | |
444 :!cp $VIMRUNTIME/macros/matchit.txt ~/.vim/doc | |
445 | |
446 Now comes the trick, which allows you to jump to the subjects in the new help | |
447 file: Generate the local tags file with the |:helptags| command. > | |
448 | |
449 :helptags ~/.vim/doc | |
450 | |
451 Now you can use the > | |
452 | |
453 :help g% | |
454 | |
455 command to find help for "g%" in the help file you just added. You can see an | |
456 entry for the local help file when you do: > | |
457 | |
458 :help local-additions | |
459 | |
460 The title lines from the local help files are automagically added to this | |
461 section. There you can see which local help files have been added and jump to | |
462 them through the tag. | |
463 | |
464 For writing a local help file, see |write-local-help|. | |
465 | |
466 ============================================================================== | |
467 *05.6* The option window | |
468 | |
469 If you are looking for an option that does what you want, you can search in | |
470 the help files here: |options|. Another way is by using this command: > | |
471 | |
472 :options | |
473 | |
474 This opens a new window, with a list of options with a one-line explanation. | |
475 The options are grouped by subject. Move the cursor to a subject and press | |
476 <Enter> to jump there. Press <Enter> again to jump back. Or use CTRL-O. | |
477 | |
478 You can change the value of an option. For example, move to the "displaying | |
479 text" subject. Then move the cursor down to this line: | |
480 | |
481 set wrap nowrap ~ | |
482 | |
483 When you hit <Enter>, the line will change to: | |
484 | |
485 set nowrap wrap ~ | |
486 | |
487 The option has now been switched off. | |
488 | |
489 Just above this line is a short description of the 'wrap' option. Move the | |
490 cursor one line up to place it in this line. Now hit <Enter> and you jump to | |
491 the full help on the 'wrap' option. | |
492 | |
493 For options that take a number or string argument you can edit the value. | |
494 Then press <Enter> to apply the new value. For example, move the cursor a few | |
495 lines up to this line: | |
496 | |
497 set so=0 ~ | |
498 | |
499 Position the cursor on the zero with "$". Change it into a five with "r5". | |
500 Then press <Enter> to apply the new value. When you now move the cursor | |
501 around you will notice that the text starts scrolling before you reach the | |
502 border. This is what the 'scrolloff' option does, it specifies an offset | |
503 from the window border where scrolling starts. | |
504 | |
505 ============================================================================== | |
506 *05.7* Often used options | |
507 | |
508 There are an awful lot of options. Most of them you will hardly ever use. | |
509 Some of the more useful ones will be mentioned here. Don't forget you can | |
510 find more help on these options with the ":help" command, with single quotes | |
511 before and after the option name. For example: > | |
512 | |
513 :help 'wrap' | |
514 | |
515 In case you have messed up an option value, you can set it back to the | |
10 | 516 default by putting an ampersand (&) after the option name. Example: > |
7 | 517 |
518 :set iskeyword& | |
519 | |
520 | |
521 NOT WRAPPING LINES | |
522 | |
523 Vim normally wraps long lines, so that you can see all of the text. Sometimes | |
524 it's better to let the text continue right of the window. Then you need to | |
10 | 525 scroll the text left-right to see all of a long line. Switch wrapping off |
526 with this command: > | |
7 | 527 |
528 :set nowrap | |
529 | |
530 Vim will automatically scroll the text when you move to text that is not | |
531 displayed. To see a context of ten characters, do this: > | |
532 | |
533 :set sidescroll=10 | |
534 | |
535 This doesn't change the text in the file, only the way it is displayed. | |
536 | |
537 | |
538 WRAPPING MOVEMENT COMMANDS | |
539 | |
540 Most commands for moving around will stop moving at the start and end of a | |
541 line. You can change that with the 'whichwrap' option. This sets it to the | |
542 default value: > | |
543 | |
544 :set whichwrap=b,s | |
545 | |
546 This allows the <BS> key, when used in the first position of a line, to move | |
547 the cursor to the end of the previous line. And the <Space> key moves from | |
548 the end of a line to the start of the next one. | |
549 | |
550 To allow the cursor keys <Left> and <Right> to also wrap, use this command: > | |
551 | |
552 :set whichwrap=b,s,<,> | |
553 | |
554 This is still only for Normal mode. To let <Left> and <Right> do this in | |
555 Insert mode as well: > | |
556 | |
557 :set whichwrap=b,s,<,>,[,] | |
558 | |
559 There are a few other flags that can be added, see 'whichwrap'. | |
560 | |
561 | |
562 VIEWING TABS | |
563 | |
564 When there are tabs in a file, you cannot see where they are. To make them | |
565 visible: > | |
566 | |
567 :set list | |
568 | |
1278 | 569 Now every tab is displayed as ^I. And a $ is displayed at the end of each |
7 | 570 line, so that you can spot trailing spaces that would otherwise go unnoticed. |
571 A disadvantage is that this looks ugly when there are many Tabs in a file. | |
572 If you have a color terminal, or are using the GUI, Vim can show the spaces | |
573 and tabs as highlighted characters. Use the 'listchars' option: > | |
574 | |
575 :set listchars=tab:>-,trail:- | |
576 | |
577 Now every tab will be displayed as ">---" (with more or less "-") and trailing | |
578 white space as "-". Looks a lot better, doesn't it? | |
579 | |
580 | |
581 KEYWORDS | |
582 | |
583 The 'iskeyword' option specifies which characters can appear in a word: > | |
584 | |
585 :set iskeyword | |
586 < iskeyword=@,48-57,_,192-255 ~ | |
587 | |
588 The "@" stands for all alphabetic letters. "48-57" stands for ASCII | |
589 characters 48 to 57, which are the numbers 0 to 9. "192-255" are the | |
590 printable latin characters. | |
591 Sometimes you will want to include a dash in keywords, so that commands | |
592 like "w" consider "upper-case" to be one word. You can do it like this: > | |
593 | |
594 :set iskeyword+=- | |
595 :set iskeyword | |
596 < iskeyword=@,48-57,_,192-255,- ~ | |
597 | |
598 If you look at the new value, you will see that Vim has added a comma for you. | |
599 To remove a character use "-=". For example, to remove the underscore: > | |
600 | |
601 :set iskeyword-=_ | |
602 :set iskeyword | |
603 < iskeyword=@,48-57,192-255,- ~ | |
604 | |
605 This time a comma is automatically deleted. | |
606 | |
607 | |
608 ROOM FOR MESSAGES | |
609 | |
610 When Vim starts there is one line at the bottom that is used for messages. | |
611 When a message is long, it is either truncated, thus you can only see part of | |
612 it, or the text scrolls and you have to press <Enter> to continue. | |
613 You can set the 'cmdheight' option to the number of lines used for | |
614 messages. Example: > | |
615 | |
616 :set cmdheight=3 | |
617 | |
618 This does mean there is less room to edit text, thus it's a compromise. | |
619 | |
620 ============================================================================== | |
621 | |
622 Next chapter: |usr_06.txt| Using syntax highlighting | |
623 | |
624 Copyright: see |manual-copyright| vim:tw=78:ts=8:ft=help:norl: |