Re: lynx-dev dev21: What broke "quit on anything other than y"?

[dickey]

> > This new, changed behavior is probably more technically correct, but I 
> > too certainly prefer the old behavior. 
>  
> I also prefer the old behavior. 

well, I thought I had it right - I'll sort this out.
  
> The stanza in lynx.cfg says: 
>  
> # If QUIT_DEFAULT_YES is TRUE then when the QUIT command is entered, any 
> # response other than n or N will confirm.  It should be FALSE if you 
> # prefer the more conservative action of requiring an explicit Y or y to 
> # confirm.  The default defined here will override that in userdefs.h. 
>  
> But this no longer matches Lynx's behavior.  The current behavior is 
> approximately: 
>  
>   If QUIT_DEFAULT_YES is TRUE then when the QUIT command is entered, the 
>   resulting "are you sure" prompt shows "(y)" as the default, whereas if 
>   it is false, the prompt shows "(n)".  The prompt then accepts only 
>   "y", "n", or <Return> (which accepts the specified default). 

there's also the ^C for interrupt and ^G for cancel.
  
> >Bela< 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey