GNU bug report logs - #13649
boobytrapped dired-do-async-shell-command question

Previous Next

Package: emacs;

Reported by: jidanni <at> jidanni.org

Date: Thu, 7 Feb 2013 16:28:02 UTC

Severity: minor

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Juri Linkov <juri <at> linkov.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: larsi <at> gnus.org, 13649 <at> debbugs.gnu.org, jidanni <at> jidanni.org
Subject: bug#13649: boobytrapped dired-do-async-shell-command question
Date: Wed, 11 May 2022 20:06:00 +0300
>>   (y-or-n-p "File ‘foo.el’ exists; overwrite?")
>> 
>> ‘C-l’, ‘C-v’, ‘M-v’ work fine and scroll the original buffer.
>> 
>> But yes-or-no-p (BTW, it requires the space char at the end of the prompt):
>> 
>>   (yes-or-no-p "Buffer foo.el modified; kill anyway? ")
>> 
>> ‘C-l’, ‘C-v’, ‘M-v’ don't scroll the original buffer.
>
> Isn't that expected?  y-or-n-p doesn't need to allow you to edit the
> text in the minibuffer.

Maybe this difference is unimportant.  But still remains the need
to find a key to show help text from yes-or-no-p.  y-or-n-p now
uses C-h to show help, but in yes-or-no-p C-h is useful as
a help key prefix.




This bug report was last modified 3 years and 88 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.