VIM(1)

📦
version 9.2.1202 · 17 versions
, in alpine 3.23, alpine 3.24

💖 VIM(1) 💖

okay so this is the VIM(1) page from the General Commands Manual, and it's literally all about vim — Vi IMproved, a programmer's text editor 💅✨

🎀 NAME 🎀

vim — Vi IMproved, a programmer's text editor 🫶

✨ SYNOPSIS ✨

the whole launch vibe is exactly this, bestie:

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

ex
view
gvim gview evim eview
rvim rview rgvim rgview

🌸 DESCRIPTION 🌸

Vim is a text editor that is upwards compatible to Vi. It can be used to edit all kinds of plain text, and it is especially useful for editing programs. no cap, that's the whole point 💖

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. it's giving glow-up, fr fr ✨

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. yes bestie, the help is literally built in 🫶

Most often Vim is started to edit a single file with the command 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. pick your main character, okay? 💅

  • 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 position depends on a "tag", a sort of goto label. {tag} is looked up in the tags file, the associated file becomes the current file and the associated command is executed. Mostly this is used for C programs, in which case {tag} could be a function name. The effect is that the file containing that function becomes the current file and the cursor is positioned on the start of the function. See :help tag-commands.
  • -q [errorfile] — Start in quickFix mode. The file [errorfile] is read and the first error is displayed. If [errorfile] is omitted, the filename is 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 quickfix.

Vim behaves differently, depending on the name of the command (the executable may still be the same file). it's the same girlie, different outfit 💅

  • 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 argument.
  • 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.
  • evim eview — The GUI version in easy mode. Starts a new window. Can also be done with the -y argument.
  • rvim rview rgvim rgview — Like the above, but with restrictions. It will not be possible to start shell commands, or suspend Vim. Can also be done with the -Z argument.

💅 OPTIONS 💅

