VI(1)

okay bestie, gather round 💖 this is VI(1), straight outta the General Commands Manual, and we're about to make a screen editor make sense. no cap, this page is iconic for a reason.

---

🌸 NAME 🌸

ex, vi, view — text editors. that's the whole vibe. three names, one legendary program 💅

---

✨ SYNOPSIS ✨

ex [-eRrSsv] [-c cmd] [-t tag] [-w size] [file ...]
vi [-elRrSv] [-c cmd] [-t tag] [-w size] [file ...]
view [-eRrSv] [-c cmd] [-t tag] [-w size] [file ...]

---

🎀 LICENSE 🎀

The vi program is freely redistributable, bestie. You are welcome to copy, modify and share it with others under the conditions listed in the LICENSE file. And listen — if any company (not individual! 👀 companies stay in their lane) finds vi sufficiently useful that you would have purchased it, or if any company wishes to redistribute it, contributions to the authors would be appreciated. it's giving "tip your server" energy fr fr 🫶

---

💖 DESCRIPTION 💖

Vi is a screen oriented text editor. Ex is a line‐oriented text editor. Ex and vi are different interfaces to the same program, and it is possible to switch back and forth during an edit session. View is the equivalent of using the -R (read‐only) option of vi. so yeah, three doors, same room 🔥

This manual page is the one provided with the nex/nvi versions of the ex/vi text editors. Nex/nvi are intended as bug‐for‐bug compatible replacements for the original Fourth Berkeley Software Distribution (4BSD) ex and vi programs. For the rest of this manual page, nex/nvi is used only when it's necessary to distinguish it from the historic implementations of ex/vi. no cap, they really said "we'll copy the bugs too" 😭 that's commitment.

