Re: process substitution error handling

From	Eli Schwartz <eschwartz@archlinux.org>
Newsgroups	gnu.bash.bug
Subject	Re: process substitution error handling
Date	2020-08-06 09:57 -0400
Message-ID	<mailman.1002.1596722250.2739.bug-bash@gnu.org> (permalink)
References	(1 earlier) <7496b183-2db3-6c03-6074-928adcd08f45@case.edu> <CAHmME9pzOY_0EJ69y9wt6r-Jh3frZpV8XdFC6zG5EOkZ99h-1A@mail.gmail.com> <e0a56db4-6444-5dde-3fdc-e3237e669cc6@archlinux.org> <8a54cb1e-af78-f79f-6d73-6a235d707207@plushkava.net> <b8fb1f5b-f8e4-b618-9c4e-7ccfa525f1f8@archlinux.org>

Show all headers | View raw

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

On 8/6/20 9:15 AM, kfm@plushkava.net wrote:
> You beat me to it. I was just about to suggest wait $! || exit. Indeed,
> I mentioned the same in a recent bug report against wireguard-tools.

So if I understand correctly, you reported the lack of wait $! || exit
in a script, and the script author instead responded by requesting a new
feature in bash that does the same thing, except after a random interval
during another command's execution?

> I concur. The scripts I looked at tended heavily towards error handling
> at a distance and were already subject to one or two amusing errexit
> pitfalls.

lol, I bet we could fix that by adding even more error handling at a
distance.

-- 
Eli Schwartz
Arch Linux Bug Wrangler and Trusted User

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

Thread

Re: process substitution error handling Eli Schwartz <eschwartz@archlinux.org> - 2020-08-06 09:57 -0400

csiph-web