Re: bash errexit shell option does not work in some cases.

From	Eli Schwartz <eschwartz@archlinux.org>
Newsgroups	gnu.bash.bug
Subject	Re: bash errexit shell option does not work in some cases.
Date	2020-06-08 10:44 -0400
Message-ID	<mailman.1443.1591627465.2541.bug-bash@gnu.org> (permalink)
References	(1 earlier) <3f403934d6b5d23ca58afc5146416c7@cweb006.nm.nfra.io> <1704.1591007300@jinx.noi.kre.to> <20200608112433.GW4133@eeg.ccf.org> <b080b864-da90-06ea-b257-42928e2d544b@case.edu> <25a558c6-d1bf-24be-21a9-aebe8fbea894@archlinux.org>

Show all headers | View raw

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

On 6/8/20 10:02 AM, Chet Ramey wrote:
> On 6/8/20 7:24 AM, Greg Wooledge wrote:
>> This is part of the set -e nightmare, which is what we keep trying to
>> get you (and everyone else) to understand.
> 
> Most of the issue with `set -e' is folks not understanding when it's
> not in effect.

Well, Greg does have a pretty good point (which is a point I for one
prioritize in my decision process for "do I personally recommend the use
of set -e") in that another part of the issue is its doing different
things across point releases of a shell.

And that's not counting the times when the issue is people not
understanding when it *is* in effect.

Or people who know exactly when it is and isn't in effect, and have no
issue, but decline to use it because the precise nature of "when it is
and isn't in effect" decreases the usefulness of it sufficiently to make
them decide they're better off implementing error checking a different
way... and *that* is, I think, what Greg is pointing out.

-- 
Eli Schwartz
Arch Linux Bug Wrangler and Trusted User

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

Thread

Re: bash errexit shell option does not work in some cases. Eli Schwartz <eschwartz@archlinux.org> - 2020-06-08 10:44 -0400

csiph-web