Re: LYNX-DEV Hmm..bug?

[Al Gilman]

  From: Nelson Henry Eric <address@hidden>

  > > > > (Of course ONLY a y or Y should mean "yes")
  > > > 
  > > > Not everyone agrees. That's why it's a build option.
  > 
  > I seemed to have missed something in the docs..the keypress for saying 
  > yes to Quit can be defined at build time?  Or are you referring to keymaps?
  
  Not the keypress or keymap, the behavior, i.e., if Lynx will exit on any
  input to the prompt besides n or N, or exit only upon y or Y.  Leave the
  following commented out in userdefs.h (the default) if you want the
  conservative behavior.
  
  /********************************
   * If QUIT_DEFAULT_YES is defined then when the QUIT command is entered,
   * any response other than n or N will confirm.  Comment this out if
   * you prefer the more conservative action of requiring an explicit
   * Y or y to confirm.
   */
  /* #define QUIT_DEFAULT_YES */
  
Personal opinions:

This is still an unhappy set of options.  If the function that goes
with default-to-yes were done "right" it wouldn't have to be optional.

Clearly, if "yes" is the default, then <RET> should translate to "yes."

The question of <SPACEBAR> is a close call.  If this were Elm, I would
say "Yes, <SPACEBAR> equates to accept-default."  In Lynx the usual 
JustDoIt synonyms are <RET> and right-arrow.  So those would be my
candidates for accept-default keys and not <SPACEBAR>.

While the current function associated with this build logical is
a feature of long standing, it is still a usability problem.
Having random keypresses accept the default detracts from the
"rated for use by humans" quality of Lynx.

As I say, IMHO.

--
Al Gilman

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