GNU bug report logs - #57792
29.0.50; async-shell-command fails with prefix-argument on -master

Previous Next

Full log

View this message in rfc822 format

From: Vladimir Nikishkin <lockywolf <at> gmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 57792 <at> debbugs.gnu.org, Stefan Kangas <stefankangas <at> gmail.com>
Subject: bug#57792: 29.0.50; async-shell-command fails with prefix-argument on -master
Date: Wed, 14 Sep 2022 22:36:19 +0800

Maybe I am confusing it with C-u M-! , but for the async version would
do the same would make sense.

Vladimir Nikishkin <lockywolf <at> gmail.com> writes:

> Lars Ingebrigtsen <larsi <at> gnus.org> writes:
>
>> Stefan Kangas <stefankangas <at> 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)

Previous Next

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