From: Vladimir Nikishkin <lockywolf@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57792@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#57792: 29.0.50; async-shell-command fails with prefix-argument on -master
Date: Wed, 14 Sep 2022 22:17:23 +0800 [thread overview]
Message-ID: <87fsgu2g0f.fsf@laptop.lockywolf.net> (raw)
In-Reply-To: <87czby82ne.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> I can reproduce this bug on master, 27.1 and 28.2. Here's a test case
>> (not tested):
>>
>> (ert-deftest simple-tests-async-shell-command-57792 ()
>> "Test for https://debbugs.gnu.org/57792 ."
>> (with-temp-buffer
>> ;; Pretend we have a prefix argument.
>> (async-shell-command "echo \"test\"" '(4))
>> (should (equal (buffer-string) "test"))))
>>
>> I'm not sure what behavior we want here, though. Should we insert the
>> command output directly at point in the current buffer, or should we
>> first insert it into "*Async Shell Command*" and copy it over when done?
>
> The prefix isn't documented to do anything (and currently bugs out), so
> perhaps we should just remove the prefix from the interactive spec
> instead?
> Is the intention that `C-u M-&' insert the output in the current buffer?
I am quite sure it used to do that in the past. Perhaps, as late as
27.2. I can try to do a bisect to find when exactly this has changed.
Moreover, it would be analogous to C-u M-: inserting the return value
into the buffer at point.
--
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)
next prev parent reply other threads:[~2022-09-14 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 3:55 bug#57792: 29.0.50; async-shell-command fails with prefix-argument on -master Vladimir Nikishkin
2022-09-14 7:51 ` Stefan Kangas
2022-09-14 14:13 ` Lars Ingebrigtsen
2022-09-14 14:17 ` Vladimir Nikishkin [this message]
2022-09-14 14:36 ` Vladimir Nikishkin
2022-09-14 15:10 ` Lars Ingebrigtsen
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=87fsgu2g0f.fsf@laptop.lockywolf.net \
--to=lockywolf@gmail.com \
--cc=57792@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefankangas@gmail.com \
/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).