From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 57792@debbugs.gnu.org, Vladimir Nikishkin <lockywolf@gmail.com>
Subject: bug#57792: 29.0.50; async-shell-command fails with prefix-argument on -master
Date: Wed, 14 Sep 2022 16:13:41 +0200 [thread overview]
Message-ID: <87czby82ne.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkm=DMs_4ANgVwSYnqZuYjDkduu38RAeBXTEjD64fxDM6Ag@mail.gmail.com> (Stefan Kangas's message of "Wed, 14 Sep 2022 00:51:54 -0700")
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?
next prev parent reply other threads:[~2022-09-14 14:13 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 [this message]
2022-09-14 14:17 ` Vladimir Nikishkin
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=87czby82ne.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=57792@debbugs.gnu.org \
--cc=lockywolf@gmail.com \
--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).