From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: kill the LHS command of a pipe once the RHS command terminates
Date: Mon, 29 Jul 2019 08:54:19 -0700 [thread overview]
Message-ID: <CAH+w=7a8aBsxdF1Otwvbm7eWe=BC2T0Ny87j+sY5QW7oXM=j_Q@mail.gmail.com> (raw)
In-Reply-To: <20190729152309.GA17940@cventin.lip.ens-lyon.fr>
On Mon, Jul 29, 2019 at 8:24 AM Vincent Lefevre <vincent@vinc17.net> wrote:
>
> On 2019-06-28 13:04:30 +0200, Vincent Lefevre wrote:
> >
> > zira% head -n 1 <(echo foo; sleep 3; echo err >&2)
> > foo
>
> Another issue is that if the producer side tries to access the terminal
> (e.g. ssh, for a passphrase), all the processes of this side are stopped
> due to a SIGTTOU signal.
Even if they weren't stopped by TTOU, they'd almost certainly be
stopped by TTIN.
> Concerning the documentation, the zshexpn(1) man page does not say
> that a process in process substitution is run in background.
They have to be, otherwise either you'd need unlimited buffering or
the read of the descriptor could deadlock. If you want it run in the
foreground, use =(...).
> Later
> there's a mention of it being run asynchronously, but this term has
> never been defined.
In the JOBS section:
If the MONITOR option is set, an interactive shell associates a job
with each pipeline. It keeps a table of current jobs, printed by the
jobs command, and assigns them small integer numbers. When a job is
started asynchronously with `&', the shell prints a line to standard
error which looks like:
[1] 1234
indicating that the job which was started asynchronously was job number
1 and had one (top-level) process, whose process ID was 1234.
And then in the SIGNALS section:
Certain jobs are run asynchronously by the shell other than those
explicitly put into the background; even in cases where the shell would
usually wait for such jobs, an explicit exit command or exit due to the
option ERR_EXIT will cause the shell to exit without waiting. Examples
of such asynchronous jobs are process substitution, see the section
PROCESS SUBSTITUTION in the zshexpn(1) manual page, and the handler
processes for multios, see the section MULTIOS in the zshmisc(1) manual
page.
next prev parent reply other threads:[~2019-07-29 15:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 11:04 Vincent Lefevre
2019-06-28 11:38 ` Vincent Lefevre
2019-06-29 16:17 ` Bart Schaefer
2019-07-06 23:55 ` Vincent Lefevre
2019-07-07 4:54 ` Bart Schaefer
2019-07-09 10:08 ` Vincent Lefevre
2019-07-09 10:54 ` Vincent Lefevre
2019-07-29 15:23 ` Vincent Lefevre
2019-07-29 15:54 ` Bart Schaefer [this message]
2019-07-29 20:48 ` Vincent Lefevre
2019-07-30 0:00 ` Bart Schaefer
2019-07-30 0:17 ` Vincent Lefevre
[not found] <20190628110430.GA13790__36317.6205357135$1561719956$gmane$org@zira.vinc17.org>
2019-06-28 18:41 ` Stephane Chazelas
2019-06-29 1:24 ` Vincent Lefevre
2019-06-29 15:30 ` Stephane Chazelas
2019-07-06 23:49 ` Vincent Lefevre
2019-07-29 23:08 ` Vincent Lefevre
2019-07-29 23:15 ` Vincent Lefevre
2019-07-29 23:42 ` Bart Schaefer
2019-07-30 0:40 ` Vincent Lefevre
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH+w=7a8aBsxdF1Otwvbm7eWe=BC2T0Ny87j+sY5QW7oXM=j_Q@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).