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 11:14 +0000
Message-ID	<mailman.219.1595243701.24492.bug-bash@gnu.org> (permalink)
References	<20200719204836.GA1184@mutt> <CAH7i3Lqre0SoX_nJaMis=g7T_+X1LtrsPWJiJCjRCrHT1Y4_Jw@mail.gmail.com> <20200720102136.GA1147@mutt> <CAH7i3LrFCT7C4suAbKwCEf5izX5y4wSbtLH8L5bsP_EzzKiSOw@mail.gmail.com> <20200720111439.GA1634@mutt>

Show all headers | View raw

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

Oğuz:
> `>&"$out" is very ugly though, it'd be nice if `{var}' thing worked at
> the RHS of redirection operator, like `>&{var}`, which, on bash 5.0.11,
> ignores `&' -another bug?- and redirects stdout to a file named `{var}'.

Probably more backwards compatibility than a bug - '>&word' (with word
neither a number nor a dash) is an alternative form of '&>word':

https://www.gnu.org/software/bash/manual/html_node/Redirections.html#Redirecting-Standard-Output-and-Standard-Error

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 11:14 +0000

csiph-web