From: Bart Schaefer <schaefer@brasslantern.com>
To: Philippe Altherr <philippe.altherr@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: Inconsistent behavior of ERR_EXIT with conditionals
Date: Sun, 6 Nov 2022 12:45:29 -0800 [thread overview]
Message-ID: <CAH+w=7ZTSXUm6DLDk9k7z_V7YezKXJdcPi2uw1bTdmMjvTbkzg@mail.gmail.com> (raw)
In-Reply-To: <CAGdYchsbWpFRsxS2CRzhdDix-B9osY_isv9nuBjbvt4nDTEWLA@mail.gmail.com>
On Fri, Nov 4, 2022 at 9:39 AM Philippe Altherr
<philippe.altherr@gmail.com> wrote:
>
>> function fun1() {
>> { false && true }
>> }
>
> [...] since the expression "false && true" as a whole evaluates to a non-zero status and doesn't appear in a position where a condition is expected, I would assume that it should trigger an exit. [...] Apparanty Zsh simply ignores non-zero statuses of conditionals if they weren't generated by the last command.
In fact, comment in exec.c says:
* ERREXIT only forces the shell to exit if the last command in a &&
* or || fails. This is the case even if an earlier command is a
* shell function or other current shell structure, so we have to set
* noerrexit here if the sublist is not of type END.
But execcursh() unconditionally sets this_noerrexit = 1.
Does this act better? (Hopefully I don't need an attachment for this
one-liner):
diff --git a/Src/exec.c b/Src/exec.c
index c8bcf4ee5..d11f79d90 100644
--- a/Src/exec.c
+++ b/Src/exec.c
@@ -451,7 +451,7 @@ execcursh(Estate state, int do_exec)
cmdpop();
state->pc = end;
- this_noerrexit = 1;
+ this_noerrexit = (WC_SUBLIST_TYPE(*end) != WC_SUBLIST_END);
return lastval;
}
All extant tests still pass. Does not affect how fun3 and fun4
behave, so I suspect this fix may be needed elsewhere ... there are a
bunch of similar cases for multi-line shell constructs in Src/loop.c
next prev parent reply other threads:[~2022-11-06 20:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 16:37 Philippe Altherr
2022-11-06 20:45 ` Bart Schaefer [this message]
2022-11-07 3:50 ` Bart Schaefer
2022-11-07 5:35 ` [PATCH] " Bart Schaefer
2022-11-07 9:44 ` Peter Stephenson
2022-11-08 1:20 ` Bart Schaefer
2022-11-08 4:58 ` Philippe Altherr
2022-11-08 5:36 ` Bart Schaefer
2022-11-08 8:04 ` Lawrence Velázquez
2022-11-08 18:51 ` Philippe Altherr
2022-11-08 19:20 ` Lawrence Velázquez
2022-11-08 23:28 ` Bart Schaefer
2022-11-09 4:11 ` Philippe Altherr
2022-11-09 6:00 ` Bart Schaefer
2022-11-09 14:22 ` Philippe Altherr
2022-11-10 1:00 ` Bart Schaefer
2022-11-10 5:09 ` Bart Schaefer
2022-11-11 3:04 ` Philippe Altherr
2022-11-11 4:06 ` Lawrence Velázquez
2022-11-11 4:09 ` Eric Cook
2022-11-08 23:11 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH+w=7ZTSXUm6DLDk9k7z_V7YezKXJdcPi2uw1bTdmMjvTbkzg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=philippe.altherr@gmail.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).