1.1. Before you Install

Before you install Vim, please refer to the OS specific release notes and information about compiling and usage of Vim at -

• Go to this location and look for files os_*.txt "http://cvs.vim.org/cgi-bin/cvsweb/vim/runtime/doc"

• The home page of vim is at "http://www.vim.org"

• Mirror site in US is at "http://www.us.vim.org"

• Ftp site "ftp://ftp.vim.org/pub/vim"

• Or use one of the mirrors "ftp://ftp.vim.org/pub/vim/MIRRORS"

1.2. Install Vim on Redhat Linux

To use Vim install the following RPM packages on Redhat Linux -

rpm -i vim*.rpm OR do this - rpm -i vim-enhanced*.rpm rpm -i vim-X11*.rpm rpm -i vim-common*.rpm rpm -i vim-minimal*.rpm

You can see the list of files the vim rpm installs by -

rpm -qa | grep ^vim | xargs rpm -ql | less or rpm -qa | grep ^vim | awk '{print "rpm -ql " $1 }' | /bin/sh | less

and browse output using j,k, CTRL+f, CTRL+D, CTRL+B, CTRL+U or using arrow keys, page up/down keys. See 'man less'.

Note that the RPM packages for Redhat Linux use a Motif interface. If you have installed the GTK libraries on your system, consider compiling Vim from the source code for a clean GUI interface. For information on compiling Vim from the source code, see "Install Vim on Unixes", below.

1.3. Install Vim on Debian GNU/Linux

To install Vim on Debian Linux (GNU Linux), login as root and when connected to internet type -

apt-get install vim vim-rt

It will download the latest version of vim, install it, configure it. The first package listed is vim, the standard editor, compiled with X11 support, vim-rt is the vim runtime, it holds all the syntax and help files.

On Debian 3.0 (woody) and above, use 'apt-get install vim' instead. The vim-rt package is part of the main vim package.

1.4. Install Vim on Unixes

For other flavors of unixes like Solaris, HPUX, AIX, Sinix, SCO download the source code file ( see Section 1.1 )

zcat vim.tar.gz | tar -xvf - cd vim-5.5/src ./configure --prefix=$HOME/local make make install

You can exclude prefix option if you want to install in default location in /usr/local. If the graphics version 'gvim' gives trouble then try with

./configure --prefix=$HOME/local --enable-gui=motif

1.5. Install Vim on Microsoft Windows 95/NT

See Section 2 .

1.6. Install Vim on VMS

1.7. Install Vim on OS/2

Read the release notes for Vim on OS/2, see Section 1.1 .

At present there is no native PM version of the GUI version of vim: The OS/2 version is a console application. However, there is now a Win32s-compatible GUI version, which should be usable by owners of Warp 4 (which supports Win32s) in a Win-OS/2 session. The notes in this file refer to the native console version.

To run Vim, you need the emx runtime environment (at least rev. 0.9b). This is generally available as (ask Archie about it):

emxrt.zip emx runtime package

1.8. Install Vim on Apple Macintosh

Read the release notes for Vim on OS/2, see Section 1.1 .

The author of Vim on Mac (old version vim 3.0) is

Eric Fischer 5759 N. Guilford Ave Indianapolis IN 46220 USA

Email to enf@pobox.com

Mac Bug Report When reporting any Mac specific bug or feature change, makes sure to include the following address in the "To:" or "Copy To:" field.

dany.stamant@sympatico.ca

Vim compiles out of the box with the supplied CodeWarrior project when using CodeWarrior 9. If you are using a more recent version (e. g. CW Pro) you have to convert the project first. When compiling Vim for 68k Macs you have to open the "size" resource in ResEdit and enable the "High level events aware" button to get drag and drop working. You have to increase the memory partition to at least 1024 kBytes to prevent Vim from crashing due to low memory.

vim:ts=8:sw=8:tw=78:

2.1. Install bash shell

In order make MS Windows 95/98/NT/2000/XP even more user-friendly, install the bash shell (Bourne Again Shell). Install "http://sources.redhat.com/cygwin/setup.exe" (Cygwin-setup program) and select bash and other common utilities. The CygWin main site is at "http://sources.redhat.com/cygwin" . With CygWin the Windows 2000 computer will look like Linux/Unix box!! And combined with gvim editor, the Windows 2000 gives programmers more power. The cygwin home is at "http://cygwin.com" .

You may also want to install MKS in case you are planning to use Java and Java compilers. Get MKS from "http://www.mks.com" .

2.2. Edit bash_profile

After installing the Cygwin, insert some useful aliases in ~/.bash_profile file. Open a cygwin window and at bash prompt -

bash$ cd $HOME bash$ gvim .bash_profile set -o vi alias ls='ls --color ' alias cp='cp -i ' alias mv='mv -i ' alias rm='rm -i ' alias vi='gvim ' alias vip='gvim ~/.bash_profile & ' alias sop='. ~/.bash_profile ' alias mys='mysql -uroot -p ' PATH=$PATH:"/cygdrive/c/Program Files/mysql/bin"

