[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LYNX-DEV LYNX reads "off" from .lynxrc set_cursor=on
From: |
Larry W. Virden, x2487 |
Subject: |
Re: LYNX-DEV LYNX reads "off" from .lynxrc set_cursor=on |
Date: |
Thu, 19 Feb 1998 12:13:16 -0500 |
From: David Combs <address@hidden>
> Isn't it a BUG that the "=on" isn't caught and
> COMPLAINED about?
>
> Or, that the "=on" doesn't simply get processed
> as if it WERE in .lynxrc.
Neither. However, it is an unobvious behavior that, depending on the
value of the userdefs.h, lynx.cfg and user's lynx.rc, setting some command
switchs to on may mean 'turn on the feature' and may, for the next
user, mean 'turn off the feature'.
It seems to me, from the point of view of someone trying to explain
how to use lynx to others, that a more consistent view would be to
always have on mean 'turn this option on' and off mean 'turn this option
off'.
Then, if the system is configured so that the user is not permitted
to turn something on or off, that an error to the trace file (or stderr)
is generated.
--
Larry W. Virden INET: address@hidden
<URL:http://www.teraform.com/%7Elvirden/> <*> O- "We are all Kosh."
Unless explicitly stated to the contrary, nothing in this posting should
be construed as representing my employer's opinions.
Re: LYNX-DEV LYNX reads "off" from .lynxrc set_cursor=on, Al Gilman, 1998/02/19
Re: LYNX-DEV LYNX reads "off" from .lynxrc set_cursor=on, David Combs, 1998/02/19
Re: LYNX-DEV LYNX reads "off" from .lynxrc set_cursor=on, Nelson Henry Eric, 1998/02/19