Re: LYNX-DEV mail ==> nifty idea: "SOURCE <file>" in lynx.cfg

[David Combs]

> From address@hidden Sat Nov 16 07:12:35 1996
> From: (James Spath)
> 
> On Nov 16,  6:23am, address@hidden wrote:
> } Thus, AGAIN: sure would be nice to be able to have
> } my OWN lynx.cfg, real small, of JUST THOSE things
> } that I want to DIFFER between my own use and the
> } settings decided-upon by the sys-adm.
> } 
> } Someone replied to my previous suggestion of this idea
> } that these things could simply go into the user's ".lynxrc".
> 
> I use "lynx -cfg my-lynx-cfg".  It has worked since at least 2.3.7.
> By stripping the comments out of the system-wide one with 
> a command like " grep -v '^#' lynx.cfg | grep -v '^$' ",
> I get a starting file size that is very short.
> 
> Having local overrides would be simpler except for additive
> settings such as DOWNLOADER.

Yes, your scheme is nice (-cfg), except for when the
sys-adm MODIFIES the standard one.

OR -- more likely -- he installs a NEW LYNX -- and
then you MUST redo all your stuff.

Maybe (a ha!) if a "source" pseudo-command was added
to lynx.cfg (and to .lynxrc too!), just the way that
csh has a "source" commmand, sh has a "." command,
and VI/ex has a ":source" command (which I use all the
time!)


Now THERE'S an EASY solution -- just add that one
command ("source <filename>").


;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;