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


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juri Linkov <juri <at> linkov.net>
Cc: larsi <at> gnus.org, 13649 <at> debbugs.gnu.org, jidanni <at> jidanni.org
Subject: Re: bug#13649: boobytrapped dired-do-async-shell-command question
Date: Mon, 09 May 2022 22:20:34 +0300
> From: Juri Linkov <juri <at> linkov.net>
> Cc: larsi <at> gnus.org,  13649 <at> debbugs.gnu.org,  jidanni <at> jidanni.org
> Date: Mon, 09 May 2022 21:42:40 +0300
> 
> >> BTW, (info "(emacs) Yes or No Prompts") says:
> >>
> >>      With both types of yes-or-no query the minibuffer behaves as
> >>   described in the previous sections; you can recenter the selected window
> >>   with ‘C-l’, scroll that window (‘C-v’ or ‘PageDown’ scrolls forward,
> >>   ‘M-v’ or ‘PageUp’ scrolls backward)
> >>
> >> But in fact ‘C-l’ doesn't scroll the window, ‘C-v’ and ‘PageDown’ don't
> >> scroll forward, and ‘M-v’ and ‘PageUp’ don't scroll backward.  Should they?
> >
> > They do here.  What did you try, exactly?
> 
> They do to some extent for y-or-n-p, but not at all for yes-or-no.

I actually tested with yes-or-no-p.

Again, would you tell what you tried and what happened, as opposed to
what you expected to happen?  I think there might be a
misunderstanding here.




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.