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

Previous Next

Full log

Message #139 received at 13649 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Juri Linkov <juri <at> linkov.net>, Eli Zaretskii <eliz <at> gnu.org>
Cc: "larsi <at> gnus.org" <larsi <at> gnus.org>,
 "13649 <at> debbugs.gnu.org" <13649 <at> debbugs.gnu.org>,
 "jidanni <at> jidanni.org" <jidanni <at> jidanni.org>
Subject: RE: [External] : bug#13649: boobytrapped dired-do-async-shell-command
 question
Date: Wed, 11 May 2022 20:27:39 +0000

> >>   (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.

Apologies for not following this.
If you're looking for a key that will show some help,
maybe consider `?'.

I use that in `dired+.el' for some similar things.
And `dired.el' uses it for `dired-summary' (to show
why something went wrong).

Previous Next

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