zsh-workers
 help / color / mirror / code / Atom feed
From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Daniel Shahaf" <d.s@daniel.shahaf.name>, zsh-workers@zsh.org
Cc: "Philippe Altherr" <philippe.altherr@gmail.com>
Subject: Re: [PATCH] NEWS item about the ERR_EXIT fixes
Date: Sat, 10 Dec 2022 22:23:47 -0500	[thread overview]
Message-ID: <f1b2563c-d562-46d1-a6cc-c4e975219278@app.fastmail.com> (raw)
In-Reply-To: <20221210113214.GV27622@tarpaulin.shahaf.local2>

On Sat, Dec 10, 2022, at 6:32 AM, Daniel Shahaf wrote:
> Shouldn't this define the term "suppresses"?  It's not used in
> the documentation of ERR_EXIT.
>
> [...]
>
> Shouldn't this define the term "propagates"?  It's not used in
> the documentation of ERR_EXIT.
>
> [...]
>
> Doc/Zsh/ can be updated as well,
> if needed (this is discussed on the 51089 thread).

The documentation addresses some but not all of the special cases
and weirdness of ERR_EXIT.  I figured that fixing that was out of
scope here, but this might actually be a good time to remedy the
omissions.  That way NEWS and README don't have to waste a bunch
of space explaining aspects of ERR_EXIT that should be in the
documentation anyway.

-- 
vq


      parent reply	other threads:[~2022-12-11  3:24 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
2022-12-13  0:33           ` Philippe Altherr
2022-12-13  3:05             ` Daniel Shahaf
2022-12-11  3:23       ` Lawrence Velázquez [this message]

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=f1b2563c-d562-46d1-a6cc-c4e975219278@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).