On Wed, 29 Mar 100, T.E.Dickey wrote:
> these issues were brought up last, iirc, in the early fall (except for
> the comment about the content of the htmlized cfg file - which has little
> to do with making a release useless).
Yes, I am aware of the debates whether this should be added at
all or not. That's not my point, I am not trying to reopen those
debates. I not asking for new mechanisms or scripts or the withdrawal
of existing ones, but for some content editing (preferably by those
who insisted so much on _having_ an organized lynx.cfg overview -
What's the point in having it if it's not organized?). And when's a
better time to ask for it than now?
> otoh, there's all that bad press relating to the security issues.
Well, I wouldn't object if you released the current code as 2.8.3
tomorrow and be done with it. But if there is to be a lengthy
pre-release period, you have to expect that problems are brought up...
> we're at a good point to validate what we have & decide whether to
> go & release it (with corrections as needed), or find that there's
> little support for refining the boolean logic of the commandline
> options.
It doesn't take much "refining". Just getting rid of the intermediate
LYUseDefShoCur and LYUseDefSelPop (set LYShowCursor and LYSelectPopups
directly in LYMain.c, as for other flags) should solve the problem for
-show_cursor and -popup, at least.
Klaus
