vi exrc behaviour has changed??!!

[Frank Rahmani]

In article <2853 at whutt.UUCP>, cher at whutt.UUCP (Mike Cherepov) writes:
> In article <329 at ttrde.UUCP>, mellman at ttrde.UUCP (Thomas Mellman) writes:
> > It appears that vi's behaviour has changed with regards to its .exrc files.
> > This has been a practical way to handle a limited number of special function
> > keys, and limited amount of macro space.
> > Now that we are moving to a R3 machine, I find that if I have the EXINIT
> > variable set, no further .exrc file reading takes place.  Furthermore,
> > even when the EXINIT variable is not set, only the .exrc file in my home
> > directory is read.
If EXINIT is set no $HOME/.exrc file will be read. To tell vi to read
other files on startup,
include a line:
so '//full/pathname/of/file/to/be/read/'
in $HOME/.exrc e.g.
so '//usr/local/scripts/.exrc'
to read a systemwide .exrc file. This works for me anyway.
fmr at cwi.nl

-- 
It is better never to have been born. But who among us has such luck?
----- News saved at 9 Feb 88 08:22:25 GMT
In article <2853 at whutt.UUCP>, cher at whutt.UUCP (Mike Cherepov) writes:
> In article <329 at ttrde.UUCP>, mellman at ttrde.UUCP (Thomas Mellman) writes:
> > It appears that vi's behaviour has changed with regards to its .exrc files.
> > This has been a practical way to handle a limited number of special function
> > keys, and limited amount of macro space.
> > Now that we are moving to a R3 machine, I find that if I have the EXINIT
> > variable set, no further .exrc file reading takes place.  Furthermore,
> > even when the EXINIT variable is not set, only the .exrc file in my home
> > directory is read.
If EXINIT is set no $HOME/.exrc file will be read. To tell vi to read
other files on startup,
include a line:
so '//full/pathname/of/file/to/be/read/'
in $HOME/.exrc e.g.
so '//usr/local/scripts/.exrc'
to read a systemwide .exrc file. This works for me anyway.
fmr at cwi.nl

-- 
It is better never to have been born. But who among us has such luck?