With color ls, when you do ls you will see all the directory names and files in different colors (it looks great!!). With set -o vi, you can use the command line history editing just as in linux.

2.3. Setup Window colors

The default background color of MS DOS prompt window is black and white text. You must change the color, fontsize and window size to make it more pleasing. On MS Windows 2000, click on button Start->Run and type "cmd" and hit return. On MS Windows 95/98/NT click on Start->Programs->MSDOS Prompt which will bring up MSDOS window. Right click on the top left corner of the MSDOS prompt window and select properties. Select color background and enter R=255, G=255, B=190 (red, green, blue) for lightyellow background and text foreground color to black (R=0, G=0, B=0). This sets background to light yellow and text foreground to black and this combination is most pleasing to human eyes. If you have problems with colors in cygwin bash window when doing 'man ls', set the text color to "marune".

For Windows95 see Color for MS-DOS prompt window .

4.1. Sample gvimrc file

You can change the settings like color, bold/normal fonts in your $HOME/.gvimrc file. It is very strongly recommended that you set the background color to lightyellow or white with black foreground. Ergonomics says that best background color is lightyellow or white with black foreground. Hence change the variable 'guibg' in your $HOME/.gvimrc file as follows:

highlight Normal guibg=lightyellow

The sample gvimrc from /usr/doc/vim-common-5.3/gvimrc_example is as follows:

" Vim " An example for a gvimrc file. " The commands in this are executed when the GUI is started. " " To use it, copy it to " for Unix and OS/2: ~/.gvimrc " for Amiga: s:.gvimrc " for MS-DOS and Win32: $VIM\_gvimrc " Make external commands work through a pipe instead of a pseudo-tty "set noguipty " set the X11 font to use. See 'man xlsfonts' on unix/linux " set guifont=-misc-fixed-medium-r-normal--14-130-75-75-c-70-iso8859-1 set guifont=8x13bold "set guifont=9x15bold "set guifont=7x14bold "set guifont=7x13bold " " Highly recommended to set tab keys to 4 spaces set tabstop=4 set shiftwidth=4 " " The opposite is 'set wrapscan' while searching for strings.... set nowrapscan " " The opposite is set noignorecase set ignorecase " " You may want to turn off the beep sounds (if you want quite) with visual bell " set vb " Source in your custom filetypes as given below - " so $HOME/vim/myfiletypes.vim " Make command line two lines high set ch=2 " Make shift-insert work like in Xterm map <S-Insert> <MiddleMouse> map! <S-Insert> <MiddleMouse> " Only do this for Vim version 5.0 and later. if version >= 500 " I like highlighting strings inside C comments let c_comment_strings=1 " Switch on syntax highlighting. syntax on " Switch on search pattern highlighting. set hlsearch " For Win32 version, have "K" lookup the keyword in a help file "if has("win32") " let winhelpfile='windows.hlp' " map K :execute "!start winhlp32 -k <cword> " . winhelpfile <CR> "endif " Hide the mouse pointer while typing set mousehide " Set nice colors " background for normal text is light grey " Text below the last line is darker grey " Cursor is green " Constants are not underlined but have a slightly lighter background highlight Normal guibg=grey90 highlight Cursor guibg=Green guifg=NONE highlight NonText guibg=grey80 highlight Constant gui=NONE guibg=grey95 highlight Special gui=NONE guibg=grey95 endif

See also sample vimrc used for console mode vim command from /usr/doc/vim-common-5.3/vimrc_example.

4.2. Xdefaults parameters

You can set some of the Vim properties in Xdefaults file.

WARNING: Do not set Vim*geometry as it will break the gvim menu, use Vim.geometry instead .

Edit the $HOME/.Xdefaults file and add the following lines:

! GVim great Colors. Vim*useSchemes: all Vim*sgiMode: true Vim*useEnhancedFSB: true Vim.foreground: Black !Vim.background: lightyellow2 Vim*background: white ! Do NOT use Vim*geometry , this will break the menus instead ! use Vim.geometry. Asterisk between Vim and geometry is not allowed. ! Vim.geometry: widthxheight Vim.geometry: 88x40 !Vim*font: -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso8859-15-*5 Vim*menuBackground: yellow Vim*menuForeground: black

In order for this change to take effect, type -

xrdb -merge $HOME/.Xdefaults man xrdb

You can also edit the ~/.gvimrc file to change the background colors

gvim $HOME/.gvimrc The best background color is lightyellow or white, with black foreground. highlight Normal guibg=lightyellow

5.1. Auto source-in method

This section below is obtained from gvim session by typing 'help syntax' -

bash$ gvim some_test :help syntax

Click on the menu Window=>Close_Others to close other Window. And then do CTRL+] on 'Syntax Loading Procedure' menu which will take you there. (Use CTRL+T to rewind and go back).

If a file type you want to use is not detected, then there are two ways to add it.

