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


Groups > gnu.bash.bug > #16370

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

Path csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From Eli Schwartz <eschwartz@archlinux.org>
Newsgroups gnu.bash.bug
Subject Re: bash errexit shell option does not work in some cases.
Date Mon, 8 Jun 2020 10:44:09 -0400
Lines 74
Approved bug-bash@gnu.org
Message-ID <mailman.1443.1591627465.2541.bug-bash@gnu.org> (permalink)
References <5a7df0ba-3ad1-1f35-1107-09fdd5950359@archlinux.org> <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>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="x53mrB0aPRc4SpF5yg5myn11FXp15yI2O"
X-Trace usenet.stanford.edu 1591627466 31105 209.51.188.17 (8 Jun 2020 14:44:26 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=1591627452; bh=qvChb8gQwaJMYppMaz5/KDJEx1/pWSpNLQhRwplBKLQ=; h=Subject:To:References:From:Date:In-Reply-To; b=L2nL7RqXxKDhmNTqpGyfR7cU1LgD4SXOe6WXQavUXKr0VaMRzn5oe2WVxZVeIe7lX qKsi6YFxyCgbBAR3K6/sSmIjMrj/TDvm1DMhy74miZfA1nGwlNtyrtmi0fDX1w2Eke sYFkthpN7ti+M/thpLXLanhAP/6H+DoOhfeTG0uW9yJwUc2aMf3kCLlUeI/zdQJGfE BSzfIRSos1ZywIoHyWzRaKUXD8XwQfN6LivU6zIOnftRhkyG3y6vYO/T2DiSYXoity H/SG7dSY6ANuFh8KUVDgRTUEvIQ/kEYLkfyiafc8OIyXLtGhGB8vQ9wOCtdGFjgwUB 8FSYiDFP1/eIRPiAktiqkre0Tf+mMK2LZ2x52hSJVYPi/Jy8wHYifA+aLm2cfAd0p7 3Jd5MWmJU+Xns04cuSQfdOB+D9JWI80vFCkdNezTPfSON3e/MsJxJ7qv677FH12Wz+ szy1zCkO0lBtBM2w91m1hABQn9qCroO8VPcZTJ82GYdNLMc6AtUUI6IPQUiloIyE6z X23qxE8jztIorYTCI+4iLDTVYEpo1Lieqfcmq/74QaFB+/HeNnF+swjFXQ8GQR+e8Y lEFlR2wL08JMAAdX3kY5wPQehQS+N2az3ha6UDceAs09Bdo88r4Sr0QchJSpdANs9/ QalY3eaYDV8Qz5kKCrCw9OIo=
X-Clacks-Overhead GNU Terry Pratchett
User-Agent Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
In-Reply-To <b080b864-da90-06ea-b257-42928e2d544b@case.edu>
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/06/08 10:44:17
X-ACL-Warn Detected OS = Linux 2.2.x-3.x [generic] [fuzzy]
X-Spam_score_int -43
X-Spam_score -4.4
X-Spam_bar ----
X-Spam_report (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=0.001, 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.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN
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 <25a558c6-d1bf-24be-21a9-aebe8fbea894@archlinux.org>
X-Mailman-Original-References <5a7df0ba-3ad1-1f35-1107-09fdd5950359@archlinux.org> <3f403934d6b5d23ca58afc5146416c7@cweb006.nm.nfra.io> <1704.1591007300@jinx.noi.kre.to> <20200608112433.GW4133@eeg.ccf.org> <b080b864-da90-06ea-b257-42928e2d544b@case.edu>
Xref csiph.com gnu.bash.bug:16370

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