Section: User Commands (1)
Updated: 2006 Apr 11
vim [options] [file ..]
vim [options] -
vim [options] -t tag
vim [options] -q [errorfile]
gvim gview evim eview
Vim is a text editor that is upwards compatible to Vi. It can be used to edit all kinds of plain text. It is especially useful for editing programs.
There are a lot of enhancements above Vi: multi level undo, multi windows and buffers, syntax highlighting, command line editing, filename completion, on-line help, visual selection, etc.. See ":help vi_diff.txt" for a summary of the differences between Vim and Vi.
While running Vim a lot of help can be obtained from the on-line help system, with the ":help" command. See the ON-LINE HELP section below.
Most often Vim is started to edit a single file with the command
More generally Vim is started with:
vim [options] [filelist]
If the filelist is missing, the editor will start with an empty buffer. Otherwise exactly one out of the following four may be used to choose one or more files to be edited.
Vim behaves differently, depending on the name of the command (the executable may still be the same file).
The options may be given in any order, before or after filenames. Options without an argument can be combined after a single dash.
Note: You can use up to 10 "+" or "-c" commands.:
Type ":help" in Vim to get started. Type ":help subject" to get help on a specific subject. For example: ":help ZZ" to get help for the "ZZ" command. Use <Tab> and CTRL-D to complete subjects (":help cmdline-completion"). Tags are present to jump from one place to another (sort of hypertext links, see ":help"). All documentation files can be viewed in this way, for example ":help syntax.txt".
For recent info read the VIM home page:
Most of Vim was made by Bram Moolenaar, with a lot of help from others. See ":help credits" in Vim.
Probably. See ":help todo" for a list of known problems.
Note that a number of things that may be regarded as bugs by some, are in fact caused by a too-faithful reproduction of Vi's behaviour. And if you think other things are bugs "because Vi does it differently", you should take a closer look at the vi_diff.txt file (or type :help vi_diff.txt when in Vim). Also have a look at the 'compatible' and 'cpoptions' options.
Tutoriais de Tecnologia Web