From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: jrvarma@gmail.com, 36331@debbugs.gnu.org
Subject: bug#36331: 26.2; command run using dired-do-async-shell-command cannot take any input
Date: Wed, 18 May 2022 18:44:24 +0300 [thread overview]
Message-ID: <83zgjeetgn.fsf@gnu.org> (raw)
In-Reply-To: <87a6bec43g.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 18 May 2022 16:22:59 +0200)
> Cc: 36331@debbugs.gnu.org
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 18 May 2022 16:22:59 +0200
>
> > First command with "*" in the command line works as expected
> >
> > cat - * >2.txt
> >
> > With this command, the *Async Shell Command* buffer waits for us to
> > type in whatever lines that we want. When we terminate the input with
> > Control-D (EOF), the command concatenates the inputs lines with 1.txt
> > and writes the result to 2.txt.
>
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
>
> I can reproduce this, but I think that this works is more by accident
> than by design. I don't think the `&' command is supposed to allow any
> input to the command -- at least it's not documented to.
Indeed, asynchronous commands cannot rely on being able to read and
write standard streams. Interactive commands should not be run
asynchronously.
next prev parent reply other threads:[~2022-05-18 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 12:37 bug#36331: 26.2; command run using dired-do-async-shell-command cannot take any input Prof Jayanth R Varma
2022-05-18 14:22 ` Lars Ingebrigtsen
2022-05-18 15:44 ` Eli Zaretskii [this message]
2022-05-19 23:36 ` Lars Ingebrigtsen
2022-05-20 3:32 ` Michael Heerdegen
2022-05-20 8:37 ` Lars Ingebrigtsen
2022-05-21 1:58 ` Michael Heerdegen
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=83zgjeetgn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36331@debbugs.gnu.org \
--cc=jrvarma@gmail.com \
--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).