Re: lynx-dev pre.10 : Options Form/Menu

[Nelson Henry Eric]

> we can drop Menu (as far as your needs go: someone else might object).

Probably will not be able to since some people find the original menu
easier to use than the new forms menu.  (Which is all the more reason
for keeping the compile option available.)

> but whether we keep it or not, we don't need the current configure switch
> unless someone wants specifically to compile ONLY with the Menu.
                                                             ^^^^
? You mean unless someone wants to compile ONLY with the new FORMS menu.

> if you don't want that, is there anyone else who does?

I DO want that, which is why I would like the already-implemented
compile option to not go away.

> which bit(s) of this do you disagree with (smile again)?

We seem to agree that we want, with our own personal Lynxes, to use the
new forms-based options menu.  I would like to be able to easily, without
having to patch the code all the time, NOT compile in the code for the
old-style menu and only use the new forms-based menu.  I know what I want,
so a configure option and/or command line toggle is meaningless for me.
You seem to want both sets of code compiled in no matter what so that you
choose not to use the one that you could choose to not compile in in the
first place with the compile option in question. :-)

Seems that we disagree about whether or not the compile option should
stay around or not. :-), again.  22Kb x (4 or 5) isn't worth arguing
about anymore.  If I can't do it with autoconf, I suppose setting CPPFLAGS
will work about as well.  It's up to Tom.

__Henry