Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Let The Music Play: Join EFF Today

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 72 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       vim [options] [file ..]
       vim [options] -
       vim [options] -t tag
       vim [options] -q [errorfile]

       gvim gview
       rvim rview rgvim rgview


       Vim is a text editor that is upwards compatible to Vi.  It
       can be used to edit all kinds of plain text.  It is  espe­
       cially useful for editing programs.

       There  are  a  lot  of  enhancements above Vi: multi level
       undo, multi windows and buffers, syntax highlighting, com­
       mand  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

            vim file

       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.

       file ..     A  list  of  filenames.  The first one will be
                   the current file and  read  into  the  buffer.
                   The  cursor  will  be  positioned on the first
                   line of the buffer.  You can get to the  other
                   files  with  the  ":next"  command.  To edit a
                   file that starts  with  a  dash,  precede  the
                   filelist with "--".

       -           The file to edit is read from stdin.  Commands
                   are read from stderr, which should be a tty.

       -t {tag}    The file to edit and the initial cursor  posi­
                   tion depends on a "tag", a sort of goto label.
                   obtained from the 'errorfile' option (defaults
                   to "AztecC.Err" for the Amiga, "errors.err" on
                   other  systems).  Further errors can be jumped
                   to with the ":cn" command.  See ":help  quick­

       Vim behaves differently, depending on the name of the com­
       mand (the executable may still be the same file).

       vim       The "normal" way, everything is default.

       ex        Start in Ex mode.  Go to Normal  mode  with  the
                 ":vi"  command.   Can also be done with the "-e"

       view      Start in read-only mode.  You will be  protected
                 from  writing  the files.  Can also be done with
                 the "-R" argument.

       gvim gview
                 The GUI version.  Starts a new window.  Can also
                 be done with the "-g" argument.

       rvim rview rgvim rgview
                 Like  the above, but with restrictions.  It will
                 not be possible to start shell commands, or sus­
                 pend  Vim.  Can also be done with the "-Z" argu­


       The options may be given in any  order,  before  or  after
       filenames.   Options  without  an argument can be combined
       after a single dash.

       +[num]      For the first file the cursor  will  be  posi­
                   tioned  on  line  "num".  If "num" is missing,
                   the cursor will  be  positioned  on  the  last

       +/{pat}     For  the  first  file the cursor will be posi­
                   tioned on the first occurrence of {pat}.   See
                   ":help   search-pattern"   for  the  available
                   search patterns.


       -c {command}
                   {command} will be  executed  after  the  first
                   file  has been read.  {command} is interpreted
                   as an Ex command.  If the  {command}  contains
                   spaces  it  must  be enclosed in double quotes
                   (this depends on  the  shell  that  is  used).
                   Otherwise  an  error  message is given and Vim

       -b          Binary mode.  A few options will be  set  that
                   makes  it  possible  to  edit a binary or exe­
                   cutable file.

       -C          Compatible.   Set  the  'compatible'   option.
                   This will make Vim behave mostly like Vi, even
                   though a .vimrc file exists.

       -d          Start in diff mode.  There should  be  two  or
                   three  file name arguments.  Vim will open all
                   the files and show differences  between  them.
                   Works like vimdiff(1).

       -d {device} Open  {device} for use as a terminal.  Only on
                   the Amiga.  Example: "-d con:20/30/600/150".

       -e          Start Vim in Ex mode, just like the executable
                   was called "ex".

       -f          Foreground.  For the GUI version, Vim will not
                   fork and detach from the shell it was  started
                   in.   On  the  Amiga,  Vim is not restarted to
                   open a new window.  This option should be used
                   when  Vim  is  executed by a program that will
                   wait for the  edit  session  to  finish  (e.g.
                   mail).   On  the Amiga the ":sh" and ":!" com­
                   mands will not work.

       --nofork    Foreground.  For the GUI version, Vim will not
                   fork  and detach from the shell it was started

       -F          If Vim has been compiled  with  FKMAP  support
                   for  editing  right-to-left oriented files and
                   Farsi keyboard mapping, this option starts Vim
                   in  Farsi  mode,  i.e. 'fkmap' and 'rightleft'
                   are set.  Otherwise an error message is  given
                   and Vim aborts.

       -g          If  Vim  has  been  compiled with GUI support,
                   this option enables the GUI.  If no  GUI  sup­
                   port  was  compiled  in,  an  error message is
                   given and Vim aborts.

       -h          Give a bit of  help  about  the  command  line
                   arguments  and options.  After this Vim exits.

       -H          If Vim has been compiled with  RIGHTLEFT  sup­
                   port  for editing right-to-left oriented files

       -l          Lisp  mode.   Sets  the 'lisp' and 'showmatch'
                   options on.

       -m          Modifying  files  is  disabled.   Resets   the
                   'write'  option,  so that writing files is not

       -N          No-compatible mode.   Reset  the  'compatible'
                   option.   This will make Vim behave a bit bet­
                   ter, but less Vi  compatible,  even  though  a
                   .vimrc file does not exist.

       -n          No  swap  file will be used.  Recovery after a
                   crash will be impossible.  Handy if  you  want
                   to  edit  a  file  on a very slow medium (e.g.
                   floppy).  Can also be done with  ":set  uc=0".
                   Can be undone with ":set uc=200".

       -o[N]       Open  N  windows  stacked.  When N is omitted,
                   open one window for each file.

       -O[N]       Open N windows side by side.  When N is  omit­
                   ted, open one window for each file.

       -R          Read-only mode.  The 'readonly' option will be
                   set.  You can still edit the buffer, but  will
                   be  prevented  from  accidently  overwriting a
                   file.  If you do want to overwrite a file, add
                   an  exclamation  mark to the Ex command, as in
                   ":w!".  The -R  option  also  implies  the  -n
                   option (see below).  The 'readonly' option can
                   be reset with ":set noro".  See ":help  'read­

       -r          List  swap files, with information about using
                   them for recovery.

       -r {file}   Recovery mode.   The  swap  file  is  used  to
                   recover  a  crashed editing session.  The swap
                   file is a file with the same filename  as  the
                   text  file  with  ".swp" appended.  See ":help

       -s          Silent mode.  Only when  started  as  "Ex"  or
                   when the "-e" option was given before the "-s"

       -s {scriptin}
                   The script file {scriptin} is read.  The char­
                   acters  in  the file are interpreted as if you
                   had typed them.  The same can be done with the
                   command  ":source! {scriptin}".  If the end of
                   initializations by  giving  the  name  "NONE".
                   See ":help initialization" within vim for more

       -U {gvimrc} Use the commands in the file {gvimrc} for  GUI
                   initializations.   All  the other GUI initial­
                   izations are skipped.  It can also be used  to
                   skip  all  GUI  initializations  by giving the
                   name "NONE".  See ":help gui-init" within  vim
                   for more details.

       -V          Verbose.   Give messages about which files are
                   sourced and for reading and writing a  viminfo

       -v          Start Vim in Vi mode, just like the executable
                   was called "vi".  This only  has  effect  when
                   the executable is called "ex".

       -w {scriptout}
                   All  the characters that you type are recorded
                   in the file {scriptout}, until you  exit  Vim.
                   This  is useful if you want to create a script
                   file to be used with "vim -s"  or  ":source!".
                   If the {scriptout} file exists, characters are

       -W {scriptout}
                   Like -w, but an existing file is  overwritten.

       -x          Use  encryption  when  writing  files.    Will
                   prompt for a crypt key.

       -X          Don't  connect  to  the  X  server.   Shortens
                   startup  time  in  a  terminal, but the window
                   title and clipboard will not be used.

       -Z          Restricted mode.  Works  like  the  executable
                   starts with "r".

       --          Denotes  the  end  of  the options.  Arguments
                   after this will be handled  as  a  file  name.
                   This  can  be  used  to  edit  a filename that
                   starts with a '-'.

       --help      Give a help message and exit, just like  "-h".

       --version   Print version information and exit.

       --remote    Connect  to  a Vim server and make it edit the
                   files given in the rest of the arguments.   If
                   no  server is found a warning is given and the
                   As  --remote,  but Vim does not exit until the
                   files have been edited.

                   As --remote-wait, but without the warning when
                   no server is found.

                   List  the names of all Vim servers that can be

       --servername {name}
                   Use {name} as the server name.  Used  for  the
                   current Vim, unless used with a --remote argu­
                   ment, then it's the name of the server to con­
                   nect to.

       --socketid {id}
                   GTK GUI only: Use the GtkPlug mechanism to run
                   gvim in another window.

       --echo-wid  GTK GUI only: Echo the Window ID on stdout


       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".


                      The  Vim  documentation  files.  Use ":help
                      doc-file-list" to get the complete list.

                      The tags file used for finding  information
                      in the documentation files.

                      System wide syntax initializations.

                      Syntax files for various languages.

                      System wide Vim initializations.

                      System wide gvim initializations.
                      name.  See ":help 'filetype'".

                      Script  to detect the type of a file by its
                      contents.  See ":help 'filetype'".

                      Files used for PostScript printing.

       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.
       Vim  is  based on Stevie, worked on by: Tim Thompson, Tony
       Andrews and G.R. (Fred) Walter.  Although  hardly  any  of
       the original code remains.


       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.

                           2002 Feb 22                     VIM(1)

The Linux Tutorial is always looking for new contributors.



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds