Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.unix.wizards
Subject: Re: SYS V Bourne Shell .shrc file
Message-ID: <11888@smoke.BRL.MIL>
Date: 5 Jan 90 03:33:51 GMT
References: <1792@ncrcce.StPaul.NCR.COM> <1864@sauron.Columbia.NCR.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 10

In article <1864@sauron.Columbia.NCR.COM> wescott@micky.Columbia.NCR.COM (Mike Wescott) writes:
>In article <1792@ncrcce.StPaul.NCR.COM> mercer@ncrcce.StPaul.NCR.COM (Dan Mercer) writes:
>> The .shrc is also invoked prior to /etc/profile and ~/.profile on login.
>Nope.  After /etc/profile but before $HOME/.profile, mimicing csh's behavior.

Ugh -- it was obviously the wrong way around in csh, so why mimic that??

When we added support for $ENV in the BRL Bourne shell (more general than
.shrc, also doesn't require disabling in non-interactive uses such as
shell scripts), we did it right.