LYNX-DEV Re: Re: extended "show color" choice

[Hiram Lester, Jr.]

On Thu, 24 Jul 1997, Klaus Weide wrote:

> Not sure which "initial reaction" you mean.  If you mean your message 
> about the fact that "forcing" color on, in spite of a mono-only terminfo
> description, doesn't work with curses - that's not addressed in what you
> quoted. But mentioned briefly in the section before:

The initial reaction was the writing or not writing of info and your
mention if the paragraph I had quoted of maintaining that information
across sessions.  More below.

> Maybe it is not clear what "NOT saving in .lynxrc" means.  Since .lynxrc
> is completely rewritten each time the '>' saving is done, not writing
> any "show_color:blah" to the file means there won't be any
> "show_color:blah" in the file, even if it was there before (in the
> previous version). The .lynxrc file is not a database where individual
> records can be updated (or left unchanged) independently.

Yes, I'm aware of this behavior of .lynxrc from where I added the flag for
standard or advanced multi-bookmark support.  My confusion is that in the
long paragraph I quoted, you seemed to be saying something about
maintaining the state of always ON/OFF even if they switched it to just
plain on or off and saved.  Maybe you meant that if they switched and
DIDN'T save that all would be left as before...

   +------------------------------------+-------------------------------+
   | Hiram W. Lester, Jr.               | E-Mail: address@hidden    |
   | Computer Science                   | Home page:                    |
   | Middle Tennessee State University  |   http://pobox.com/~hwlester/ |
   +------------------------------------+-------------------------------+

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;