Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!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: <11947@smoke.BRL.MIL>
Date: 12 Jan 90 22:02:44 GMT
References: <1792@ncrcce.StPaul.NCR.COM> <1864@sauron.Columbia.NCR.COM> <11888@smoke.BRL.MIL> <1990Jan7.175807.13054@NCoast.ORG>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 20

In article <1990Jan7.175807.13054@NCoast.ORG> allbery@ncoast.ORG (Brandon S. Allbery) writes:
>As quoted from <11888@smoke.BRL.MIL> by gwyn@smoke.BRL.MIL (Doug Gwyn):
>| 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??
>I think the csh behavior cited above is more correct.  I've gotten sick of
>kluging around Altos's csh, which invokes .cshrc before /etc/cshrc

Certainly /etc/profile should be sourced before ~/.profile.
There should NOT be a /etc/shrc at all, and ~/.shrc (or better,
the file specified by the ENV environment variable) should be
sourced ONLY for an interactive shell and after ~/.profile for
a login shell.

Shell features should not be added as isolated items, but rather
designed carefully to work together.  We use the above approach
at BRL to provide extremely spiffy user environments both with
and without multiple windows.