Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #16712

Re: process substitution error handling

Path csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From Eli Schwartz <eschwartz@archlinux.org>
Newsgroups gnu.bash.bug
Subject Re: process substitution error handling
Date Thu, 6 Aug 2020 09:57:12 -0400
Lines 70
Approved bug-bash@gnu.org
Message-ID <mailman.1002.1596722250.2739.bug-bash@gnu.org> (permalink)
References <20200420051508.GA2359844@zx2c4.com> <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>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Bpxyt5OGqgDfmyXBBkOYc7gpjgtJAJPOz"
X-Trace usenet.stanford.edu 1596722251 1078 209.51.188.17 (6 Aug 2020 13:57:31 GMT)
X-Complaints-To action@cs.stanford.edu
To bug-bash@gnu.org
Envelope-to bug-bash@gnu.org
X-Spam-BL-Results
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/simple; d=archlinux.org; s=orion; t=1596722237; bh=HhZys7KJGKuitVdF8j/ZS0D+7Pb2bvHap0PgA0KyiUU=; h=Subject:To:References:From:Date:In-Reply-To; b=uKD8kN5j9TC6i2o/PBXxmvusc/Nz177Wipx+hbuCmHxRHf/Q4ZSbDThx7NwXl4I3Q M5Phc6Cz95MtjdtfJ2b4vtcXJVIeaYB7ZTSjmWvT37eW541BWp2mwNo2uIErsILyOl IuqRRhOsU+FNVe69USuk+S0d7tL8FiTJtNyefbd+DV7laAThhXbeHHiLEp1JuWEy7X JGmOpQxcdlzmRiL5N/cCjJiqK784u8rmiIuairfCDQ63Tq5HzxWIpJcMXM2m58/QC/ inEyK1eUA7zaOZIfyBjf/gLgbPUBcV6aWNysyHyvzt8GTP9rk8teOwVph5lGaN0JG9 lk/UPM9nHXcWB7u6vXNo2TUNtaPh0B7eaACWm2X3yWagX6iC7Vj+BMwU3lyBqWAr0o ZwftJkthZ5OTAJhDWwr/C3oyO7l2Xgj1kZ2duMKa9Wej0G4wNyQgjy0UJKkqvj6yl7 k3Vl/Hd2f31UNbKP38/0A5Y+F4uIuKjkxgWyOAjfWI3Aq6oEyKws5EMsvj91cW2SKk II1sI7BVFoJsf+LEd5uBsd2O9Z6j0rXoGz6yC+YiFCI4N2s1DZtfVd4l0udEFyJcoE vW6qST4V8u2k2LVBSvmgWIlNI0jaHW51s9ZKMYfsM9YKZihfcnI4v0fgySI7T3Z9b/ rSbsABiaImewUrbD7awjEPpg=
X-Clacks-Overhead GNU Terry Pratchett
In-Reply-To <8a54cb1e-af78-f79f-6d73-6a235d707207@plushkava.net>
Received-SPF pass client-ip=88.198.91.70; envelope-from=eschwartz@archlinux.org; helo=orion.archlinux.org
X-detected-operating-system by eggs.gnu.org: First seen = 2020/08/06 09:57:23
X-ACL-Warn Detected OS = Linux 2.2.x-3.x [generic] [fuzzy]
X-Spam_score_int -53
X-Spam_score -5.4
X-Spam_bar -----
X-Spam_report (-5.4 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no
X-Spam_action no action
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.23
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <https://lists.gnu.org/archive/html/bug-bash>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID <b8fb1f5b-f8e4-b618-9c4e-7ccfa525f1f8@archlinux.org>
X-Mailman-Original-References <20200420051508.GA2359844@zx2c4.com> <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>
Xref csiph.com gnu.bash.bug:16712

Show key headers only | 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