[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev suggested addition to lynx.cfg

From: Klaus Weide
Subject: Re: lynx-dev suggested addition to lynx.cfg
Date: Tue, 13 Jul 1999 01:06:56 -0500 (CDT)

On Tue, 13 Jul 1999, Henry Nelson wrote:
> > I suggest the following be added at the end of lynx.cfg:
> > 
> > # If an installation or distribution uses a (properly modified) copy
> [...]
> > #INCLUDE:~/.lynx.cfg
> > 
> > Comments?
> Only to ask why "at the end."  Why not at the top together with all the
> other #INCLUDE information?  (Alternately, move the INCLUDE stuff to the
> very bottom of lynx.cfg.  It seems more logical to have it the first one,
> however.)

It should be at the end so that users' settings can override the
default settings.  I assume that would normally be the desired behavior.
("normally" = no restrictions imposed on users, can change anything -
when something else is needed, the INCLUDE hopefully won't get

> Having duplicate defines widely spaced in the lynx.cfg file
> makes it just that more complex to extract unique strings from lynx.cfg.

Ok, there should also be a pointer near the beginning, where INCLUDE
is explained, that points to the end.  I suggest adding after

# Then in ~/lynx.cfg:
#   INCLUDE:/usr/local/lib/lynx.cfg
#           ^^^^^^^^^^^^^^^^^^^^^^^ or whatever is appropriate on your system
# and now your own tweaks.

# This can also be used the other way around: Instead of a user-specified
# file including the global configuration file, the global file can
# include user-specific files.  See the end of this file.

Is this better?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]