Re: lynx-dev suggested addition to lynx.cfg

[Vlad Harchev]

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:
> > > > > [ ... ]
> > > > > #INCLUDE:~/.lynx.cfg

> 
> [...] 
> >  This is not bad idea to allow users to use configure more settings of lynx.
> > But it seems to me that the best solution to add the text you propose,
> > commenting last line (the very INCLUDE line) - so it won't break something 
> > and
> > it will notify users about the powerful approach they can use.
> 
> That was exactly the intention - the file should be shipped with the
> "INCLUDE" commented out as "#INCLUDE".  Definitely it should be shipped
> that way by lynx-dev, if a distribution wants to enable it by default
> (instead of leaving as a comment for users) it's their choice but I
> wouldn't recommend it.

 Sorry I forgot that the line was commented.
 
> [...] 
> >  So, my conclusion: we can add this text, but IMO commenting the very 
> > INCLUDE
> > line.
> 
> As I said, that was the idea.

 As long as all is commented, these few lines won't hurt - and seems that they
can help.

>      -----
> 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?
 
> (I don't think the more-than-three-character file extension is an
> issue, the text already limits the suggestion to "Unix-like systems",
> and no such file will actually be included in a lynx source .zip .)
> 
> >  Is your clock correct, Klaus? 
> 
> As far as I know. :)   It may be off a few seconds...

 Poor you..

>    Klaus
> 

 Best regards,
  -Vlad