Re: lynx-dev 'reloading' lynx.cfg (was: options (more, please))

[Leonid Pauzner]

17-Jul-99 11:05 David Combs wrote:
>> > > The almost-worst situation is having to change the .cfg.
>> > >
>> > I think you've got these two reversed, since the redoubtable Mr
>> > Pausner (I think) added re-sourcing lynx.cfg on-the-fly a while
>> > ago.  I use it quite a bit, and am very grateful to have it.
>> >

> QUESTION and NEED: How does a long-time user of lynx FIND OUT
> about these new features?

There is a features.html page for every release at sol.slcc.edu
It is a hand-edited text, discussed on lynx-dev when the release come.

Another option is trying to diff lynx.cfg and INSTALLATION
between your version and current [nearly all new features are configurable].

In fact, one may add a "history" link from lynxcfg_toc.html
to list new options added between releases starting 2.6 (IMHO),
it is not a big job.

> ----

> The "changes" we all see posted to this list are 99.9% re
> BUG FIXES.  Perhaps the special string "xxFEATURE:" or
> "^NEWFEATURE" (uppercase, plus maybe "--------" following it
> to the right, blank line before and after, making it easier to
> see), would help for that .1% that affects (effects?) our USAGE
> of lynx.

may be, but see above.
> ---

> Of course, some ONE person could do that FOR us all, duplicating
> that .1% into a SECOND "featureCHANGES" file -- that way, the
> work would get done ONCE, instead of HUNDREDS of times, once
> per reader.