Method 1: You can modify the $VIMRUNTIME/filetype.vim file, but this is not recommended as it will be overwritten when you install a new version of Vim.

Method 2: Create a file in $HOME/vim/myfiletypes.vim and put these lines in it -

" " ************************************************************* " Filename : $HOME/vim/myfiletypes.vim " See the document by typing :help autocmd within vim session " see also the doc at /usr/share/vim/doc/autocmd.txt " This file will setup the autocommands for new filetypes " using the existing syntax-filetypes. " For example when you open foo.prc it will use syntax of plsql " Basically does :set filetype=prc inside vim " Add a line in $HOME/.gvimrc as below: " so $HOME/vim/myfiletypes.vim " " ************************************************************* augroup filetype au! au! BufRead,BufNewFile *.phc set filetype=php au! BufRead,BufNewFile *.mine set filetype=mine au! BufRead,BufNewFile *.xyz set filetype=drawing au! BufRead,BufNewFile *.prc set filetype=plsql augroup END

Then add a line in your $HOME/.vimrc and $HOME/.gvimrc file to source in the file "myfiletypes.vim". ( CAUTION: You MUST put this in both vimrc and gvimrc files in order for this to work) Example:

so $HOME/vim/myfiletypes.vim

NOTE: Make sure that you set "so myfiletypes.vim" before switching on file type detection. This is must be before any ":filetype on" or ":syntax on" command.

See the documentation on autocommand at -

• :help autocmd (within a vim editing session)

• See also the doc at /usr/share/vim/doc/autocmd.txt

Your file will then be sourced in after the default FileType autocommands have been installed. This allows you to overrule any of the defaults, by using ":au!" to remove any existing FileType autocommands for the same pattern. Only the autocommand to source the scripts.vim file is given later. This makes sure that your autocommands in "myfiletypes.vim" are used before checking the contents of the file.

5.2. Manual method

Instead of using "Syntax" menu you can also manually source in the syntax file. Edit the file with gvim and at : (colon) command give 'so' command. For example -

gvim foo.pc :so $VIM/syntax/esqlc.vim

