GNU bug report logs -
#19467
25.0.50; Default arguments for 'yes-or-no-p'
Previous Next
Reported by: Dani Moncayo <dmoncayo <at> gmail.com>
Date: Mon, 29 Dec 2014 19:34:01 UTC
Severity: wishlist
Tags: wontfix
Found in version 25.0.50
Done: Stefan Kangas <stefan <at> marxist.se>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
On Mon, Dec 29, 2014 at 10:32 PM, Drew Adams <drew.adams <at> oracle.com> wrote:
>> I'd like I could choose the "yes"/"no" answer via M-n/M-p (as
>> alternative to typing the answer directly in the minibuffer).
>
> FWIW, that defeats the purpose/intention of `yes-or-no-p'.
> We have `y-or-n-p' for quick response. The point of
> `yes-or-no-p' is presumably to slow you down and make you
> work a bit, so you take the question seriously. ;-)
I agree wrt the intention of 'yes-or-no-p': force the user to think
the answer well. But IMO:
1. Looking for a default value with "M-n... RET" entails some work;
it's not something inmediate like a single keystroke (as in
'y-or-n-p').
2. The behavior I'm requesting feels quite natural to me: When Emacs
asks for input with a minibuffer and there are a few valid (or even
typical) values, those values are available in the minibuffer
"future history".
--
Dani Moncayo
This bug report was last modified 5 years and 337 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.