Re: 'foo > >(bar)' doesn't set $! for external foo not invoked via 'command'

From	Rusty Bird <rustybird@net-c.com>
Newsgroups	gnu.bash.bug
Subject	Re: 'foo > >(bar)' doesn't set $! for external foo not invoked via 'command'
Date	2020-07-20 14:11 +0000
Message-ID	<mailman.228.1595254290.24492.bug-bash@gnu.org> (permalink)
References	<20200719204836.GA1184@mutt> <CAH7i3Lqre0SoX_nJaMis=g7T_+X1LtrsPWJiJCjRCrHT1Y4_Jw@mail.gmail.com> <1659625e-267d-402e-c199-0772820fed79@case.edu> <20200720141119.GA2767@mutt>

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Chet Ramey:
> >> Description:
> >>         $! isn't set to the PID of 'bar' for
> >>
> >>                 foo > >(bar)
> >>
> >>         if 'foo' is an external program (as opposed to a builtin or
> >>         function) - unless it's invoked via 'command'.
> 
> Redirections are performed in the subshell created to execute `foo', so the
> process substitution is invoked there and can't affect the parent's $!.

I guess my question is: Would it not make sense to always perform the
redirection before the subshell is created?

OTOH, looks like it's trivial to work around the issue by using
'{ foo; } > >(bar)'.

Rusty

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: 'foo > >(bar)' doesn't set $! for external foo not invoked via 'command' Rusty Bird <rustybird@net-c.com> - 2020-07-20 14:11 +0000

csiph-web