The syntax source files are at /usr/share/vim/syntax/*.vim. Vim supports more than 120 different syntax files for different languages like C++, PERL, VHDL, JavaScript,...and so on!!

Each syntax file supports one or more default file name extensions, for example, JavaScript syntax file supports the *.js extension. If you happen to use an extension that conflicts with another default syntax file (such as adding JavaScript to a *.html file) than you can source in the additional syntax file with the command :so $VIM/syntax/javascript.vim. To avoid all of this typing, you can create a soft link like -

ln -s $VIM/syntax/javascript.vim js gvim foo.html (... this file contains javascript functions and HTML) :so js

8.1. Directory Tree 'tags'

To recursively process the tags file for the entire directory :

$ cd $HOME $ ctags -R

This will recurse the directory underneath and create a tag file all the files under the directory and beneath. But to use this tag file you must set the following in the vim session or modify .gvimrc file

$ vi ~/.gvimrc " Set the tag file search order set tags=./tags,tags,~/tags,/home/john/ccplus/tags

Or in the Vim session you set the tags with colon command:

$ vi somefile.cpp :set tags=./tags,tags,~/tags,/home/john/ccplus/tags

8.2. Ctags for ESQL

Since ctags does not directly support the Embedded SQL/C (ESQL) language, the following shell script can be used to create tags for esql. ESQL/C is database SQL commands embedded inside the "C" programs. Oracle's ESQL/C is called Pro*C and Sybase, Informix have ESQL/C and PostgreSQL has product "ecpg".

Save this file as "sqltags.sh" and do chmod a+rx tags_gen.sh.

#!/bin/sh # Program to create ctags for ESQL, C++ and C files ESQL_EXTN=pc tag_file1=tags_file.1 tag_file2=tags_file.2 which_tag=ctags rm -f $tag_file1 $tag_file2 tags aa=`ls *.$ESQL_EXTN` #echo $aa for ii in $aa do #echo $ii jj=`echo $ii | cut -d'.' -f1` #echo $jj if [ ! -f $jj.cpp ]; then echo " " echo " " echo "***********************************************" echo "ESQL *.cpp files does not exist.. " echo "You must generate the *.cpp from *.pc file" echo "using the Oracle Pro*C pre-compiler or Sybase" echo "or Informix esql/c pre-compiler." echo "And then re-run this command" echo "***********************************************" echo " " exit fi rm -f tags $which_tag $jj.cpp kk=s/$jj\.cpp/$jj\.pc/g #echo $kk > sed.tmp #sed -f sed.tmp tags >> $tag_file1 #sed -e's/sample\.cpp/sample\.pc/g' tags >> $tag_file1 sed -e $kk tags >> $tag_file1 done # Now handle all the C++/C files - exclude the ESQL *.cpp files rm -f tags $tag_file2 bb=`ls *.cpp *.c` aa=`ls *.$ESQL_EXTN` for mm in $bb do ee=`echo $mm | cut -d'.' -f1` file_type="NOT_ESQL" # Exclude the ESQL *.cpp and *.c files for nn in $aa do dd=`echo $nn | cut -d'.' -f1` if [ "$dd" = "$ee" ]; then file_type="ESQL" break fi done if [ "$file_type" = "ESQL" ]; then continue fi rm -f tags $which_tag $mm cat tags >> $tag_file2 done mv -f $tag_file2 tags cat $tag_file1 >> tags rm -f $tag_file1 # Must sort tags file for it work properly .... sort tags > $tag_file1 mv $tag_file1 tags

8.3. Ctags for JavaScript programs, Korn, Bourne shells

The shell script given below can be used to generate tags for a very large variety of programs written in JavaScript, PHP/FI scripts, Korn shell, C shell, Bourne shell and many others. This is a very generic module.

Save this file as tags_gen.sh and do chmod a+rx tags_gen.sh.

#!/bin/sh tmp_tag=tags_file tmp_tag2=tags_file2 echo " " echo " " echo " " echo " " echo " " echo "Generate tags for ...." while : do echo " Enter file extension for which you want to generate tags." echo -n " File-extension should be like sh, js, ksh, etc... : " read ans if [ "$ans" == "" ]; then echo " " echo "Wrong entry. Try again!" else break fi done \rm -f $tmp_tag aa=`ls *.$ans` for ii in $aa do jj=`echo $ii | cut -d'.' -f1` #echo $jj cp $ii $jj.c ctags $jj.c echo "s/$jj.c/$ii/g" > $tmp_tag2 sed -f $tmp_tag2 tags >> $tmp_tag \rm -f tags $jj.c done sort $tmp_tag > tags \rm -f $tmp_tag $tmp_tag2

8.4. Debugger gdb

You would be using gdb extensively along with Vi. Debugging is the most important aspect of programming as the major cost of software projects goes into debugging and testing.

To debug C++/C programs use 'gdb' tool. See 'man gdb' . You must compile your programs with -g3 option like

gcc -g3 foo.c foo_another.c sample.c

To set up easy aliases do -

Setup an alias in your ~/.bash_profile alias gdb='gdb -directory=/home/src -directory=/usr/myname/src ' Give - gdb foo.cpp gdb> dir /hom2/another_src This will add to file search path gdb> break 'some_class::func<TAB><TAB> This will complete the function name saving you typing time... and will output like - gdb> break 'some_class::function_foo_some_where(int aa, float bb)'

Pressing TAB key twice is the command line completion, which will save you lots of typing time. This is one of the most important technique of using gdb.

To get online help do -

gdb> help Gives online help gdb> help breakpoints Gives more details about breakpoints.

To set breakpoints and do debugging

unixprompt> gdb exe_filename gdb> b main This will put breakpoint in main() function gdb> b 123 This will put breakpoint in line 123 of the current file gdb> help breakpoints Gives more details about breakpoints.

To analyze the core dumps do

unixprompt> gdb exe_filename core gdb> bt Gives backtrace of functions and line numbers where the program failed gdb> help backtrace Gives more details about backtrace.

You can also use GUI version of gdb called xxgdb.

See also gdb interface to Vim at "http://www.lxlinux.com/gdbvim.tgz" .

Memory leak tools -

• Freeware Electric Fence on linux cd,

• Commercial tools Purify "http://www.rational.com"

• Insure++ "http://www.insure.com"

10.1. Vi Resources and Tips

The following Vi resources are available on internet:

• O'Reilly "Learning the Vi Editor" at "http://www.eyetap.org/ece385/oreilly/unix/vi/index.htm"

• Vi Google directory at Google-Vi

• Resources, Tips, News about Vim "http://vim.sourceforge.net"

• Vi Cheatsheet "http://www.geekcheat.com/Merchant2/merchant.mv"

• Vim and vi article "http://www.troubleshooters.com/lpm/200212/200212.htm"

• Vim Outliner - An outline processor is a software program enabling the user to quickly construct outlines, and better yet, to correct and rearrange the outline. "http://www.troubleshooters.com/vimoutliner"

11.1. Vim Hands-on Tutorial

On Linux system see the tutorial at /usr/doc/vim-common-5.*/tutor, on other unix systems go to directory where vim is installed and look for doc directory.

bash$ cd /usr/doc/vim-common*/tutor bash$ less README.txt bash$ cp tutor $HOME bash$ cd $HOME bash$ less tutor

11.2. Vi Tutorials on Internet

• Purdue University "http://ecn.www.ecn.purdue.edu/ECN/Documents/VI/"

• Advanced Vi tutorial "http://www.yggdrasil.com/bible/bible-src/user-alpha-4/guide/node171.html"

• Tutorials "http://www.cfm.brown.edu/Unixhelp/vi_.html"

• Univ of Hawaii tutorial "http://www.eng.hawaii.edu/Tutor/vi.html"

• InfoBound "http://www.infobound.com/vi.html"

• Vi Lovers home page "http://www.thomer.com/thomer/vi/vi.html"