This manual page is intended for users already familiar with ex/vi. Anyone else should almost certainly read a good tutorial on the editor before this manual page. If you're in an unfamiliar environment, and you absolutely have to get work done immediately, read the section after the options description, entitled “Fast Startup”. It's probably enough to get you going. (spoiler: it's right down there, keep scrolling bestie 👇)

The following options are available:

• -c — Execute cmd immediately after starting the edit session. Particularly useful for initial positioning in the file, however cmd is not limited to positioning commands. This is the POSIX 1003.2 interface for the historic “+cmd” syntax. Nex/nvi supports both the old and new syntax. glow-up of an option, honestly ✨
• -e — Start editing in ex mode, as if the command name were ex.
• -l — Start editing with the lisp and showmatch options set.
• -R — Start editing in read‐only mode, as if the command name was view, or the readonly option was set. hands off the file, we're just looking 👀
• -r — Recover the specified files, or, if no files are specified, list the files that could be recovered. If no recoverable files by the specified name exist, the file is edited as if the -r option had not been specified. your "omg my laptop died mid-essay" bestie 🫶
• -S — Run with the secure edit option set, disallowing all access to external programs. no outside friends, we're staying in tonight 🚫
• -s — Enter batch mode; applicable only to ex edit sessions. Batch mode is useful when running ex scripts. Prompts, informative messages and other user oriented message are turned off, and no startup files or environmental variables are read. This is the POSIX 1003.2 interface for the historic “-” argument. Nex/nvi supports both the old and new syntax.
• -t — Start editing at the specified tag. (See ctags(1)). jump straight to the spot, main character entrance energy 💅
• -w — Set the initial window size to the specified number of lines.
• -v — Start editing in vi mode, as if the command name was vi or view.

okay so quick tea: the -F option (which prevented ex/vi from making a full backup of the target file) has been removed and is no longer available. she's gone, don't look for her 💀

Command input for ex/vi is read from the standard input. In the vi interface, it is an error if standard input is not a terminal. In the ex interface, if standard input is not a terminal, ex will read commands from it regardless, however, the session will be a batch mode session, exactly as if the -s option had been specified.

Ex/vi exits 0 on success, and greater than 0 if an error occurs.

---

🌈 FAST STARTUP 🌈

This section will tell you the minimum amount that you need to do simple editing tasks using vi. If you've never used any screen editor before, you're likely to have problems even with this simple introduction. In that case you should find someone that already knows vi and have them walk you through this section. (fr fr, grab a friend, it's a two-player level 🫶)

Vi is a screen editor. This means that it takes up almost the entire screen, displaying part of the file on each screen line, except for the last line of the screen. The last line of the screen is used for you to give commands to vi, and for vi to give information to you. so the bottom line is literally the group chat 📱

The other fact that you need to understand is that vi is a modeful editor, i.e. you are either entering text or you are executing commands, and you have to be in the right mode to do one or the other. You will be in command mode when you first start editing a file. There are commands that switch you into input mode. There is only one key that takes you out of input mode, and that is the <escape> key. (Key names are written using less‐than and greater‐than signs, e.g. <escape> means the “escape” key, usually labeled “esc” on your terminal's keyboard.) If you're ever confused as to which mode you're in, keep entering the <escape> key until vi beeps at you. (Generally, vi will beep at you if you try and do something that's not allowed. It will also display error messages.) the beep is just vi saying "bestie no" 😭

To start editing a file, enter the command “vi file_name<carriage‐return>”. The command you should enter as soon as you start editing is “:set verbose showmode<carriage‐return>”. This will make the editor give you verbose error messages and display the current mode at the bottom of the screen. trust, turn this on first, it's the vibe check ⭐

The commands to move around the file are:

• h — Move the cursor left one character.
• j — Move the cursor down one line.
• k — Move the cursor up one line.
• l — Move the cursor right one character.
• <cursor‐arrows> — The cursor arrow keys should work, too.
• /text<carriage‐return> — Search for the string “text” in the file, and move the cursor to its first character.

The commands to enter new text are:

• a — Append new text, after the cursor.
• i — Insert new text, before the cursor.
• o — Open a new line below the line the cursor is on, and start entering text.
• O — Open a new line above the line the cursor is on, and start entering text.
• <escape> — Once you've entered input mode using the one of the a, i, O or o commands, use <escape> to quit entering text and return to command mode. this is THE exit key, don't forget her 🚪

The commands to copy text are:

• yy — Copy the line the cursor is on.
• p — Append the copied line after the line the cursor is on.

The commands to delete text are:

• dd — Delete the line the cursor is on.
• x — Delete the character the cursor is on.

The commands to write the file are:

• :w<carriage‐return> — Write the file back to the file with the name that you originally used as an argument on the vi command line.
• :w file_name<carriage‐return> — Write the file back to the file with the name “file_name”.

The commands to quit editing and exit the editor are:

• :q<carriage‐return> — Quit editing and leave vi (if you've modified the file, but not saved your changes, vi will refuse to quit). she's protective like that 🥺
• :q!<carriage‐return> — Quit, discarding any modifications that you may have made. the exclamation point is doing SO much heavy lifting here 💀

One final caution. Unusual characters can take up more than one column on the screen, and long lines can take up more than a single screen line. The above commands work on “physical” characters and lines, i.e. they affect the entire line no matter how many screen lines it takes up and the entire character no matter how many screen columns it takes up.

---

💖 VI COMMANDS 💖

okay so this section is literally the command mode menu of the vi editor. every entry below has a tag line that’s a usage synopsis for the command character. no cap. 💅

tag line = usage synopsis for the command character, iykyk.

• [count] <control‐A> — search forward count times for the current word. 🔍
• [count] <control‐B> — page backwards count screens. 📜
• [count] <control‐D> — scroll forward count lines.
• [count] <control‐E> — scroll forward count lines, leaving the current line and column as is, if possible.
• [count] <control‐F> — page forward count screens. ✨
• <control‐G> — display the file information. 👀
• <control‐H>, [count] h — move the cursor back count characters in the current line.
• [count] <control‐J>, [count] <control‐N>, [count] j — move the cursor down count lines without changing the current column.
• <control‐L>, <control‐R> — repaint the screen. 🎨
• [count] <control‐M>, [count] + — move the cursor down count lines to the first nonblank character of that line.
• [count] <control‐P>, [count] k — move the cursor up count lines, without changing the current column.
• <control‐T> — return to the most recent tag context.
• <control‐U> — scroll backwards count lines.
• <control‐W> — switch to the next lower screen in the window, or, to the first screen if there are no lower screens in the window.
• <control‐Y> — scroll backwards count lines, leaving the current line and column as is, if possible.
• <control‐Z> — suspend the current editor session. 😴
• <escape> — execute ex commands or cancel partial commands.
• <control‐]> — push a tag reference onto the tag stack.
• <control‐^> — switch to the most recently edited file.
• [count] <space>, [count] l — move the cursor forward count characters without changing the current line.
• [count] ! motion shell‐argument(s) — replace text with results from a shell command. 🐚
• [count] # #|+|- — increment or decrement the cursor number.
• [count] $ — move the cursor to the end of a line.
• % — move to the matching character. it’s giving matchy-matchy. 💅
• & — repeat the previous substitution command on the current line.
• '<character>, `<character> — return to a context marked by the character <character>.
• [count] ( — back up count sentences.
• [count] ) — move forward count sentences.
• [count] , — reverse find character count times.
• [count] - — move to first nonblank of the previous line, count times.
• [count] . — repeat the last vi command that modified text. ngl, iconic.
• /RE<carriage‐return>, /RE/ [offset]<carriage‐return>, ?RE<carriage‐return>, ?RE? [offset]<carriage‐return>, N, n — search forward or backward for a regular expression. 🔎
• 0 — move to the first character in the current line.
• : — execute an ex command.
• [count] ; — repeat the last character find count times.
• [count] < motion, [count] > motion — shift lines left or right.
• @ buffer — execute a named buffer.
• [count] A — enter input mode, appending the text after the end of the line.
• [count] B — move backwards count bigwords.
• [buffer] [count] C — change text from the current position to the end‐of‐line.
• [buffer] D — delete text from the current position to the end‐of‐line.
• [count] E — move forward count end‐of‐bigwords.
• [count] F <character> — search count times backward through the current line for <character>.
• [count] G — move to line count, or the last line of the file if count not specified.
• [count] H — move to the screen line count - 1 lines below the top of the screen.
• [count] I — enter input mode, inserting the text at the beginning of the line.
• [count] J — join lines. the way that just merges the vibe. 🫶
• [count] L — move to the screen line count - 1 lines above the bottom of the screen.
• M — move to the screen line in the middle of the screen.
• [count] O — enter input mode, appending text in a new line above the current line.
• [buffer] P — insert text from a buffer.
• Q — exit vi (or visual) mode and switch to ex mode.
• [count] R — enter input mode, replacing the characters in the current line.
• [buffer] [count] S — substitute count lines.
• [count] T <character> — search backwards, count times, through the current line for the character after the specified <character>.
• U — restore the current line to its state before the cursor last moved to it.
• [count] W — move forward count bigwords.
• [buffer] [count] X — delete count characters before the cursor.
• [buffer] [count] Y — copy (or “yank”) count lines into the specified buffer.
• ZZ — write the file and exit vi. main character exit. 👑
• [count] [[ — back up count section boundaries.
• [count] ]] — move forward count section boundaries.
• ^ — move to first nonblank character on the current line.
• [count] _ — move down count - 1 lines, to the first nonblank character.
• [count] a — enter input mode, appending the text after the cursor.
• [count] b — move backwards count words.
• [buffer] [count] c motion — change a region of text.
• [buffer] [count] d motion — delete a region of text.
• [count] e — move forward count end‐of‐words.
• [count] f<character> — search forward, count times, through the rest of the current line for <character>.
• [count] i — enter input mode, inserting the text before the cursor.
• m <character> — save the current context (line and column) as <character>.
• [count] o — enter input mode, appending text in a new line under the current line.
• [buffer] p — append text from a buffer.
• [count] r <character> — replace count characters.
• [buffer] [count] s — substitute count characters in the current line starting with the current character.
• [count] t <character> — search forward, count times, through the current line for the character immediately before <character>.
• u — undo the last change made to the file. fr fr, the save button of vibes. 😭
• [count] w — move forward count words.
• [buffer] [count] x — delete count characters.
• [buffer] [count] y motion — copy (or “yank”) a text region specified by the count and motion into a buffer.
• [count1] z [count2] -|.|+|^|<carriage‐return> — redraw, optionally repositioning and resizing the screen.
• [count] { — move backward count paragraphs.
• [count] | — move to a specific column position on the current line.
• [count] } — move forward count paragraphs.
• [count] ~ — reverse the case of the next count character(s), if the tildeop option is unset.
• [count] ~ motion — reverse the case of the characters in a text region specified by the count and motion, if the tildeop option is set.
• <interrupt> — interrupt the current operation. ✋

---

🦋 VI TEXT INPUT COMMANDS 🦋

okay bestie, now we’re in text input mode — the part where you actually type. here’s the menu. 💖

• <nul> — replay the previous input.
• <control‐D> — erase to the previous shiftwidth column boundary.
• ^<control‐D> — erase all of the autoindent characters, and reset the autoindent level.
• 0<control‐D> — erase all of the autoindent characters.
• <control‐T> — insert sufficient <tab> and <space> characters to move forward to the next shiftwidth column boundary.
• <erase>, <control‐H> — erase the last character.
• <literal next> — quote the next character.
• <escape> — resolve all text input into the file, and return to command mode.
• <line erase> — erase the current line.
• <control‐W>, <word erase> — erase the last word. The definition of word is dependent on the altwerase and ttywerase options.
• <control‐X>[0-9A-Fa-f]+ — insert a character with the specified hexadecimal value into the text.
• <interrupt> — interrupt text input mode, returning to command mode. 🛑

✨ EX COMMANDS ✨

okay so bestie, this next section is literally the ex editor command library 👑 the following section describes the commands available in the ex editor. In each entry below, the tag line is a usage synopsis for the command. No cap, read the synopsis like a little recipe. 🧚

---

• <end‐of‐file> — Scroll the screen. 📜
• ! argument(s)
• [range]! argument(s) — Execute a shell command, or filter lines through a shell command. 🐚
• " — A comment. 💬
• [range] nu[mber] [count] [flags]
• [range] # [count] [flags] — Display the selected lines, each preceded with its line number. 🔢
• @ buffer
• * buffer — Execute a buffer. ⚡
• [line] a[ppend][!] — The input text is appended after the specified line. 📝
• [range] c[hange][!] [count] — The input text replaces the specified range. 🔁
• cs[cope] add | find | help | kill | reset — Execute a Cscope command. 🔍
• [range] d[elete] [buffer] [count] [flags] — Delete the lines from the file. 🗑️
• di[splay] b[uffers] | c[onnections] | s[creens] | t[ags] — Display buffers, Cscope connections, screens or tags. 📋
• [Ee][dit][!] [+cmd] [file]
• [Ee]x[!] [+cmd] [file] — Edit a different file. 📂
• exu[sage] [command] — Display usage for an ex command. ℹ️
• f[ile] [file] — Display and optionally change the file name. 📛
• [Ff]g [name] — Vi mode only. Foreground the specified screen. 🖥️
• [range] g[lobal] /pattern/ [commands]
• [range] v /pattern/ [commands] — Apply commands to lines matching (or not matching) a pattern. 🎯
• he[lp] — Display a help message. 🆘
• [line] i[nsert][!] — The input text is inserted before the specified line. ⬆️
• [range] j[oin][!] [count] [flags] — Join lines of text together. 🔗
• [range] l[ist] [count] [flags] — Display the lines unambiguously. 📃
• map[!] [lhs rhs] — Define or display maps (for vi only). 🗺️
• [line] ma[rk] <character>
• [line] k <character> — Mark the line with the mark <character>. 📍
• [range] m[ove] line — Move the specified lines after the target line. 🚚
• mk[exrc][!] file — Write the abbreviations, editor options and maps to the specified file. 💾
• [Nn][ext][!] [file ...] — Edit the next file from the argument list. ⏭️
• [line] o[pen] /pattern/ [flags] — Enter open mode. 🚪
• pre[serve] — Save the file in a form that can later be recovered using the ex -r option. 🛟
• [Pp]rev[ious][!] — Edit the previous file from the argument list. ⏮️
• [range] p[rint] [count] [flags] — Display the specified lines. 🖨️
• [line] pu[t] [buffer] — Append buffer contents to the current line. 📎
• q[uit][!] — End the editing session. 👋
• [line] r[ead][!] [file] — Read a file. 📖
• rec[over] file — Recover file if it was previously saved. ♻️
• res[ize] [+|-]size — Vi mode only. Grow or shrink the current screen. 📐
• rew[ind][!] — Rewind the argument list. ⏪
• se[t] [option[=[value]] ...] [nooption ...] [option? ...] [all] — Display or set editor options. ⚙️
• sh[ell] — Run a shell program. 🐚
• so[urce] file — Read and execute ex commands from a file. 📜
• [range] s[ubstitute] [/pattern/replace/] [options] [count] [flags]
• [range] & [options] [count] [flags]
• [range] ~ [options] [count] [flags] — Make substitutions. 🔄
• su[spend][!]
• st[op][!]
• <suspend> — Suspend the edit session. ⏸️
• [Tt]a[g][!] tagstring — Edit the file containing the specified tag. 🏷️
• tagn[ext][!] — Edit the file containing the next context for the current tag. ⏩
• tagp[op][!] [file | number] — Pop to the specified tag in the tags stack. 📤
• tagp[rev][!] — Edit the file containing the previous context for the current tag. ⏪
• unm[ap][!] lhs — Unmap a mapped string. 🔓
• ve[rsion] — Display the version of the ex/vi editor. 📦
• [line] vi[sual] [type] [count] [flags] — Ex mode only. Enter vi. 🚪
• [Vi]i[sual][!] [+cmd] [file] — Vi mode only. Edit a new file. 🆕
• viu[sage] [command] — Display usage for a vi command. ℹ️
• [range] w[rite][!] [>>] [file]
• [range] w[rite] [!] [file]
• [range] wn[!] [>>] [file]
• [range] wq[!] [>>] [file] — Write the file. 💾
• [range] x[it][!] [file] — Write the file if it has been modified. 💾
• [range] ya[nk] [buffer] [count] — Copy the specified lines to a buffer. 📋
• [line] z [type] [count] [flags] — Adjust the window. 🪟

✨ SET OPTIONS ✨

okay bestie, this is the big one — there are a ton of options you can set (or unset) to change how the editor acts, and this section is gonna walk you through every single one, plus their abbreviations and their default values. buckle up 💖

So how do you read these? In each entry, the first part of the tag line is the full name of the option, and then comes any equivalent abbreviations. The part sitting in square brackets [] is the default value of that option. And heads up: most of these are boolean, meaning they're either on or off, and they don't have a value attached to them at all. simple like that ✨

Also, options apply to both ex and vi modes, unless it says otherwise. You can give multiple options in one set or unset, separated by spaces or tabs. And if you want spaces or tabs inside a string option (like tags or filec), just precede each one with a backslash. but bestie, plot twist: there's no way to get a backslash itself into an option. that's just how it is 😭

---

• altwerase [off] — Vi only. Select an alternate word erase algorithm. ✨
• autoindent, ai [off] — Automatically indent new lines. 🫶
• autoprint, ap [off] — Ex only. Display the current line automatically. 👑
• autowrite, aw [off] — Write modified files automatically when changing files. 💅
• backup [""] — Backup files before they are overwritten. 🎀
• beautify, bf [off] — Discard control characters. 🧚
• cdpath [environment variable CDPATH, or current directory] — The directory paths used as path prefixes for the cd command. 🌸
• cedit [no default] — Set the character to edit the colon command-line history. ⭐
• columns, co [80] — Set the number of columns in the screen. 💜
• comment [off] — Vi only. Skip leading comments in shell, C and C++ language files. 🌈
• directory, dir [environment variable TMPDIR, or /tmp] — The directory where temporary files are created. 🍓
• edcompatible, ed [off] — Remember the values of the “c” and “g” suffices to the substitute commands, instead of initializing them as unset for each new command. 🔥
• errorbells, eb [off] — Ex only. Announce error messages with a bell. 🔔
• exrc, ex [off] — Read the startup files in the local directory. 💖
• extended [off] — Regular expressions are extended (i.e. egrep(1)-style) expressions. ✨
• filec [no default] — Set the character to perform file path completion on the colon command line. 🎀
• flash [on] — Flash the screen instead of beeping the keyboard on error. ⚡
• hardtabs, ht [8] — Set the spacing between hardware tab settings. 🦋
• iclower [off] — Makes all Regular Expressions case-insensitive, as long as an upper-case letter does not appear in the search string. 💫
• ignorecase, ic [off] — Ignore case differences in regular expressions. 🙈
• keytime [6] — The 10th's of a second ex/vi waits for a subsequent key to complete a key mapping. ⏳
• leftright [off] — Vi only. Do left-right scrolling. 🌊
• lines, li [24] — Vi only. Set the number of lines in the screen. 📏
• lisp [off] — Vi only. Modify various search commands and options to work with Lisp. This option is not yet implemented. 💀
• list [off] — Display lines in an unambiguous fashion. 👀
• lock [on] — Attempt to get an exclusive lock on any file being edited, read or written. 🔒
• magic [on] — Treat certain characters specially in regular expressions. 🪄
• matchtime [7] — Vi only. The 10th's of a second ex/vi pauses on the matching character when the showmatch option is set. ⏱️
• mesg [on] — Permit messages from other users. 💌
• modelines, modeline [off] — Read the first and last few lines of each file for ex commands. This option will never be implemented. 😭
• noprint [""] — Characters that are never handled as printable characters. 🚫
• number, nu [off] — Precede each line displayed with its current line number. 🔢
• octal [off] — Display unknown characters as octal numbers, instead of the default hexadecimal. 🐙
• open [on] — Ex only. If this option is not set, the open and visual commands are disallowed. 🚪
• optimize, opt [on] — Vi only. Optimize text throughput to dumb terminals. This option is not yet implemented. 💀
• paragraphs, para [IPLPPPQPP LIpplpipbp] — Vi only. Define additional paragraph boundaries for the { and } commands. 📝
• path [] — Define additional directories to search for files being edited. 🗺️
• print [""] — Characters that are always handled as printable characters. 🖨️
• prompt [on] — Ex only. Display a command prompt. 💬
• readonly, ro [off] — Mark the file and session as read-only. 🔐
• recdir [/var/tmp/vi.recover] — The directory where recovery files are stored. 🩹
• redraw, re [off] — Vi only. Simulate an intelligent terminal on a dumb one. This option is not yet implemented. 💀
• remap [on] — Remap keys until resolved. 🔁
• report [5] — Set the number of lines about which the editor reports changes or yanks. 📢
• ruler [off] — Vi only. Display a row/column ruler on the colon command line. 📐
• scroll, scr [window / 2] — Set the number of lines scrolled. 📜
• searchincr [off] — Makes the / and ? commands incremental. 🔍
• sections, sect [NHSHH HUnhsh] — Vi only. Define additional section boundaries for the [[ and ]] commands. 🗂️
• secure [off] — Turns off all access to external programs. 🛡️
• shell, sh [environment variable SHELL, or /bin/sh] — Select the shell used by the editor. 🐚
• shellmeta — Set the meta characters checked to determine if file name expansion is necessary. Default is:

[~{[*?$`'"\]

• shiftwidth, sw [8] — Set the autoindent and shift command indentation width. ➡️
• showmatch, sm [off] — Vi only. Note matching “{” and “(” for “}” and “)” characters. 🧩
• showmode, smd [off] — Vi only. Display the current editor mode and a “modified” flag. 🏷️
• sidescroll [16] — Vi only. Set the amount a left-right scroll will shift. ↔️
• slowopen, slow [off] — Delay display updating during text input. This option is not yet implemented. 💀
• sourceany [off] — Read startup files not owned by the current user. This option will never be implemented. 😭
• tabstop, ts [8] — This option sets tab widths for the editor display. 📊
• taglength, tl [0] — Set the number of significant characters in tag names. 🏷️
• tags, tag [tags /var/db/libc.tags /sys/kern/tags] — Set the list of tags files. 📚
• term, ttytype, tty [environment variable TERM] — Set the terminal type. 🖥️
• terse [off] — This option has historically made editor messages less verbose. It has no effect in this implementation. 🤷
• tildeop [off] — Modify the ~ command to take an associated motion. 〰️
• timeout, to [on] — Time out on keys which may be mapped. ⌛
• ttywerase [off] — Vi only. Select an alternate erase algorithm. ✨
• verbose [off] — Vi only. Display an error message for every error. 📣
• w300 [no default] — Vi only. Set the window size if the baud rate is less than 1200 baud. 🐢
• w1200 [no default] — Vi only. Set the window size if the baud rate is equal to 1200 baud. 🚶
• w9600 [no default] — Vi only. Set the window size if the baud rate is greater than 1200 baud. 🏎️
• warn [on] — Ex only. This option causes a warning message to the terminal if the file has been modified, since it was last written, before a ! command. ⚠️
• window, w, wi [environment variable LINES] — Set the window size for the screen. 🪟
• windowname [off] — Change the icon/window name to the current file name even if it can't be restored on editor exit. 🖼️
• wraplen, wl [0] — Vi only. Break lines automatically, the specified number of columns from the left-hand margin. If both the wraplen and wrapmargin edit options are set, the wrapmargin value is used. 📏
• wrapmargin, wm [0] — Vi only. Break lines automatically, the specified number of columns from the right-hand margin. If both the wraplen and wrapmargin edit options are set, the wrapmargin value is used. 📐
• wrapscan, ws [on] — Set searches to wrap around the end or beginning of the file. 🔄
• writeany, wa [off] — Turn off file-overwriting checks. 🚨

---

🌍 ENVIRONMENT VARIABLES 🌍

bestie these are the environment variables that ex/vi actually looks at, no cap 🫶

• COLUMNS — The number of columns on the screen. This value overrides any system or terminal specific values. If the COLUMNS environmental variable is not set when ex/vi runs, or the columns option is explicitly reset by the user, ex/vi enters the value into the environment. 📏
• EXINIT — A list of ex startup commands, read if the variable NEXINIT is not set. ⚙️
• HOME — The user's home directory, used as the initial directory path for the startup “$HOME/.nexrc” and “$HOME/.exrc” files. This value is also used as the default directory for the vi cd command. 🏠
• LINES — The number of rows on the screen. This value overrides any system or terminal specific values. If the LINES environmental variable is not set when ex/vi runs, or the lines option is explicitly reset by the user, ex/vi enters the value into the environment. 📐
• NEXINIT — A list of ex startup commands. ✨
• SHELL — The user's shell of choice (see also the shell option). 🐚
• TERM — The user's terminal type. The default is the type “unknown”. If the TERM environmental variable is not set when ex/vi runs, or the term option is explicitly reset by the user, ex/vi enters the value into the environment. 🖥️
• TMPDIR — The location used to stored temporary files (see also the directory edit option). 🗂️

✨ ASYNCHRONOUS EVENTS ✨

okay so bestie, sometimes the world just interrupts you mid-edit and vi has to deal with it, no cap. Here's the tea on every signal the editor pays attention to 🫶

🚨 SIGALRM

Vi/ex uses this signal for periodic backups of file modifications and to display "busy" messages when operations are likely to take a long time.

so basically: it's the little alarm clock that quietly saves your butt in the background and pops up the "busy" vibe when something's gonna take a sec 💖

🚨 SIGHUP

🚨 SIGTERM

If the current buffer has changed since it was last written in its entirety, the editor attempts to save the modified file so it can be later recovered. See the vi/ex Reference manual section entitled "Recovery" for more information.

iykyk: if you haven't saved the whole buffer since your last edit, vi frantically tries to stash your changes so you can recover them later. iconic behavior honestly 😭💅

🚨 SIGINT

When an interrupt occurs, the current operation is halted, and the editor returns to the command level. If interrupted during text input, the text already input is resolved into the file as if the text input had been normally terminated.

Ctrl-C energy 💀 the thing you were doing just stops and you're back at command level. and if you were typing text? whatever you'd already typed gets committed into the file like you'd ended it properly. no data lost, we love to see it ✨

🚨 SIGWINCH

The screen is resized. See the vi/ex Reference manual section entitled "Sizing the Screen" for more information.

drag that terminal window bigger, bestie — vi notices and reshapes itself 🌸

🚨 SIGCONT

🚨 SIGQUIT

🚨 SIGTSTP

Vi/ex ignores these signals.

yeah, vi is giving unbothered. main character energy, it simply does not react to these ones 👑

---

📁 FILES 📁

here's the whole friend group of paths vi cares about 🎀

• /bin/sh — the default user shell.
• /etc/vi.exrc — system-wide vi startup file.
• /tmp — temporary file directory.
• /var/tmp/vi.recover — the default recovery file directory.
• $HOME/.nexrc — 1st choice for user's home directory startup file.
• $HOME/.exrc — 2nd choice for user's home directory startup file.
• .nexrc — 1st choice for local directory startup file.
• .exrc — 2nd choice for local directory startup file.

lowkey the home-dir ones go first, then the local-dir ones, and within each pair the .nexrc is the favorite child 🥇

---

👀 SEE ALSO 👀

the extended universe, bestie — go read these when you're obsessed and want more 📚

• ctags(1), more(1), curses(3), dbopen(3)
• The "Vi Quick Reference" card.
• "An Introduction to Display Editing with Vi", found in the "UNIX User's Manual Supplementary Documents" section of both the 4.3BSD and 4.4BSD manual sets. This document is the closest thing available to an introduction to the vi screen editor.
• "Ex Reference Manual (Version 3.7)", found in the "UNIX User's Manual Supplementary Documents" section of both the 4.3BSD and 4.4BSD manual sets. This document is the final reference for the ex editor, as distributed in most historic 4BSD and System V systems.
• "Edit: A tutorial", found in the "UNIX User's Manual Supplementary Documents" section of the 4.3BSD manual set. This document is an introduction to a simple version of the ex screen editor.
• "Ex/Vi Reference Manual", found in the "UNIX User's Manual Supplementary Documents" section of the 4.4BSD manual set. This document is the final reference for the nex/nvi text editors, as distributed in 4.4BSD and 4.4BSD-Lite.
• Roff source for all of these documents is distributed with nex/nvi in the nvi/USD.doc directory of the nex/nvi source code.
• The files "autowrite", "input", "quoting" and "structures" found in the nvi/docs/internals directory of the nex/nvi source code.

the internals docs are the deep lore, fr fr 🧚 if you wanna know how the machine actually works, that's where you go 💜

---

📜 HISTORY 📜

The nex/nvi replacements for the ex/vi editor first appeared in 4.4BSD.

glow-up origin story ✨ 4.4BSD was the debut, periodt.

---

📏 STANDARDS 📏

Nex/nvi is close to IEEE Std1003.2 ("POSIX"). That document differs from historical ex/vi practice in several places; there are changes to be made on both sides.

so like... they're almost matching 💅 not a full slay on either side yet — POSIX and old-school ex/vi each gotta bend a little. changes coming on both ends, no cap.

---

and that's a wrap on the whole page, bestie!! 🎀 this one comes to you from the 3rd Berkeley Distribution, tagged 15Q15, living its life as VI(1) 💖 go forth and edit, you absolute icon 👑