Path: utzoo!mnetor!uunet!mcvax!bsovax!pim
From: pim@bsovax.UUCP (Pim Willemsen)
Newsgroups: comp.bugs.sys5
Subject: Re: vi exrc behaviour has changed??!!
Message-ID: <282@bsovax.UUCP>
Date: 15 Feb 88 09:03:05 GMT
References: <329@ttrde.UUCP> <2853@whutt.UUCP>
Reply-To: pim@BSOVAX.UUCP (Pim Willemsen)
Organization: BSO/AT, P.O.Box 8052, 3503 RB UTRECHT, The Netherlands
Lines: 25
Keywords: EXINIT .exrc CWD

In article <2853@whutt.UUCP> cher@whutt.UUCP (Mike Cherepov) writes:
>In article <329@ttrde.UUCP>, mellman@ttrde.UUCP (Thomas Mellman) writes:
>> It appears that vi's behaviour has changed with regards to its .exrc files.
>> even when the EXINIT variable is not set, only the .exrc file in my home
>> directory is read.
>
>Just modify your $HOME/.exrc file to include the line:
>set exrc

We are running 4.1 BSD and I use EXINIT to define some key-sequences 
that contain a ^D; as this doesn't seem to work in a .exrc file.
So the environment variable EXINIT looks like:

    map ^D B|etc...|source $HOME/.exrc

The vertical bar '|' is a separator and the source command directs 
vi to read further key mappings from the file .exrc in my home directory. 
This works just fine.  I don't know whether the source command
is available in system V.

-- 
------------------------------------------------------------------------------
   Pim Willemsen           |    =========   BSO/Automation Technology
   mcvax!bsovax!pim        |    == BSO ==   POB 8052
                           |    =========   3503 RB  Utrecht, The Netherlands