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

[Klaus Weide]

On Fri, 16 Jul 1999, Leonid Pauzner wrote:
> 16-Jul-99 06:24 Klaus Weide wrote:

> > What happens to the seetings that add to a list - like PRINTER,
> > DOWNLOADER, UPLOADER, VIEWER, RULES.  I expect that, without
> > "clearing" those lists, each reloading of the .cfg file will
> > just grow them.
> 
> No, these lists are cleared in reload_read_cfg(),
> was done before 2.8.2 release.

It seems PRINTER, DOWNLOADER, UPLOADER, EXTERNAL lists are cleared.
I overlooked the free_lynx_cfg() when I checked briefly before writing
the above.

RULE / RULESFILE aren't, but a call to HTClearRules() *may* be enough
to do that.

VIEWERs also aren't cleared, and that would be much more tricky
since viewers end up in the HTPresentations list (maintained in
HTFormat.c) together with MIME presenters / converters from
various sources.  Also reloading now should put VIEWERs at the
head of the list so the will have precedence; VIEWERs from lynx.cfg
loaded normally at startup have the lowest precedence.  (should ==
because I didn't test it)

SUFFIX looks similar to VIEWER, entries end up intermixed with
suffix mappings from other sources.

Changing mailcap / mime.types locations won't have an effect.

This (VIEWER/SUFFIX/mailcap/mime.types) could maybe be solved
by clearing the lists and completely starting from scratch with 
HTFormatInit(), HTFileInit().  That means repeating more and
more of the normal main() startup sequence in reload_read_cfg.

KEYMAPs looks like another 'little' thing that doesn't work quite
right; mappings done by the original lynx.cfg cannot be completely
undone.  (Also the PASS flag I added cannot be undone.)

   Klaus