29-Mar-2000 12:21 Klaus Weide wrote:
> 2) The classification of lynx.cfg options that is used for the
> HTML generated from it, i.e. all the ".h1" added to lynx.cfg, is
> illogical, unsystematic, and often just plain wrong. Frankly, it
...
> may have changed. This was my impression when I first looked at
> it. Does anyone (other than the author, perhaps) find the lynx.cfg-
> generated HTML useful in its current state?
Yes, I think it is very useful in general,
but several .h1 groups should be splited/renamed/described
in a better way. That is something we could change easily
but obviously nobody except the original author was bothering about.
I think proxy variables should be moved from "Internal behaviour"
into the separate group "Proxy"; misterious "Content/Rendering"
should be renamed to "Character sets" (oh, how many options
now in this group... there is also my contribution in this unlikely
tradition). Other corrections always welcome:)
(Original Vlad's design assumed that one option could belongs to several
.h1 groups, which could be more logical for certain cases,
but apperently Tom's implementation support only one single group.
So we should live with that.
