NetNews Usenet Archive 1992 #30/NN_1992_30.iso/spool/comp/unix/question/14614

Internet Message Format | 1992-12-11 | 1.7 KB

Path: sparky!uunet!cs.utexas.edu!sun-barr!ames!agate!doc.ic.ac.uk!uknet!comlab.ox.ac.uk!tbrann
From: [e-mail] (Tony Brannigan)
Newsgroups: comp.unix.questions
Subject: Re: .exrc file for vi customization
Message-ID: <[e-mail]>
Date: 11 Dec 92 23:17:26 GMT
References: <smr.723822561@hitkw14> <[e-mail]>
Organization: Oxford University Engineering Dept.
Lines: 27
Originator: tbrann@black

[e-mail] (Phil Hughes) writes:
|>I have one thing to add.  Much like Stephen's example I find that I need
|>different vi setups based on what I am working on.  To automate this
|>process I put the like
|>    so .viset
|>in my .exrc file.  Whenever vi is started it looks for the file .viset in
|>the current directory.  If found, it reads it in much the same as it reads
|>.exrc.  If it doesn't find it an error message that that effect quickly
|>blinks on the status line and things continue.
|>
|>This makes it possible to have special vi setups for various directories.
|>Thus, when I am working on documentation I put a .viset in the
|>documentation directory that binds function keys to troff font changes and
|>sets a wrap margin.

In any implementation of vi I have used, it checks the current directory
for a file called ".exrc".  It first checks your home directory for a
.exrc, and if it finds it sources it, then checks the current directory
for a .exrc and, if it finds it, sources it.

This assumes you have not set the EXINIT environment variable.

Tony
--
"And soon all of us will sleep under the earth, | [e-mail]
  we who never let each other sleep above it."  | [e-mail]
   Marina Tsvetayeva 1915                       | [e-mail]