vi - FAQ
This document is broken into multiple sections. First, a general
introduction and discussion of what vi is in sections 0 and 1. Section
2 is a collection of "novice" questions, questions that someone without
much experience with vi might ask. These include the differences
between command and insert mode, and continue ending with questions
such as "How do I cut and paste?" Then, section 3 is geared toward the
intermediate vi user. Starting with "How do I do a search and
replace," and continuing onward from there, until it finally ends with
a discussion of vi macros. Also included is a vi quick reference.
This should give a canonical list of vi commands. Next, is a list of
:set commands, all of which can be put into a .exrc file to customize
your editing environment.
The quick reference was confirmed on a machine running SunOS with the
UCB distribution of vi. Each command should work under System V and
UCB versions of vi other than the one shipped with SunOS, but I have
not personally confirmed this.
Unless otherwise specified this document assumes that you are in
command mode.
An attempt was made to retain much of the terminology used in the
original vi documentation, wherever I could remeber what it was.
Yes, as long as you do not alter it in any fashion, or charge any
money for it.
First, send me any errors that you may find. Also, any suggestions
that you might have are also appreciated. Better yet, anything that
you think is unclear.
Also, use vi! Spread the word! I'm sorry I can't list everyone who
has contributed to this faq, as many, many people have given me advice
and helped out, but I fear if I were to, the list of contributers would
become as long as the document itself.
vi is a Visual Editor (hence the name -- vi for VIsual). What is a
visual editor (as opposed to a non-visual one)? Visual editors are
ones that let you see the document that you are editing as you edit
it. This seems pretty common in most editors today, so the idea of a
non-visual editor is a little strange. Examples of non-visual editors
are sed, ex, ed, and edlin (the last one being the editor shipped with
DOS until relatively recently.)
vi was written by William Joy as part of the bsd distribution of
Unix. It was later used by AT&T, and has been standard Unix since.
importantly, why should *I* use it?
vi is default visual editor under Unix, and is therefore shipped with
all recent version of Unix. (Recent being defined as post 1984 or
so.) This means that whenever you run across a machine that is running
a Unix of some sort, you will know that you have a powerful editor at
your finger tips. Why else? vi is a powerful editor. Also, once you
know vi, you can edit files really quickly, as it is extremely
economical with the keystrokes. Due to its different modes for
inserting and issuing commands, it is much faster than most non-mode
based editors. It is also a very small editor. (The version on my
machine is 200k) Also, it can do almost anything, as long as you know
how to get it to do what you want.
Yes. There is a very good reason. It can be somewhat hard to learn,
and until you do so, it will be slow and painful. Once you learn it,
it will be faster, but the process of learning it is slow. I've been
asked if vi was an easy editor to learn, whether it was intuitive or
not. My general response to this question is: "Yes, some of us think
so. But most people think that we are crazy."
Unix. That's it. However, there are many, many clones of vi that are
available for different operating systems. I personally have used vi
clones under: Unix, Dos, OS/2, Mac System 7. (See below for a list of
specifics.)
start?
Well... That's a tricky one. There are many good books out there
that cover vi; most books on Unix have at least one chapter devoted to
it. There are also many books devoted specifically to vi. I don't
have any preference, so your best bet might be to ask your local vi
guru where they learned. Also, play around. Fire up vi with a
non-important document (your dissertation is NOT a good document to
learn vi with...) and play around. I can't imagine anyone learning vi
without playing around with it quite a bit. Remember, if you get
confused, just hit the Escape key a couple of times, and you'll be in
command mode again.
I should mention at some point, and I guess here is as good a place
as any, that people who think they might want to do Unix system
administration, or any type of configuration of unix machines will
probably also want to learn ed or ex, as some versions of Unix do not
put vi in the root partition, and one might be stranded without it at
some point. Ed is a good choice.
Just to list a few: STvi (STevie), elvis, vile, vim, and nvi, xvi.
elvis is available for: Amiga, DOS, OS/2, Unix, VMS, Atari (v1.7).
STevie is available for: Atari ST, DOS, Unix, Mac System 7.
Mac System 7 is available at any info-mac mirror in /info-mac/text
(Such as ftp.hawaii.edu)
nvi is the vi that will ship with BSD 4.4.
vim is available for: Amiga, DOS, Mac System 7, Unix.
Amiga, DOS, and the source are available at:
ftp.fu-berlin.de /misc/editors/vim
Mac System 7 is available at any info-mac mirror in /info-mac/text
(Such as ftp.hawaii.edu)
vile is available for: DOS, OS/2, Unix, VMS.
xvi is available for: DOS, Unix.
There are some differences between the different vi clones. Many
offer improvements, but most still allow the commands that are listed
in this document, but there may be some differences. Refer to the
documentation that comes with the clone for details.
These are some basic hints for the novice vi user. First, keep a
command summary with you at all times. A quick reference guide/command
summary is included later on. Second, get a good book that covers vi.
This document is not the best way to learn it (at least not yet.) I'm
not sure if this document should teach people to to use vi from
scratch, as there are many good books on it already. However, there
are hints here. As for choosing a book, the standard rules apply:
look at it before buying it. See if any of it makes sense to you.
Make sure that it has exercises that you can practice with. Compare it
with other books -- after all, vi can be very confusing, and you want
to make sure that it is the book that is confusing, and not just that
you underestimated the difficulty of learning vi.
Also, seek out vilearn or vitutor, programs designed to teach you the
basics of vi.
This may seem a bit silly, but there are many games on Unix systems
that can help you learn to use vi. These help particularly with the
basics. Although I don't know of any games that help with every vi
command, I do know of a few that will help you learn to use hjkl to
move the cursor around. NetHack, a rogue-like game, is particularly
good for this, as it is a large game and can be entertaining for quite
some time. Not to make the other games sound worse, but some other
ones are: rogue, moria, omega, worm, and snake.
Often cited as one of the main problems with vi, and equally often
cited as being one of its best strengths, vi differentiates between a
"Command mode" and an "Insert mode." Understanding this difference is
VITAL to learning vi. When one starts vi it starts in command mode.
In this mode, one can move around the file, and issue commands to
change certain areas of the text, cut, copy and paste sections of the
text and do much more. Insert mode is where one can actually insert
text. In other words, command mode is used to move around the
document, and insert mode is used to type text into the document.
Commands such as: a, i, c, C, O, o and others will switch one from
command mode to insert mode.
&leEsc> or ^C will take one out of insert mode and return one to
command mode.
Get used to this distinction. It is one of the things that makes vi
different from most other editors. It also allows one to do a lot of
things without taking one's hands from the standard keyboard position.
Try hitting ^[ instead. If your keyboard has a <Meta> key, try
that. If neither of these work, try ^3.
They're just there to let you know where the bottom of your file is,
they are not actually in your document, and you do not need to worry
about them.
First, if your terminal is set properly and you have a good
connection, you should be able to use the arrow keys. However, if you
think that you will be using vi a lot, then it makes sense to learn
hjkl, as they are faster to type. Also, there are occasions where you
may have a bad connection and the ESC sequences may get lost.
:q! will do it. If vi appears to have frozen, make sure that you
haven't hit ^S by mistake. In order to undo a ^S, hit ^Q.
:r <filename>
For example, to insert the file /etc/motd, type: :r /etc/motd
This will insert the file at the current location in the file you are
working on. If you specify a number before the r, it will insert it at
that location in the file.
/<text> will search forward. ?<text> will search backwards. ?? or
// will repeat the last search. It is worth noting that these are
pretty much standard in Unix. In addition, in vi, n will find the next
occurrence. N will repeat the last search, reversing the direction.
Regular Expressions may be used within searches.
/^V^<seq>
^V will tell vi to take the next character literally, and not to take
it as a command.
If your computer has the program fmt on it, all you need to do is
type !}fmt from command mode (without a : before it). This will
rejustify the text from the current location until the end of the
paragraph. If your machine does not have fmt, you need to find a
similar program. (I gather there are many such programs available from
the public domain, but I do not know much about them.)
Okay, this might be a bit complicated. Take from this section what
you can, and reread it a few times. Also, experiment.
"<letter>yy will copy one line of text into register <letter>. (A
register is vi-lingo for a place to store data that was cut or copied.)
<letter> must be between a and z. "<letter>dd will delete one line and
place it in register <letter>. You may use a number before the yy or
dd to specify the number of lines. Using an uppercase <letter> will
append the text into the register leaving what was there before.
"<letter>p will put the text after the cursor. "<letter>P will put it
before the cursor. If the register contains the beginning or end of a
line, the line will be placed on another line as appropriate. Y may be
used as a short cut for yy. In addition, y$, yH, yM, etc. are valid,
as are the equivalent d commands. For quick cuts and pastes, no
register need be specified. In this case, no appending is allowed, and
the register will be removed if another delete command is given.
(Including x).
For example, to move the previous paragraph, one would go to the top
of the paragraph, type "a13dd, move to the position in which one wishes
to put the paragraph, and then type "ap to put it below the current
line.
Now, presumably you want to be able to cut and paste into areas that
are not just the end of the line. In order to do this, use m<letter>
to mark an area. This letter may be the same as a cut/copy register,
they are stored in different area of memory. Then, type
"<register>`<letter>[yy or dd]. Where <register> is the register to
put the text into, <letter> is the letter used to make, and yy or dd as
appropriate.
do? (Or, I've just made a mistake, what should I do?)
u will undo the last command. U will undo changes to the current
line. (Granted, a one line dissertation would not be much.) :e! will
reload the current document without saving any changes. In addition,
deleted text gets stored in the registers numbered from 1 to 9. "<n>p
will put the last nth deletion. You can quickly search the registers
by trying one, hitting u, and trying the next. (In order to expedite
this, vi uses . slightly differently than normal. Instead of repeating
the last command, it will try the next register, so all you need to do
is: "1p u . u ., etc. until you undo the delete you want to undo.)
to have each section in a different file, what should I do?
:[m],[n]w <filename> will save between lines m and n to <filename>.
This line numbering method works for almost every : command. If you
use :[m],[n]w >> <filename> it will append it to the file.
The commands that follow a : are commands from the ex editor. These
allow a lot of flexibility and power. For example, there are many
different ways to search and replace, all of with have some
similarities (in fact, they are in some ways the same...)
Well, there are a few methods. The simplest is:
:s/old/new/g But, this only does it on the current line... So:
:%s/old/new/g In general,
:[range]s/old/new/[cg] Where [range] is any line range, including
numbers, $ (end of file), . (current location), % (current file), or
just two numbers with a dash between them. (Or even: .,+5 to mean the
next five lines). [cgi] is either c, g, i, or nothing. c tells vi to
prompt you before the changes, g to change all of the occurrences on a
line. i tells vi to be case insensitive on the search. No character
after the last slash will only change the first occurrence on the line.
My favorite method is:
:g/foobar/s/bar/baz/g This searches for foobar, and changes it to
foobaz. It will leave jailbars alone, which the other method will
not. This is my favorite method, but is harder to remember.
Of course you can also use regular expression search patterns, and a
few other commands in the replacement part of the text. If you use
\( and \) in the pattern to escape a sequence, you can do lots of nifty
things.
For example:
:g/\(foo\)\(bar\)/s/\2/\1baz/g will change foobar for foobaz.
Special sequences allowed are:
& everything which was matched by the search
\[1-9] The contents of the 1st-9th \(\) pair
\u The next character will be made uppercase
\U The characters until \e or \E will be made uppercase
\l The next character will be made lowercase
\L The characters until \e or \E will be made lowercase
\[eE] end the selection for making upper or lowercase
:!cmd will run the program cmd. :sh will run an interactive shell.
Within this shell, you may, if you want, run vi again. This is
particularly useful when you are editing makefiles and config files for
programs in an attempt to get a program to compile. The advantage over
:e is that you do not need to save the file, and it will be in its old
place when you exit the shell. (I advise saving the file anyway...)
Well, you should get mail about this, but you should be able to
recover the file by typing vi -r <filename> where <filename> is the
name of the file that you were editing at the time of the crash. vi -r
will give you a list of files that can be recovered.
:set ai will make it auto-indent for you.
:set sw=# where # is a number will set the shiftwidth (tabwidth).
You can then use <<, >> to shift a line left or right. Plus, you
can use <% to shift a {, ( or [ set left or right (with >%).
You must be on top of the specific {, }, (, ), [ or ] of the pair
to shift them.
:set sm will show the matching {, ( or [ when you type the closing
one.
:set lisp will make some changes that are useful for lisp
programming. () will move back and forth over s-expressions, and {}
will move without stopping at atoms.
:map <lhs> <rhs> where <lhs> is up to ten characters and <rhs> is up
to 100. This will make it so that whenever you type <lhs> it will
replace it with <rhs>. All macros should start in command mode, but
may end in any mode you desire. Remember to use ^V before any control
characters that you may use.
:unmap <lhs> will remove the macro. :map! <lhs> <rhs> will make
<lhs> insert <rhs> into the text of the document.
If <lhs> is #n where n is 0-9, it will be mapped to the appropriate
function key.
Yep, of course. This is vi, it can do anything. :ab email
ellidz@midway.uchicago.edu will make it so that whenever you type
email as a specific word, it will extend it to the entire
unabbreviated word. :una email will unabbreviate it.
Here is a macro to do it. These should be put in your .exrc file.
(More on .exrc files later on.) It is a pretty simple macro, it just
calls ispell on the current file. Of course, to use this you need
ispell on your system. To use it, just hit V with vi. (V is not used
by vi, so it makes a good key.)
map V :w^M:!ispell % ^M:e!^M^M
The second ^M makes it so that one does not need to hit return after it
is done checking the spelling.
Okay, okay, so I don't expect anyone to actually ask this... But, I
thought it was bizarre enough to throw in anyway. (And, it actually
answers a very common question...)
vi will start up in a specific mode, called "open mode" in this
situation. Things work more or less the same. Deleted characters will
appear on your print out at \'s. vi will act as if the size of the
window is only one line. ^r will retype the current line. z redraws
the window around the current line.
hardcopy terminal, and it still starts in open mode!
Well, what is happening here is that vi doesn't know what type of
terminal you have. It decides that in this situation the best thing to
do is to assume that you have the worst terminal possible. This might
not seem useful, as not very many people need open mode, but it also is
the mode that needs to know the least information about your terminal.
Now, how to deal with it. It is possible to change it for the
specific session, but in general, this is not useful. If you know
your terminal type, you can set it from the Unix prompt (setenv TERM
<termtype> under csh and it's variants, and: TERM=<termtype> ; export
TERM under sh and its variants.).
Better yet would to be to edit your .profile or .chsrc to include
this so it is automatically done for you when you login. (Of course,
you need to either know ed or be able to set it at the unix prompt
before you'll be able to edit the file...)
If you do not know your terminal type, try vt100. Most modern
terminals and terminal emulators can emulate vt100. If this does not
work, find someone to help you.
There is a FAQ posted frequently which gives a list of all the files
that are online at the vi archive. It also gives a list of addresses
which mirror the vi archive. The main address is alf.uib.no, but it is
archived at many, many sites. The vi-archive faq lists all of them.
Please check that faq before ftping to it, as there is almost defiantly
a closer and therefore faster site to you that the one in Norway.
A mirror site is available at: cs.uwp.edu /pub/vi, and another at
monu6.cc.monash.edu.au /pub/Vi.
The site has many, many files on vi, including a few clones. It also
has the UCB distribution of vi, and lots of useful macros. Check it
out.
This section is for silly vi tricks, and silly macros. Actually, any
interesting vi tricks and macros are acceptable, as long as they are
not too lengthy. I will add any that are suggested to me that I think
are reasonable.
xp This will delete the character under the cursor, and put it
afterwards. In other words, it swaps the location of two characters.
ddp Similar to xp, but swapping lines.
uu Undo and redo last change. (This will take you to the last
modification to the file without changing anything.)
None at the moment, suggest some.
... means that something needs to be specified before or after the
command, as appropriate. This is normally a cursor movement
keys (h,j,k,l,w,b, etc.) or a line number.
# (where # is a number) following command n times...
: go to ex-mode
) next sentence
( previous sentence
} next paragraph
{ previous paragraph
]] next section
[[ previous section
0 beginning of line
$ end of line
^ first non-whitespace character
+ first character of next line
- first character of previous line
(spacebar) next character
(return) next line
/ search forward
? search backward
% find match of current parenthesis, brace, or bracket
, reverse direction of last f, F, t, or T
; repeat last f, F, t, or T
. repeat last command
` goto mark
' goto beginning of line with mark
`` return to previous mark or location before a search
'' go to start of line of previous mark or location before search
~ switch case of current character
" store in register
!! repeat last shell command
! send next to command, replace output (eg !}fmt passes the current
paragraph to the command fmt, and replaces the output with
whatever fmt returns.)
>> shift paragraph one shiftwidth to the right
<< shift paragraph one shiftwidth to the left
>% shift until matching (, [, or { to the right
<% shift until matching (, [, or { to the left
a append after the current location
A append at the end of the line
^a unused
b beginning of previous word
B beginning of previous word, ignore punctuation
^b scroll back one screen
c change until...
C change to end of line
^c ends insert mode, unused in command mode
d delete until...
D delete to end of line
^d scroll down half a window, moves to previous shiftwidth in insert
mode
e end of word
E end of word, ignore punctuation
^e scroll screen down one line
f find...
F find backward...
^f scroll forward one screen
g unused
G ...Goto [defaults to end of file]
^g show status line
h left
H first line on screen
^h backspace in insert mode, left in command mode
i insert before current location
I insert before first non-whitespace character on line
^i tab in insert, unused in command
j down
J join next line with current line
^j down in command, create newline in insert
k up
K unused
^k unused
l right
L last line on screen
^l redraw screen
m mark position into register
M middle of screen
^m carriage return
n repeat last search
N repeat last search, reverse direction
^n down in command
o open line below current
O open line above current
^o unused
p put below current line
P put above current line
^p up in command
q unused
Q quit and run ex
^q unused
r replace current character
R replace characters until insert mode is left
^r redraw screen in command mode
s substitute
S substitute entire line
^s unused
t to...
T backward to...
^t moves to next shiftwidth.
u undo last change
U undo changes to current line
^u scroll up half a window
v unused
V unused
^v unused
w beginning of next word
W beginning of next word, ignore punctuation
^w unused in command, in insert move back to beginning of previous
word
x delete current character
X delete previous character
^x unused
y yank...
Y yank current line
^y scroll screen up one line
z reposition screen around line (Return to top of screen, . to
middle, - to bottom)
ZZ write and quit
^z unused
(Note: this is not a canonical list, just some of the more important
ones.)
:r <file> read <file> into current text
:r !<command> read output from command <command> into current text
:nr <file> read in at line number
:!<file> run command, return
:sh goto shell
:so <file> read and execute commands from <file>
:x write and quit
:wq write and quit
:l1,l2w <file> write between lines l1 and l2 to <file>. If <file>
is not specified, assume current. If l1,l2 not
specified, assume entire file (making it :w)
:w >> <file> append to <file>. May use line numbers
:w! overwrite current file
:q quit
:q! quit, forget changes
:e <file> edit <file> without leaving vi
:e! forget changes since last write
:n edit next file
:e +n <file> edit <file> at line n, if no end, assume end of file
:n <files> specify <files> as new list of files to edit
:e# edit alternate file (if :e <file> is used, alternate is
the original file)
:args show files to be edited
:rew rewind life of files to top
:map m n create a macro (make m do n)
:map! m n create an insert mode macro (make m do n)
:unmap m destroy macro m
:unmap! m destroy insert mode macro m
:ab <1> <2> abbreviate - replace <1> with <2> whenever typed as
a word
:unab <1> unabbreviate <1>
:set <option> set <option>...
The abbreviations in parenthesis may be used. Syntax:
:set <option> <param> (If <param> is expected)
Multiple options may be specified on one line.
:set <option>? displays the value of the <option>
:set all displays the value of all the options.
For options without a value, set no<option> turns it off.
Option: Default: What it does:
autoindent (ai) noai Makes new lines automatically
indent to the position as the
line above or below
autoprint (ap) ap Display changes after each
command
autowrite (aw) noaw Automatically save file
before :n, :!
beautify (bf) nobf Ignore all control characters
during input (except tab,
newline, formfeed)
directory= (dir=) /tmp Name of the directory to store
buffer
edcompatible noedcompatible Use ed-like features on
substitute
errorbells (eb) errorbells Sound bell on error
exrc (ex) noexrc Allow .exrc files outside home
dir
hardtabs= (ht=) 8 Set boundary for hardware tabs
ignore case (ic) noic Ignore case in regex expressions
lisp nolisp Turn on lisp mode
list nolist Display all tabs, end of lines
magic magic Enable more regex expressions
mesg mesg Allows mesgs to be sent to
terminal
number (nu) nonumber Displays line numbers in file
open open Allows open and visual
optimize (opt) optimize Optimizes throughput of text by
not sending carriage returns
when printing text
paragraphs= (para=) IPLPPPQPPLIbp Sets the delimiters for { & }
prompt prompt Command mode input gives : prompt
readonly (ro) noro Cannot write unless ! is given
redraw noredraw Redraw screen when edits are made
remap remap Allows macros that point to other
macros
report= 5 Report changes if they effect > x
lines
scroll 1/2 window Amount of screen to scroll when
scroll down is received in
command mode. Also, number of
lines printer by z. (z prints
2*scroll)
sections= SHNHH HU Defines end of section for [[
and ]]
shell= (sh=) /bin/sh Default shell. Uses SHELL
environment, if set
shiftwidth= (sw=) 8 Characters to shift when using
shift commands
showmatch (sm) nosm Show matching {, }, (, ), [, or ]
showmode noshowmode Shows which mode you are in.
slowopen (slow) Do not update display
immediately after insert
tabstop= (ts=) 8 Sets tabstop length
taglength= (tl=) 0 Number of characters significant
for tags (0 means all
characters)
tags= tag, /usr/lib/tags Define pathname of files
containing tags.
term= Set the terminal type
terse noterse Display shorter error messages
timeout (to) timeout Keyboard maps timeout after one
second
ttytype= Set the terminal type
warn warn Display "No write since last
change" messages
window= (w=) Number of lines in window in visual
mode
wrapmargin= (wm=) 0 Set the right margin. Greater
than 0 will word wrap n spaces
from the edge of the screen
wrapscan (ws) ws Searches wrap around end of file
writeany (wa) nowa Allow saving to any file
Any commands that can be used in command input mode ( : commands),
may be used in a .exrc, which will load automatically whenever you
start vi. In addition, the source command (so), abbreviations (ab),
and macros may be used. There may not be any blank lines in your
.exrc. A " in the first column may be used to tell vi that what
follows is a comment.
This .exrc file is a real one. Mine. Because of that, it doesn't
set as many options as one might wish it did to get a good idea of what
may be used. However, it should get the basic idea down, and it is
quite straightforward.
set wm=3
set sm
" abbreviations for my email address.
ab zidllem E. Larry Lidz - ellidz@midway
ab zidlleu E. Larry Lidz - ellidz@midway.uchicago.edu
map V :w^M:!ispell -x %^M:e!^M^M
First, note that you do not need to specify the :, it is assumed.
The first line, set wm=3 sets the warpmargin to be three characters
from the right of the screen. This gives me a nice wordwrap.
The second line sets showmatch so that whenever I type a }, ) or ],
it shows the matching brace, parenthesis, or bracket. This is useful
for the programming I do.
The third line sets an abbreviation so that whenever I type zidllem
as a word by itself it expands to my name and email address. The
fourth is similar except that it gives the whole address, not just the
local one.
The fifth line sets V to automatically run ispell on the current
document passing it the -x parameter so that it doesn't save any
backups. (I don't like filling my directories with useless backups.)
I'd like to say that vi is bug free, but unfortunatly, it's not.
These bugs are bugs in the original vi, not necessarily in any of the
different clones.
Macros for _ do not always work properly.
This glossary will be updated as people suggest terms that they do
not understand. Please let me know if you have any suggestions.
command mode
Command mode is the mode within vi where the user gives commands to
vi. (Including cursor movement commands, editing commands, etc.)
ed
A non-visual editor under unix.
<Esc>
The escape key. A key on a keyboard normally marked by escape.
Sometimes ^[ will work in its place. If there is no escape key,
sometimes the Meta key will work.
ex
An editor under unix, all commands preceded with : are passed to
it.
insert mode
Insert mode is the mode within vi where text is inserted into the
document.
macro
A macro is a shortcut key combination. For example, a macro allows
one to hit one letter and have it execute a few different commands.
open mode
Open mode is the mode that vi will start in if it cannot determine
your terminal type, or if it believes you have a hardware or glass-tube
terminal.
regular expressions (RegEx)
Regular expressions, commonly known as "RegEx" are a set of key
combinations that are meant to allow people to have a large variety of
control over what they are searching for. RegEx is used a lot under
Unix, and is common between many programs.
sed
Stream-line editor. An editor that has no interface. All commands
are given from the command line.
vi
The editor to which this FAQ is dedicated.
The ULTIMATE GUIDE to the VI and EX Text Editors
Hewlett Packard Company (authors)
The Benjamin/Cummings Publishing Company, Inc.
ISBN 0-8053-4460-8
Please make suggestions as to what books are most useful for learning
vi. I will add books to this section as people suggest them to me.
(C)opyright, E. Larry Lidz, 1994, 1995. All Rights Reserved.
radek@sci.muni.cz