Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16337 > unrolled thread
| Started by | Eli Schwartz <eschwartz@archlinux.org> |
|---|---|
| First post | 2020-06-01 09:16 -0400 |
| Last post | 2020-06-01 09:16 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: bash errexit shell option does not work in some cases. Eli Schwartz <eschwartz@archlinux.org> - 2020-06-01 09:16 -0400
| From | Eli Schwartz <eschwartz@archlinux.org> |
|---|---|
| Date | 2020-06-01 09:16 -0400 |
| Subject | Re: bash errexit shell option does not work in some cases. |
| Message-ID | <mailman.897.1591017393.2541.bug-bash@gnu.org> |
[Multipart message — attachments visible in raw view] — view raw
On 6/1/20 6:28 AM, Robert Elz wrote: > Date: Sun, 31 May 2020 22:46:48 -0400 > From: Eli Schwartz <eschwartz@archlinux.org> > Message-ID: <5a7df0ba-3ad1-1f35-1107-09fdd5950359@archlinux.org> > > While I generally agree with ... > > | Don't use errexit > > but not really with: > > | it does not mean what you think it does. > > (it does mean what I think it means ...) (I think shell developers are exempt from this generalization. :p) > in this case: > > | You're merely the latest person to discover that this applies to you: > | http://mywiki.wooledge.org/BashFAQ/105 > > doesn't really apply - the cases reported are simply bugs in bash, > a shell implementing -e correctly should exit as it was expected to. > > This all results from earlier posix specs where -e and simple commands > were linked - the wording has been improved (still short of perfect) > and simple commands are no longer relevant (other than that exit status > generally originates with the result from a simple command). As I am a poor user, I could not figure out whether the grammar allowed or forbade this this result. So this is actually that unbelievable of unbelievables, a script which is broken because of set -e and it's actually because set -e has a bug? Thanks for clarifying. -- Eli Schwartz Arch Linux Bug Wrangler and Trusted User
Back to top | Article view | gnu.bash.bug
csiph-web