From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: larsi@gnus.org, 13649@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#13649: boobytrapped dired-do-async-shell-command question
Date: Wed, 11 May 2022 14:38:51 +0300 [thread overview]
Message-ID: <835ymcs3hw.fsf@gnu.org> (raw)
In-Reply-To: <86ilqc8rn8.fsf@mail.linkov.net> (message from Juri Linkov on Wed, 11 May 2022 10:17:31 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: larsi@gnus.org, 13649@debbugs.gnu.org, jidanni@jidanni.org
> Date: Wed, 11 May 2022 10:17:31 +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.
next prev parent reply other threads:[~2022-05-11 11:38 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 16:25 bug#13649: boobytrapped dired-do-async-shell-command question jidanni
2013-02-07 17:01 ` Stefan Monnier
2013-02-07 17:11 ` jidanni
2013-02-08 8:25 ` Juri Linkov
2013-02-08 13:44 ` Eli Zaretskii
2013-02-08 16:03 ` Stefan Monnier
2013-02-08 16:07 ` Eli Zaretskii
2013-02-08 16:59 ` Stefan Monnier
2013-02-08 17:07 ` Drew Adams
2013-02-08 16:33 ` Drew Adams
2013-02-09 0:46 ` Juri Linkov
2013-02-09 8:33 ` Eli Zaretskii
2013-02-08 15:11 ` Stefan Monnier
2013-02-09 0:49 ` Juri Linkov
2013-02-09 1:47 ` Stefan Monnier
2013-02-10 10:10 ` Juri Linkov
2013-02-10 16:19 ` Stefan Monnier
2013-02-09 3:36 ` jidanni
2013-02-10 13:22 ` jidanni
2013-02-10 13:52 ` Juri Linkov
2013-02-10 14:20 ` jidanni
2013-02-10 15:22 ` Juri Linkov
2013-02-10 15:28 ` jidanni
2013-02-11 9:18 ` Juri Linkov
2022-04-24 13:49 ` Lars Ingebrigtsen
2022-04-24 15:44 ` Juri Linkov
2022-04-24 15:57 ` Lars Ingebrigtsen
2022-04-25 15:40 ` Juri Linkov
2022-04-26 9:49 ` Lars Ingebrigtsen
2022-04-26 15:44 ` Juri Linkov
2022-04-27 12:11 ` Lars Ingebrigtsen
2022-05-08 17:49 ` Juri Linkov
2022-05-08 18:57 ` Eli Zaretskii
2022-05-09 18:42 ` Juri Linkov
2022-05-09 19:20 ` Eli Zaretskii
2022-05-11 7:17 ` Juri Linkov
2022-05-11 11:38 ` Eli Zaretskii [this message]
2022-05-11 17:06 ` Juri Linkov
2022-05-11 17:40 ` Eli Zaretskii
2022-05-12 16:52 ` Juri Linkov
2022-05-12 17:21 ` Eli Zaretskii
2022-05-12 17:34 ` Juri Linkov
2022-05-12 17:39 ` Eli Zaretskii
2022-05-11 20:27 ` Drew Adams
2022-05-12 5:22 ` Eli Zaretskii
2022-05-12 16:19 ` Drew Adams
2022-05-12 16:54 ` Juri Linkov
2022-05-09 9:42 ` Lars Ingebrigtsen
2022-05-09 9:43 ` Lars Ingebrigtsen
2022-05-09 18:47 ` Juri Linkov
2022-05-10 1:53 ` Lars Ingebrigtsen
2022-05-11 16:59 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=835ymcs3hw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13649@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).