zsh-workers
 help / color / mirror / code / Atom feed
From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Philippe Altherr" <philippe.altherr@gmail.com>,
	"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 22:32:00 -0500	[thread overview]
Message-ID: <79df64ce-17e7-45e8-833f-f975c97f7797@app.fastmail.com> (raw)
In-Reply-To: <CAGdYchtw5PDJs5ekU0ZqwB3gzoMJaLQ2j-dJ7LomrMALDwo-Dg@mail.gmail.com>

On Sat, Dec 10, 2022, at 8:49 AM, Philippe Altherr wrote:

> Afaik, Zsh intends to be compatible with the POSIX "set -e" 
> specification 

On what are you basing this assertion?

> If that is indeed the case, then all the patches can be seen as bug 
> fixes.

I don't agree.  The documentation barely says anything about any
of the behaviors you modified, and zsh is not a POSIX-compatible
shell, so it's entirely reasonable for users to have accepted the
previous behavior as intentional.

> So no Zsh doc changes are required (or at least not because of 
> these patches).

This is only incidentally true.  The documentation omits many details
about ERR_EXIT's special cases, so your changes largely fall between
the lines (so to speak).

-- 
vq


  reply	other threads:[~2022-12-11  3:32 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
2022-12-11  3:32         ` Lawrence Velázquez [this message]
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=79df64ce-17e7-45e8-833f-f975c97f7797@app.fastmail.com \
    --to=larryv@zsh.org \
    --cc=d.s@daniel.shahaf.name \
    --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).