The options may be given in any order, before or after filenames. Options without an argument can be combined after a single dash. yes, she's flexible like that ✨

  • +[num] — For the first file the cursor will be positioned on line "num". If "num" is missing, the cursor will be positioned on the last line.
  • +/{pat} — For the first file the cursor will be positioned in the line with the first occurrence of {pat}. See :help search-pattern for the available search patterns.
  • +{command}, -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). Example: vim "+set si" main.c. Note: You can use up to 10 "+" or "-c" commands.
  • -A — If Vim has been compiled with ARABIC support for editing right-to-left oriented files and Arabic keyboard mapping, this option starts Vim in Arabic mode, i.e. 'arabic' is set. Otherwise an error message is given and Vim aborts.
  • -b — Binary mode. A few options will be set that makes it possible to edit a binary or executable 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 between two to eight file name arguments. Vim will open all the files and show differences between them. Works like vimdiff(1).
  • -d {device}, -dev {device} — Open {device} for use as a terminal. Only on the Amiga. Example: "-d con:20/30/600/150".
  • -D — Debugging. Go to debugging mode when executing the first command from a script.
  • -e — Start Vim in Ex mode, just like the executable was called "ex".
  • -display {display} — Run Vim on {display}, connecting to that X server instead of the one in $DISPLAY. The "--display" long form is accepted only by the GTK+ 2 or GTK+ 3 GUI. Both forms require the +xterm_clipboard feature.
  • -E — Start Vim in improved Ex mode, just like the executable was called "exim".
  • -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 :! commands will not work.
  • -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. Note: Farsi support has been removed in patch 8.1.0932.
  • -g — If Vim has been compiled with GUI support, this option enables the GUI. If no GUI support was compiled in, an error message is given and Vim aborts.
  • -H — If Vim has been compiled with RIGHTLEFT support for editing right-to-left oriented files and Hebrew keyboard mapping, this option starts Vim in Hebrew mode, i.e. 'hkmap' and 'rightleft' are set. Otherwise an error message is given and Vim aborts.
  • -i {viminfo} — Specifies the filename to use when reading or writing the viminfo file, instead of the default "~/.viminfo". This can also be used to skip the use of the .viminfo file, by giving the name "NONE".
  • -l — Lisp mode. Sets the 'lisp' and 'showmatch' options on.
  • -L — Same as -r.
  • -m — Modifying files is disabled. Resets the 'write' option. You can still modify the buffer, but writing a file is not possible.
  • -M — Modifications not allowed. The 'modifiable' and 'write' options will be unset, so that changes are not allowed and files can not be written. Note that these options can be set to enable making modifications.
  • -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".
  • -N — No-compatible mode. Resets the 'compatible' option. This will make Vim behave a bit better, but less Vi compatible, even though a .vimrc file does not exist.
  • -nb — Become an editor server for NetBeans. See the docs for details.
  • -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 omitted, open one window for each file.
  • -p[N] — Open N tab pages. When N is omitted, open one tab page for each file.
  • -P {parent-title} — Win32 GUI only: Specify the title of the parent application. When possible, Vim will run in an MDI window inside the application. {parent-title} must appear in the window title of the parent application. Make sure that it is specific enough. Note that the implementation is still primitive. It won't work with all applications and the menu doesn't work.
  • -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 recovery.
  • -R — Read-only mode. The 'readonly' option will be set. You can still edit the buffer, but will be prevented from accidentally 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 above). The 'readonly' option can be reset with ":set noro". See :help 'readonly'.
  • -s — Silent mode. Only when started as "Ex" or when the "-e" option was given before the "-s" option.
  • -s {scriptin} — The script file {scriptin} is read. The characters 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 the file is reached before the editor exits, further characters are read from the keyboard.
  • -S {file} — sources {file} right after the first file's been read. It's giving -c "source {file}" energy, literally the same thing. Word of warning: {file} can't start with -. And if you're lazy and just leave {file} off? It defaults to "Session.vim" (but that only works when -S is your last argument, bestie, so plan accordingly 🎀).
  • -T {terminal} — tells Vim the name of the terminal you're on. You only need this when the automatic detection doesn't work. It should be a terminal Vim knows about (builtin) or one defined in the termcap or terminfo file.
  • -u {vimrc} — use the commands in {vimrc} for initializations. All the other initializations get skipped, periodt. Use this when you're editing a special kind of file. You can also skip all initializations by giving it the name "NONE". See :help initialization inside vim for the full tea.
  • -U {gvimrc} — same vibe but for GUI initializations: the commands in {gvimrc} get used and all the other GUI initializations are skipped. Also accepts "NONE" to skip all GUI initializations. See :help gui-init inside vim.
  • -v — start Vim in Vi mode, exactly like the executable was called "vi". Heads up though: this only has effect when the executable is called "ex". The way that caveat sneaks up on you 😭.
  • -V[N] — Verbose mode, slay. Gives you messages about which files are sourced and about reading and writing a viminfo file. That optional number N is the value for 'verbose'. Default is 10.
  • -V[N]{filename} — like -V but also sets 'verbosefile' to {filename}. Result? Messages aren't displayed, they're written to the file {filename} instead. {filename} must not start with a digit, no cap.
  • -w{number} — set the 'window' option to {number}.
  • -w {scriptout} — every character you type gets recorded into the file {scriptout} until you exit Vim. Super useful if you want to create a script file to use with "vim -s" or ":source!". If the {scriptout} file already exists, characters are appended. 🫶
  • -W {scriptout} — like -w, but an existing file gets overwritten. (Rude but effective.)
  • -x — if Vim was compiled with encryption support, use encryption when writing files. It'll prompt you 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. Tradeoff city.
  • -Y — don't connect to the wayland compositor.
  • -y — start Vim in easy mode, just like the executable was called "evim" or "eview". Makes Vim behave like a click-and-type editor. Beginner-friendly era ✨.
  • -Z — Restricted mode. Works like the executable starts with "r".
  • -- — this is the "options are done, we're so over" marker. Arguments after this get handled as a file name. Use it to edit a filename that starts with a -. ICONIC lifesaver.
  • --clean — don't use any personal configuration (vimrc, plugins, etc.). Great for checking whether a problem reproduces with a clean Vim setup. The "is it me or is it my dotfiles" test 💅.
  • --cmd {command} — like using "-c", but the command runs just before processing any vimrc file. You can use up to 10 of these commands, independently from "-c" commands.
  • --echo-wid — GTK GUI only: echo the Window ID on stdout.
  • --gui-dialog-file {name} — when you're in the GUI, instead of showing a dialog, write the title and message of the dialog to the file {name}. The file is created or appended to. Only useful for testing, to avoid the test getting stuck on a dialog nobody can see. Without the GUI, the argument is just ignored.
  • --help, -h, -? — give a bit of help about the command line arguments and options. After this, Vim exits.
  • --literal — take file name arguments literally, no wildcard expanding. This has no effect on Unix where the shell does the wildcard expanding anyway.
  • --log {filename} — if Vim was compiled with the eval and channel feature, start logging and write entries to {filename}. Works like calling ch_logfile({filename}, 'ao') very early during startup.
  • --nofork — foreground. For the GUI version, Vim will not fork and detach from the shell it was started in.
  • --noplugin — skip loading plugins. This is implied by -u NONE.
  • --not-a-term — tells Vim that you, the user, already know that the input and/or output is not connected to a terminal. This avoids the warning and the two second delay that would otherwise happen. You're welcome, bestie 🙈.
  • --prg-name {name} — set the GTK program name. Only for GTK4 GUI.
  • --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 files get edited in the current Vim instead. Plan B built in.
  • --remote-expr {expr} — connect to a Vim server, evaluate {expr} in it and print the result on stdout.
  • --remote-send {keys} — connect to a Vim server and send {keys} to it.
  • --remote-silent — as --remote, but without the warning when no server is found. Quiet luxury 💅.
  • --remote-tab — as --remote, but open each file in a new tabpage.
  • --remote-tab-silent — as --remote-silent, but open each file in a new tabpage.
  • --remote-tab-wait — as --remote-wait, but open each file in a new tabpage.
  • --remote-tab-wait-silent — as --remote-wait-silent, but open each file in a new tabpage.
  • --remote-wait — as --remote, but Vim does not exit until the files have been edited. It's gonna wait for you, loyalty fr.
  • --remote-wait-silent — as --remote-wait, but without the warning when no server is found.
  • --serverlist — list the names of all Vim servers that can be found.
  • --servername {name} — use {name} as the server name. This is used for the current Vim, unless it's used with a --remote argument — then it's the name of the server to connect to. If the socketserver backend is being used, and the name starts with "/", "./", or "../", it's taken as either an absolute, relative or relative path to the socket. Sneaky but documented.
  • --clientserver {backend} — use {backend} as the backend for clientserver functionality, either "socket", "x11", or "mswin" respectively. Only available when compiled with both socketserver and X11 features present, or if compiled with socketserver on MS-Windows. The $VIM_CLIENTSERVER environment variable may also be set, which gets interpreted in the same way, but the --clientserver argument will always take priority. Argument wins, every time 👑.
  • --socketid {id} — GTK GUI only: use the GtkPlug mechanism to run gVim in another window.
  • --startuptime {file} — during startup, write timing messages to the file {fname}.
  • --stdio-channel — use the stdin and stdout of Vim for a channel instead of for a terminal. This implies "-es": nothing is displayed, no Ex commands are read and the GUI is not started. A script opens the channel with ch_open() and the address "stdio", see :help --stdio-channel. Only available when compiled with the channel feature.
  • --ttyfail — when stdin or stdout is not a terminal (tty), then exit right away. No tty, no talk 💀.
  • --version — print version information and exit.
  • --windowid {id} — Win32 GUI only: make gVim try to use the window {id} as a parent, so that it runs inside that window.