• vi Help file "http://www.vmunix.com/~gabor/vi.html"

• These are dead links::

  Quick Vi tutorial "http://linuxwww.db.erau.edu/LUG/node165.html"

• Tutorials "http://www.linuxbox.com/~taylor/4ltrwrd/section3_4.html"

• Unix world online vi tutorial "http://www.networkcomputing.com/unixworld/unixhome.html"

• Cornell Univ "http://www.tc.cornell.edu/Edu/Tutor/Basics/vi/"

• Beginner's Guide to vi "http://www.cs.umr.edu/unixinfo/general/packages/viguide.html"

• vim FAQ "http://www.math.fu-berlin.de/~guckes/vim/faq/"

12.1. Cursor Movement Commands

The vi cursor movement commands allow you to position the cursor in the file and/or on the screen efficiently, with a minimum number of keystrokes. There are oodles of cursor movement commands - don't try memorizing them all at once! Later, we'll see that much of the power of vi comes from mixing cursor movement commands with other commands to delete, change, yank (copy), and filter text.

Please edit a large text file (say, wknight ) so you can experiment with each command as it is described. Keep in mind these commands will only work in Command Mode, not Insert Mode; if you start getting your "commands" in your text, press the ESC key to return to Command Mode.

• cursor keys : As we've seen, cursor keys move by single character amounts left, down, up, and right. Movement above the top of the file, below the bottom, to the right of the end of a line, or left of the beginning is not allowed (no line wrapping).

• hjkl : When vi was written (around 1978), many terminals on UNIX systems did not have cursor keys! h, j, k, and l were chosen as commands to move left, down, up, and right, respectively. Try them! Most vi diehards prefer these to the cursor keys because

  • (a) they are in the same place on all keyborads, and

  • (b) they fit nicely under the fingers, unlike most cursor keys, which are arranged in a box or "T" or some other nonlinear shape.

  Why h, j, k, and l? Well, in the ASCII character set, CTRL-H is backspace (moves left), CTRL-J is linefeed (moves down), and, of course, k and l are next to h and j, so you see, they're mnemonic.

• 0 : ("zero", not "oh") Move to the beginning of current line. (To try this and the next few commands, use the cursor keys or h j k l to move to an indented text line that contains few "e" characters. If you can't find an indented line in your file, create one by inserting a few space characters at the beginning of a line.)

• ^ : Move to first non-white character of current line. (For indented line, 0 and ^ are different.)

• $ : Move to last character of current line.

• tC : Move to (but not on) next character c in current line. (Press 0, then press te. This will move to the first e in the curent line.)

• fC : Find (move on top of) next character c in current line. (Press fe, and the cursor will find - that is, move on top - the next e in the current line.)

• TC : Move to (but not on) the previous character c in current line (Press $, then Te.)

• FC : Find (move on top of) the previous character c in current line. (Press Fe.)

• n| : Move to column n in current line. (Try 20 |. The digits 2 and 0 will not be displayed as you type them, but when you press | the cursor will move to column 20.) Try some experiments with t f T F | . When you do something illegal, vi will beep your terminal.

• w : Forward to beginning of next "small" word ( a "small" word consists of unbroken alphanumeric characters or punctuation characters, but not mixed alphanumeric and punctuation). Try tapping w a dozen times or so - note what happens at punctuation.

• W : Forward to beginning of next "big" word (alphanumeric and punctuation mixed). Try W a dozen times or so.

• b : Backward to beginning of "small" word.

• B : Backward to beginning of "big" word.

• e : Forward to end of "small" word.

• E : Forward to end of "big" word.

• + Return : Move to first non-white space character on next line. (+ and the Return key have the same effect.)

• - : Move to first non-white space character on previous line.

• ) : Move to the end of sentence. (A sentence ends either at a blank line or at a period or examination mark followed by two space characters or at the end of a line. A period or exclamation mark followed by one space character does not end a sentence; this is correct behaviour, according to traditional rules of how sentences should appear in typed documents, but often appears wrong to those who have never suffered through a formal typing class.)

