From: Philippe Altherr <philippe.altherr@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: [PATCH] NEWS and README items about ERR_EXIT and ERR_RETURN changes
Date: Mon, 12 Dec 2022 17:06:09 +0100 [thread overview]
Message-ID: <CAGdYchv9TqhhQA6JrhYHd4cApTXVmAhiHzFFevLNHgiQgMAcgg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 84 bytes --]
Here is an updated patch to document the ERR_EXIT and ERR_RETURN changes.
Philippe
[-- Attachment #1.2: Type: text/html, Size: 146 bytes --]
[-- Attachment #2: patch-errexit-news-and-readme.txt --]
[-- Type: text/plain, Size: 3022 bytes --]
diff --git a/NEWS b/NEWS
index cdafd1ff5..e3a16a8bc 100644
--- a/NEWS
+++ b/NEWS
@@ -4,6 +4,14 @@ CHANGES FROM PREVIOUS VERSIONS OF ZSH
Note also the list of incompatibilities in the README file.
+Changes since 5.9
+-----------------
+
+The ERR_EXIT and ERR_RETURN options were refined to be more self-
+consistent and better aligned with the POSIX-2017 specification of
+`set -e`. For details on what exactly changed, see the list of
+incompatibilities in the README file.
+
Changes since 5.8.1
-------------------
diff --git a/README b/README
index 21142e17c..cb6d380aa 100644
--- a/README
+++ b/README
@@ -31,8 +31,56 @@ Zsh is a shell with lots of features. For a list of some of these, see the
file FEATURES, and for the latest changes see NEWS. For more
details, see the documentation.
-Incompatibilities since 5.8.1
------------------------------
+Incompatibilities since 5.9
+---------------------------
+
+The ERR_EXIT and ERR_RETURN options were refined to be more self-
+consistent and better aligned with the POSIX-2017 specification of
+`set -e`:
+
+ - Function calls or anonymous functions prefixed with `!` now never
+ trigger exit or return. Negated function calls or anonymous
+ functions used to trigger exit or return if ERR_EXIT or ERR_RETURN
+ was set and the function call or anonymous function returned a
+ zero exit status. Example:
+
+ setopt ERR_EXIT
+ f() { true }
+ ! f
+ echo "This is printed only since 5.10."
+
+ - The `always` command now ignores ERR_EXIT and ERR_RETURN, as other
+ complex commands do, if its exit status comes from a command
+ executed while the option is ignored. Example:
+
+ setopt ERR_EXIT
+ { false && true } always { echo "This was and still is printed." }
+ echo "This is printed only since 5.10."
+
+ - Function calls, anonymous functions, and the `eval`, `.`, and
+ `source` builtins now never ignore ERR_EXIT and ERR_RETURN on
+ their own. These commands used to ignore ERR_EXIT and ERR_RETURN
+ if their result came from a complex command (if, for, ...) whose
+ result came from a command executed while the option is
+ ignored. Example:
+
+ setopt ERR_EXIT
+ f() { if true; then false && true; fi }
+ f
+ echo "This is printed only prior to 5.10."
+
+ - The `&&` and `||` operators now always ignore ERR_RETURN in their
+ left operand. Until this version, the operators failed to ignored
+ ERR_RETURN in their left operand if they were executed as part of
+ a function call or an anonymous function that was itself executed
+ in a context where ERR_RETURN is ignored. Example:
+
+ setopt ERR_RETURN
+ f() { { false; echo "This is printed only since 5.10." } || true }
+ if f; then true; fi
+
+Incompatibilities between 5.8.1 and 5.9
+---------------------------------------
compinit: A "y" response to the "Ignore ... and continue?" prompt removes
insecure elements from the set of completion functions, where previously
next reply other threads:[~2022-12-12 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 16:06 Philippe Altherr [this message]
2022-12-12 16:28 ` Bart Schaefer
2022-12-12 23:14 ` Philippe Altherr
2022-12-13 3:20 ` Daniel Shahaf
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=CAGdYchv9TqhhQA6JrhYHd4cApTXVmAhiHzFFevLNHgiQgMAcgg@mail.gmail.com \
--to=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).