Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!mit-eddie!bu-cs!encore!xylogics!loverso
From: loverso@Xylogics.COM (John Robert LoVerso)
Newsgroups: comp.mail.mush
Subject: Re: Sourcing (and not sourcing) Mushrc
Message-ID: <5527@xenna.Xylogics.COM>
Date: 14 Jul 89 15:57:30 GMT
References: <28509@pbhya.PacBell.COM> <114962@sun.Eng.Sun.COM> <672@aurora.AthabascaU.CA> <115054@sun.Eng.Sun.COM> <5395@xenna.Xylogics.COM> <3749@ogccse.ogc.edu> <3750@ogccse.ogc.edu>
Reply-To: loverso@Xylogics.COM (John Robert LoVerso)
Organization: Xylogics, Inc., Burlington MA
Lines: 18

In article <3750@ogccse.ogc.edu> schaefer@ogccse.UUCP (Barton E. Schaefer) writes:
> Would you rather it sourced the default Mushrc AFTER it sourced yours?!?
> The idea is that your .mushrc overrides the defaults ...

I forgot to mention the driving reason behind what I did.  My thoughts are
that my .mushrc completely overrides the `default' Mushrc.  I don't want
to have to possibly undo whatever my system administrator added in there.
(well, I'm him, but that's besides the point).  If I really want the stuff
in Mushrc, I can always put a "source /usr/local/lib/mush/Mushrc" in MY
own .mushrc.

I'd be happy with an option ("-N"?) that just prevented mush from sourcing
the Mushrc, but left the sourcing of my .mushrc alone. 

(ps: I've always had my own "make install" for mush, which copies to
/usr/local/lib/mush, among other things, the numerous README files, etc).

John