• ( : Move to beginning of sentence.

• } : Move to end of paragraph. (Paragraphs are seperated with blank lines, by vi 's definition.)

• { : Move to beginning of paragraph.

• H : Move to home position (top line) on the screen

• M : Move to middle line on the screen.

• L : Move to last line on the screen.

• nG : Move to line n. If n is not given, move to the last line in the file. (Try 15G to move to line 15, for example. The CTRL-G command displays the name of the file, some status information, and the current line number. To move to the top of the file: 1G)

• CTRL-d : Scroll down half-screen (see note).

• CTRL-u : Scroll up half-screen (see note).

• CTRL-f : Move forward one-screen (see note).

• CTRL-b : Move backward one-screen (see note).

• Note : These four scrolling/paging commands cannot be used with the delete, change, yank, or filter commands.

• /reg_exp : Move to next occurrence of the regular expression reg_exp When you press /, the cursor drops to the lower left corner of the screen and waits for you to type in the regular expression. Press the Return key to finish; vi then searches forward for the next occurrence of the regular expression. For example, press /the followed by Return. This moves forward to the next occurrence of the, perhaps imbedded in the middle of some longer word (other, weather, etc.). If you just press / and then Return, vi searches for the next occurrence of whatever the last regular expression was that you searched for.

• n : Has the same effect as pressing / and then Return; i.e., searches for the next occurrence of whatever the last regular expression was that you searched for.

• ?reg_exp : Searches backward, rather than forward. If no reg_exp is given, it searches for the last regular expression that was entered. Both / and ? wrap around, so searching "below" the bottom or "above" the top of the file is legal.

• N : Same as pressing ? and then Return.

12.2. Repeat Counts

Many of the movement commands discussed above can be preceded with a repeat count; the movement is simply repeated the given number of times:

• 3w : Move forward three words

• 5k : Move up four characters

• 3fa : Find the third succeeding a in current line

• 6+ : Move down six lines

• 4H : Move to Line 4 on the screen (home plus 3)

• 8L : Move to the eigth line from the bottom of the screen

• 3$ : Move to the end of the third line down

12.3. Deleting Text

We've seen that dd deletes the current line. This can be used with a repeat count: 3dd deletes three lines, the current line, and the two following lines.

The d command can be used as a "prefix" on most of the movement commands above to delete nearly arbitrary chunks of text. When used with d, the movement commands are called target specifiers. d can be given a repeat count. (As you try these experiments, remember to press u after each command to undo the deletion).

• dw : Delete "small" word forward

• d3w : Delete three "small" words forward

• 3dw : Three times, delete "small" word forward

• 3d3w : Three times, delete three "small" words forward (that is, delete nine "small" words forward)

• d+ : Delete current line and next line down

• d/the : Delete from current character up to but not including the next occurrence of the pattern the.

• d$ : Delete to end of line

• d0 : Delete to beginning of line

• d30G : Delete from the curent line to and including Line 30

• dG : Delete from current line to and including last line

• d1G : Delete from current line to and including Line 1

• 15x : Delete current and 14 following characters

12.4. Changing Text

The c command is similar to d, except it toggles vi into Insert Mode, allowing the original (unwanted) text to be changed to something else.

For example, put the cursor on the beginning of a word (press w to get to the beginning of the next word). Then, press cw to change that word. On the screen, the last character in the word being changed will be replaced with a $ symbol indicating the boundary of the change; type in a new word (you will overwrite the original word on the screen) and press the ESC key when done. Your input may be longer or shorter than the word being changed.

Put the cursor at the beginning of a line containing at least three words, and try c3w to change three words. Try c$ to change to the end of the current line. In all cases where the change affects only the current line, the boundary of the change is indicated with $.

When a change affects more than just the current line, vi deletes the original text from the screen and toggles into Insert Mode. For example, try c3+ to change the current and the next three lines; vi deletes the four original lines from the screen and toggles into Insert Mode in a new blank line. As usual, press the ESC key when you have finished entering your new text.

Some other change commands:

• cc : Change current line

• 5cc : Change five lines (current and next four)

• c/the : Change from current character up to but not including the next occurrence of the pattern the

• c$ : Change to end of line

• c30G : Change from the current line to and including Line 30

• cG : Change from curernt line to and including last line

• c1G : Change from curernt line to and including Line 1

12.5. Yanking (Copying) Text

The y command yanks a copy of text into a buffer; the yanked text can then be put (or pasted) elsewhere in the file using p or P.

The simplest form of yank is yy to yank the current line; after yy, try p to put a copy of the yanked line after the cursor. Following yy, you can make as many copies of the yanked line as you want by moving up and down in the file and pressing p.

To copy multiple lines, try, for example, 5yy (yank the current and next four lines). p puts a copy of the yanked lines after the cursor; the sequence 5yyp "works" but it probably doesn't do what you would like. The P command is like p, but puts a copy of the yanked text ahead of the cursor; try the sequence 5yyP.

Other yank commands:

• y3w : Yank three words

• y$ : Yank to end of current line

• y1G : Yank from current line to and including Line 1

12.6. Filtering text

The filter command ! , prompts for the name of a UNIX command (which should be a filter), then passes selected lines through the filter, replacing those selected line in the vi buffer with the output of the filter command. vi 's ability to pass nearly arbitrary chunks of text through any UNIX filter adds incredible flexibility to vi , at no "additional cost" in size or performance to vi itself.

Some examples will help illustrate. Create a line in your file containing just the word who and absolutely no other text. Put the cursor on this line, and press !! This command is analogous to dd, cc, or yy, but instead of deleting, changing, or yanking the current line, it filters the current line. When you press the second !, the cursor drops down to the lower left corner of the screen and a single ! is displayed, prompting you to enter the name of a filter. As the filter name, type sh and press the Return key. sh (the Bourne shell) is a filter! It reads standard input, does some processing of its input (that is, executes commands), and sends its output (the output of those commands) to standard output. Filtering the line containing who through sh causes the line containing who to be replaced with a list of the current users on the system - right in your file!

Try repeating this process with date . That is, create a line containing nothing but the word date , then put the cursor on the line, and press !!sh and the Return key. The line containing date is replaced with the output of the date command.

Put your cursor on the first line of the output of who. Count the number of lines. Suppose, for example, the number is six. Then select those six lines to be filtered through sort; press 6!!sort and the Return key. The six lines will be passed through sort, and sort's output replaces the original six lines.

The filter command can only be used on complete lines, not on characters or words.

Some other filter commands (here, < CR > means press Return):

• !/the < CR > sort < CR > : Sort from the current line up to and including the next line containing the

• !1Ggrep the < CR > : Replace from the current line to and including Line 1 with just the lines that contain the

• !Gawk '{print $1}' < CR > : From the current line to the end of file, replace every line with just its first word.

12.7. Marking Lines and Characters

You can mark lines and characters to be used as targest for movement, deletion, change, yanking, and filtering using the command mc, where c is a lowercase letter.

For example, put the cursor in the middle of some word and press ma. This marks the character under the cursor as mark a.

Now, move the cursor off the marked character and to a different line ( use the cursor keys, CTRL-u, or whatever). To return to the marked line, press 'a (that is, single quote, then a). This moves to the first non-white space character on the line containing mark a.

Move off that line again. To return to the marked character, press `a (that is, backquote, then a). This moves on top of the character marked with a.

Marking is usually used with deleting, changing, yanking or filtering. For example, move the cursor to a line other than the one containing mark a, and then press d'a (d, single quote, a). This deletes from the current line to and including the line marked with a.

Put the cursor in the middle of a different word and press mb to set mark b. Now, move the cursor away from that word (but only a few lines, so you can see what we're about to do more easily), and then press d`b (d, backquote, b). This deletes from the current CHARACTER to and including the CHARACTER marked with b.

As another example, to sort the output of who, mark the first line (ma), then move the cursor to the last line and press !'asort and the Return key.

If you jump to a mark and decide you want to jump back to whatever you jumped from, you can press '' (jump back to line) or `` (jump back to character).

12.8. Naming Buffers

When you delete, change, or yank text, the original text is stored (until the next delete, change, or yank) in an unnamed buffer from which it can be put using p or P. Using the unnamed buffer, only the most recently deleted, changed or yanked text may be recovered.

If you wish to delete, change, or yank multiple sections of text and remember them all (up to a maximum of 26), you can give a buffer name ahead of the delete change or yank command. A buffer name has the form "c (double quote, lowercase c).

For example, press "ayy to yank the current line into buffer a, then move to a different line and press "byy to yank that line into buffer b. Now, move elsewhere in the file and press "ap and "bp to put copies of the text stored in buffers a and b.

Some other named buffer commands:

• "a6yy : Yank six lines (current and next five) into buffer a

• "bd1G : Delete from the curernt line to and including Line 1, storing the deleted lines in buffer b

• "cy'c : Yank from the current line to the line marked c into buffer c (marks and buffers are distinct, and may have the same name without confusing vi )

12.9. Substitutions

To substitute one chunk of text for another in lines throughout your file, use the :s command. Some substitute examples:

• :1,$s/the/THE/g From Line 1 to the last line (line $), substitute for the text THE; do this globally in each line where the occurrs

• :'a,.s/.*/ha ha/ From the line marked a to the current line (line .), substitute for everything on the line the text ha ha

12.10. Miscellaneous "Colon Commands"

All colon commands begin with a colon; when you press the colon, the cursor drops to the lower left corner of the screen, and a colon prompt is displayed waiting for you to finish your colon command.

Some important examples:

• :w Write the buffer contents to the file without quitting from vi

• :w abc Write the buffer contents to the file abc (creating abc if it doesn't exist, or overwriting current contents if it does exist) without quitting from vi

• :1,10w abc Write lines 1 through 10 to file abc

• :'a,$w abc Write from the line marked a to the last line into file abc

• :e abc Edit file abc, instead of the current file. vi prints an error message if changes have been made to the curernt file that have not been saved with :w

• :e! abc Edit file abc, throwing away any changes that may have been made to the current file

• :e # Edit the prior file edited (successive :e# commands toggle back and forth between two files)

• :f abc Change the file anme for the current vi buffer to abc

• :q Quit, unless unsaved chanegs have been made

• :q! Quit, throwing away any changes that may have been made

• :r abc Read the file abc into current vi buffer, after the line the cursor is on (try :r croc to read in a copy of the croc file)

• :!cmd Execute command cmd (who, sort, ls, etc.)

12.11. Setting Options

Various options affect the "feel" of vi . You can display all the various options that can be set using the colon command :set all. You can also use set to change options.

For example, if you want to see line numbers for the lines in the file you're editing, use the command :set number. To turn off line numbering, use the command :set nonumber. Most options can be abbreviated; :set nu turns on line numbering and :set nonu turns off line numbering.

If you :set nomagic, the special meanings of regular expression characters (period, asterisk, square bracket, etc.) are switched off. Use :set magic to restore the special meanings.

Some options take a value. For example, :set tabstop=4 causes tabs to be displayed as four space characters, rather than the usual eight.

If you find you always want certain options set certain ways, you can put the set commands you want ina file .exrc, or you can set up the environment variable EXINIT to specify the options you want.

For example, if your login shell is Bourne shell, this line could go in your .profile file:

EXINIT='set nomagic nu tabstop=4'; export EXINIT

If your login shell is a C shell, this line could go in your .login file:

setenv EXINIT 'set nomagic nu tabstop=4'

12.12. Key Mappings

If you find you're performing a series of simple commands over and over, you can map the command series to an unused command key using the :map command. If your mapping must include control characters such as Return key (CTRL-M in ASCII) or the ESC (CTRL-[ in ASCII) key, precede such characters with CTRL-v to suppress their usual special meaning.

For example, this command maps CTRL-A to move the cursor forward 55 lines, then back up to the most recent blank line, then change that blank line to a formfeed (CTRL-L) and three blank lines. That is, each CTRL-A will paginate the next page, without splitting paragraphs across pages.

Note: In this command, each control character is shown as ^C, where C is some uppercase letter. For example, CTRL-M is shown as ^M. Also, when you enter this command you will not see the CTRL-v characters as shown: each CTRL-v merely suppresses the usual special meaning of the following control character, so when you press the sequence ^V^M, all you will see on the screen is ^M. In this command, ^M is the Return key and ^[ is the ESC key.

:map ^A 55+?^$^V^Mcc^V^L^V^M^V^M^V^M^V^[

12.13. Editing Multiple Files

You can edit multiple files with vi by giving multiple file names as command line arguments:

vi croc fatherw wknight

Three colon commands are used to move through the multiple files:

• :n Move to the next file in the argument list (you must save changes with :w or vi will print an error message)

• :N Move to the previous file in the argument list (you must save changes with :w or vi will print an error message)

• :rew Rewind and start over with the first file in the argument list

For example, try the following experiment: First get out of vi , then execute vi with croc and wknight as arguments:

$ vi croc wknight

In croc, search for the

/the < CR >

Yank this line into buffer a:

"ayy

Now go to the next file (you've made no change to croc, so this will work):

:n < CR >

Search for the "next" line containing the, without retyping the search string:

n

Put a copy of buffer a after the current line in wknight:

"ap

Move down two lines, and yank the current line into buffer b:

jj"byy

Save the changes to wknight

:w < CR >

Now, rewind to croc

:rew < CR >

Search again, and put a copy of buffer b after the found line:

n"bp

Save the changes, and exit vi

ZZ

12.14. Final Remarks

This tutorial was intended to introduce some of the vi capabilities that you might overlook in your system's vi manual or that might not be mentioned in the manual (different systems have manuals of widely varying quality).

You will not be a vi expert after reading this tutorial, but you will have a good appreciation of vi 's capabilities. Only time and effort can make a vi expert. But the efficiency and universality of vi make this effort pay off in the long run.

You may have decided you hate vi . So be it! But be aware that vi remains the standard UNIX text editor - the one editor you can count on being available on every UNIX system you'll use - so even if you prefer to use something else day-to-day, you'd be well advised to know the bare minimum vi material covered in this tutorial.

13.1. Vi states

Vi has 3 modes:

1. command mode - Normal and initial state; others return here (use ESC to abort a partially typed command)

2. input mode - entered by specific commands a i A I o O c C s S R and ended by ESC or abnormally with interrupt

3. line mode - i.e. waiting for input after a : , / , ? or a ! command (end with CR , abort with CTRL-c ). CTRL is the control key: CTRL-c means "control c"

13.2. Shell Commands

1. TERM= code Puts a code name for your terminal into the variable TERM

2. export TERM Conveys the value of TERM (the terminal code) to any UNIX system program that is terminal dependant.

3. tput init Initializes the terminal so that it will function properly with various UNIX system programs.

4. vi filename Accesses the vi screen editor so that you can edit a specified file.

5. vi file1 file2 file3 Enters three files into the vi buffer to be edited. Those files are file1, file2, and file3 .

6. view file Invoke vi editor on file in read-only mode

7. vi -R file Invoke vi editor on file in read-only mode

8. vi -r file Recover file and recent edits after system crash

13.3. Setting Options

1. :set option Activate option

2. :set option=value Assign value to option

3. :set no option Deactivate option

4. :set Display options set by user

5. :set all Display list of all current options, both default and those set by the user

6. :set option ? Display values of option

13.4. Notations used

Notations:

1. CTRL-c CTRL is the control key: CTRL-c means "control c"

2. CR is Carriage return (ENTER key)

13.5. Interrupting, cancelling

1. ESC end insert or incomplete command

2. &