[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: |
Wed, 14 Jul 1999 03:17:35 -0500 (CDT) |
On Tue, 13 Jul 1999, Vlad Harchev wrote:
> On Tue, 13 Jul 1999, Klaus Weide wrote:
> > On Tue, 13 Jul 1999, Vlad Harchev wrote:
> > > On Tue, 13 Jul 1999, Klaus Weide wrote:
> > > > On Tue, 13 Jul 1999, Vlad Harchev wrote:
> > > > > On Mon, 12 Jul 1999, Klaus Weide wrote:
> > > > >
> > > > > > I suggest the following be added at the end of lynx.cfg:
> > > > > > [ ... ] <-- text here
> > > > > > #INCLUDE:~/.lynx.cfg
> > -----
> > I wrote earlier that I don't care about what the suggested filename is,
> > but now I think that "~/.lynx.cfg" can still invite people to make bad
> > assumptions - the name encourages users to just copy the system-wide
> > /etc/lynx.cfg or /usr/local/lib/lynx.cfg to their home directory and
> > then change only what they want to change in that copy. That will
> > fail at least for the "INCLUDE" itself, if the user doesns't remove
> > it... (I havent' checked how the code deals with such a loop).
>
> lynx has a maximal allowed inclusion level (as I remember - 10).
>
> > So the name should indicate that the file is 'included' by something
> > else. I suggest .lynx.cfg-inc, maybe someone has a better idea?
>
> May be more explicit: .lynx.cfg-override?
So far I prefer -inc vs. -override:
1. It's shorter.
2. It doesn't override all of lynx.cfg (which one might assume based on
the name), and it doesn't override all settings (e.g. PRINTER would
add to the list).
Anyone else? :)
Klaus