Lines Matching refs:can
8 Vim can be tuned to work like you want it to. This chapter shows you how to
35 you), you can edit it this way: >
39 If you don't have a vimrc file yet, see |vimrc| to find out where you can
47 For MS-Windows you can use one of these:
60 The vimrc file can contain all the commands that you type after a colon. The
76 Vim distribution) file can be used to make Vim startup in not-compatible mode
77 (see |not-compatible|). The file can be found here:
110 file, exit Vim, and then edit the file again, you can undo the changes made
168 Loading defaults.vim can be disabled with this command: >
262 CTRL-G u to first break undo, so that you can undo CTRL-U after inserting a
276 You can see that a mapping can be used to do quite complicated things. Still,
301 included with Vim in filetype plugins. You can also add your own, see
305 When editing programs, the indent of a line can often be computed
343 the :map command, you can tell Vim that the F5 key does this job. The command
367 In this example, the trigger is a single key; it can be any string. But when
370 One key that can be used with mappings is the backslash. Since you
387 A package is a set of files that you can add to Vim. There are two kinds of
390 The Vim distribution comes with a few packages that you can optionally use.
398 That's all! After restarting Vim you can find help about this plugin: >
402 package directory in 'runtimepath', so that the help file can be found.
404 You can find packages on the Internet in various places. It usually comes as
405 an archive or as a repository. For an archive you can follow these steps:
408 < "fancy" can be any name of your liking. Use one that describes the
417 Here "fancytext" is the name of the package, it can be anything
420 More information about packages can be found here: |packages|.
425 Vim's functionality can be extended by adding plugins. A plugin is nothing
427 can add a plugin very easily by dropping it in your plugin directory.
444 being compiled into Vim. You can find them listed in the help index
448 You can add a global plugin to add functionality that will always be present
456 Where can you find plugins?
457 - Some are always loaded, you can see them in the directory $VIMRUNTIME/plugin.
458 - Some come with Vim. You can find them in the directory $VIMRUNTIME/macros
465 Some plugins can be updated automatically, see |getscript|.
486 That's all! Now you can use the commands defined in this plugin.
497 you can start using with this command: >
504 better one, you can add it. There are two steps for adding a filetype plugin:
511 You can find them in the same places as the global plugins. Watch out if the
519 You can add a filetype plugin by dropping it in the right directory. The
522 the "stuff" filetype, and you are on Unix. Then you can move this file to the
529 adding. If it's OK, you can give the new one another name: >
534 which can be anything. If you use "otherstuff.vim" it wouldn't work, it would
539 characters. You can use an extra directory to get around this: >
550 Here "<name>" can be any name that you prefer.
559 part of the plugin file doesn't matter, you can use it to have several plugins
577 will explain how to install the help file, so that you can easily find help
588 The "cp" command is for Unix, on MS-Windows you can use "copy".
603 Now you can use the >
607 command to find help for "doit" in the help file you just added. You can see
613 section. There you can see which local help files have been added and jump to
621 If you are looking for an option that does what you want, you can search in
630 You can change the value of an option. For example, move to the "displaying
645 For options that take a number or string argument you can edit the value.
661 Some of the more useful ones will be mentioned here. Don't forget you can
667 In case you have messed up an option value, you can set it back to the
675 Vim normally wraps long lines, so that you can see all of the text. Sometimes
693 line. You can change that with the 'whichwrap' option. This sets it to the
711 There are a few other flags that can be added, see 'whichwrap'.
722 line, so that you can spot trailing spaces that would otherwise go unnoticed.
724 If you have a color terminal, or are using the GUI, Vim can show the spaces
735 The 'iskeyword' option specifies which characters can appear in a word: >
744 like "w" consider "upper-case" to be one word. You can do it like this: >
763 When a message is long, it is either truncated, thus you can only see part of
765 You can set the 'cmdheight' option to the number of lines used for