Re: LYNX-DEV LYNX reads "off" from .lynxrc set_cursor=on

[Greg Marr]

>It seems to me necessary that these cmd-line options have
>the SAME EFFECT regardless of WHERE you run lynx.

They do have the exact same effect regardless of where you run lynx, they
toggle the state of a variable which is defined in a configuration file.
They just don't have the effect that you thought/desired that they do.
What difference does it make whether the default is chosen at compile time
or at run time from a config file?  Either way, the default can be changed
at any time.  The first method just requires a little more work.

>Otherwise is equal to the effect of being able to
>redefine "yes" to be "no", WITHOUT TELLING THE USER.

There is no redefinition of yes to no.  The configuration file is read
first, and then any command line toggles are applied to that configuration.
 If someone changes the defaults in either the compiled binary or the
config file, it is either the user who changed it, in which case the user
is told, or it is the administrator of the machine, in which case the
administrator should tell the users that the default has changed.

>Is EXTREMELY user-antagonistic.

I still don't see how this is the case.

--
Greg Marr
address@hidden
"We thought you were dead." 
"I was, but I'm better now." - Sheridan, "The Summoning"