Re: System-wide jed.rc that does not get overwritten when jed is upgraded?

[Lloyd Zusman <ljz@xxxxxxxxxx>]

Lloyd Zusman <ljz <at> asfast.com> writes:

> 
> Lloyd Zusman <ljz <at> asfast.com> writes:
> 
> > [ ... ]
> >
> [ ... ]
> 
> But in looking at the end of site.sl, I realized that there is another 
> Unix-specific solution that is even easier. If defaults.sl is not found,
> a file called jed.conf is searched for in /etc and /usr/etc. I can put
> system-wide, startup-specfic code in that file, which also solves my
> problem.

... but this still requires me to redefine command_line_hook(), because
/etc/jed.conf gets loaded _before_ the standard command_line_hook() causes
$JED_ROOT/lib/jed.rc to be loaded. This means that any settings that I
put into jed.conf will get overwritten by variables that are set
in $JED_ROOT/lib/jed.rc.  This significantly diminishes the usefulness
of this centralized jed.conf file.

So I can either use the standard /etc/jed.conf mechanism and have it
redefine command_line_hook(), or I can do this redefine within defaults.sl.

Well, neither of these options would be the end of the world, but I think
it would be better if the standard installation of jed would allow something
like /etc/jed.conf to _override_ $JED_ROOT/lib/jed.rc settings, instead of
the opposite.

Thoughts?

-- 
 Lloyd Zusman
 ljz@xxxxxxxxxx
 God bless you.





--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.