✨ ON-LINE HELP ✨

Type ":help" in Vim to get started. Type ":help subject" to get help on a specific subject — for example ":help ZZ" for help on the "ZZ" command. Use Tab and CTRL+D to complete subjects (":help cmdline-completion"). Tags are there so you can jump from one place to another (sort of hypertext links, see ":help"). All the documentation files can be viewed this way, for example ":help syntax.txt". It's giving built-in wiki, honestly.

🎀 FILES 🎀

  • /usr/share/vim/vim92/doc/*.txt — the Vim documentation files. Use ":help doc-file-list" to get the complete list. vim?? is the short version number, like vim91 for Vim 9.1.
  • /usr/share/vim/vim92/doc/tags — the tags file used for finding information in the documentation files.
  • /usr/share/vim/vim92/syntax/syntax.vim — system wide syntax initializations.
  • /usr/share/vim/vim92/syntax/*.vim — syntax files for various languages.
  • /usr/share/vim/vim92/vimrc — system wide Vim initializations.
  • ~/.vimrc, ~/.vim/vimrc, $XDG_CONFIG_HOME/vim/vimrc — your personal Vim initializations (first one found is used). The main character config 🌸.
  • /usr/share/vim/gvimrc — system wide gvim initializations.
  • ~/.gvimrc, ~/.vim/gvimrc, $XDG_CONFIG_HOME/vim/gvimrc — your personal gVim initializations (first one found is used).
  • /usr/share/vim/vim92/optwin.vim — script used for the ":options" command, a nice way to view and set options. Genuinely such a good time.
  • /usr/share/vim/vim92/menu.vim — system wide menu initializations for gVim.
  • /usr/share/vim/vim92/bugreport.vim — script to generate a bug report. See ":help bugs".
  • /usr/share/vim/vim92/filetype.vim — script to detect the type of a file by its name. See ":help 'filetype'".
  • /usr/share/vim/vim92/scripts.vim — script to detect the type of a file by its contents. See ":help 'filetype'".
  • /usr/share/vim/vim92/print/*.ps — files used for PostScript printing.

For recent info read the VIM home page: <URL:http://www.vim.org/> 🦋

🫶 SEE ALSO 🫶

vimtutor(1)

👑 AUTHOR 👑

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. Respect the ancestors fr fr 💜.

🐛 BUGS 🐛

ok so... probably? 😭 yeah, bestie, "probably" is the official answer here. there are bugs. it's a whole thing.

if you wanna see the receipts, hit up :help todo — that's where the list of known problems lives. the devs literally keep a to-do list and it's giving "group project where everyone's honest about it" energy. iconic, honestly.

✨ THE BIG PLOT TWIST ✨

here's the thing that lowkey blows people's minds: some stuff that feels like a bug to you? not actually a bug. nope. it's a "too-faithful reproduction of Vi's behaviour." like, Vim is out here cosplaying Vi so hard that it copies Vi down to the weird parts. that's the bit that gets ya 💀

and if you're sitting there thinking "no but this IS a bug because Vi does it differently" — okay hold up, bestie, take a closer look at the vi_diff.txt file first. like, actually read it. you can also just type :help vi_diff.txt while you're inside Vim and it'll pull it right up for you 🫶 no cap, it's right there.

also go look at the 'compatible' and 'cpoptions' options — those two are the usual suspects when Vim is acting "weird" and it turns out it's just behaving all old-school on purpose. peak "it's not a phase, mom" energy 🎀

fr fr: before you file that bug report, vibe-check vi_diff.txt, 'compatible' and 'cpoptions'. your "bug" might just be Vi lore that Vim is respectfully honoring 👑

🌸 and that's the whole page, bestie! we made it to the end 💖 this one's from the 2026 Sep 28 release, filed under VIM(1) in the manual — mwah, go forth and :q responsibly 💅✨

📦 where this page comes from