Thread View: att.unix
2 messages
2 total messages
Started by Thomas Mellman
Thu, 04 Feb 1988 18:03
vi exrc behaviour has changed??!!
Author: Thomas Mellman
Date: Thu, 04 Feb 1988 18:03
Date: Thu, 04 Feb 1988 18:03
19 lines
1252 bytes
1252 bytes
It appears that vi's behaviour has changed with regards to its .exrc files. I used to (prior to sysV R3) keep my basic set of vi options and macros in the EXINIT variable, and more specific macros in particular directories. For example, in directories where I do C work, I have a .exrc file tailored for that kind of work, and in my documentation directories, I have a different .exrc file. 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. It seems that somebody decided that since he didn't use the old .exrc feature, nobody else did either, and just quietly lopped it off. I am disappointed.
Re: vi exrc behaviour has changed??!!
Author: Mike Cherepov
Date: Sat, 06 Feb 1988 17:41
Date: Sat, 06 Feb 1988 17:41
20 lines
1471 bytes
1471 bytes
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. > 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. > It seems that somebody decided that since he didn't use the old .exrc > feature, nobody else did either, and just quietly lopped it off. I am > disappointed. Relax - the feature is still there (according to the specs doc, anyhow, I haven't tried it). Just modify your $HOME/.exrc file to include the line: set exrc that should restore the functionality. Alternatively, you can try "set exrc" with EXINIT. And, surprise, there was a VERY good reason for this change, but I am reluctant to discuss it here. Good luck... Mike Cherepov [ihnp4!]whutt!cher
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads