From: Philippe Altherr <philippe.altherr@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH] NEWS item about the ERR_EXIT fixes
Date: Sat, 10 Dec 2022 14:49:56 +0100 [thread overview]
Message-ID: <CAGdYchtw5PDJs5ekU0ZqwB3gzoMJaLQ2j-dJ7LomrMALDwo-Dg@mail.gmail.com> (raw)
In-Reply-To: <20221210113214.GV27622@tarpaulin.shahaf.local2>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
Just a quick reply. I will prepare an updated patch that includes a short
description in NEWS (mainly an updated version of Lawrence's proposal) and
a longer one with examples in README. Once it's ready (probably only
tomorrow), I will check again here whether there are still questions not
yet answered by the updated patch.
Afaik, Zsh intends to be compatible with the POSIX "set -e" specification
<https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#set>.
If that is indeed the case, then all the patches can be seen as bug fixes.
So no Zsh doc changes are required (or at least not because of these
patches). The patches also only affect corner cases, which are quite a bit
more complicated than Daniel's examples. None of Daniel's examples are
affected; they all keep behaving the same way.
Philippe
[-- Attachment #2: Type: text/html, Size: 978 bytes --]
next prev parent reply other threads:[~2022-12-10 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 21:45 Philippe Altherr
2022-12-09 0:24 ` Bart Schaefer
2022-12-09 6:44 ` Lawrence Velázquez
2022-12-09 9:30 ` Philippe Altherr
2022-12-09 15:17 ` Mikael Magnusson
2022-12-10 7:23 ` Lawrence Velázquez
2022-12-10 7:35 ` Lawrence Velázquez
2022-12-10 11:32 ` Daniel Shahaf
2022-12-10 13:49 ` Philippe Altherr [this message]
2022-12-11 3:32 ` Lawrence Velázquez
2022-12-13 0:33 ` Philippe Altherr
2022-12-13 3:05 ` Daniel Shahaf
2022-12-11 3:23 ` Lawrence Velázquez
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=CAGdYchtw5PDJs5ekU0ZqwB3gzoMJaLQ2j-dJ7LomrMALDwo-Dg@mail.gmail.com \
--to=philippe.altherr@gmail.com \
--cc=d.s@daniel.shahaf.name \
--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).