🚀 go-pugleaf

From: island!argv (Dan Heller)

> On Jul 14, 10:01am, Barton E. Schaefer wrote:

> On Jul 14,  3:57pm, John Robert LoVerso wrote:
> } Subject: Re: Sourcing (and not sourcing) Mushrc
> } 
> } In article 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.
> 
> Perhaps "-I init_file" to specify a file to be read before the folder is
> loaded, in the same way that -F reads one after the folder is loaded.
> Then you could use
> 
>     mush -n -I ~/.mushrc
> 
I agree that there should be an option to not source the system init
file.  I like -I, but would ammend that there can be a filename appended
to the arg in the following (ugly) manner:
    -I/usr/lib/Mushrc
or:
    -I
In the first case (the init file desired is attached to the arg), then
that file is used rather than the default init file.  If no filename is
attached to -I, then no default init file is used.

As for the user's .mushrc file, that can already be changed by the $MAILRC
env variable.  With the above scheme, it is now possible to configure,
at runtime, the location of both the default and the user's mushrc.  Also,
you can specify not to source either one of them.

I realize the syntax for -I as I've proposed it is ugly and incosnstent
with the rest of the mush args, but at least it solves this problem :-)

  --dan