From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Philippe Altherr <philippe.altherr@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: ERR_RETURN doc
Date: Sat, 10 Dec 2022 11:33:55 +0000 [thread overview]
Message-ID: <20221210113355.GW27622@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <CAGdYcht2a6oDePU_ba1Y7TZuWmWY9ELtzq7KX8jjEfuz=Zi3SQ@mail.gmail.com>
Philippe Altherr wrote on Thu, Dec 01, 2022 at 20:30:22 +0100:
> Yep, that remains correct. Same for ERR_EXIT.
>
> Most(/All?) of the patches address cases where the implementation wasn't
> following the specification.
>
Shouldn't docs of ERR_EXIT explicitly mention that «! true» does not
cause an exit?
> The patch about the always statement makes it behave like compound
> statements. Since the always statement isn't part of POSIX, this could be
> seen either as a bug fix or a spec change (but rather of the always
> statement than of ERR_EXIT).
>
> Philippe
>
>
> On Thu, Dec 1, 2022 at 5:30 PM Bart Schaefer <schaefer@brasslantern.com>
> wrote:
>
> > On Thu, Dec 1, 2022 at 6:42 AM Philippe Altherr
> > <philippe.altherr@gmail.com> wrote:
> > >
> > > https://zsh.sourceforge.io/Doc/Release/Options.html#index-ERRRETURN.
> >
> > Will that doc remain correct with respect to what it says about
> > ERR_EXIT after recent patches are considered?
> >
> > (Still on my TODO list, have been busier than I expected so far this week.)
> >
next prev parent reply other threads:[~2022-12-10 11:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f29162cd-28d1-85ed-6a3c-9bec1fb2e13a@eastlink.ca>
[not found] ` <CAA-Ti-hhbwZD3-aeMvy_tm5f7SKHw7XN4muJn8ymez1q7rAE_A@mail.gmail.com>
[not found] ` <CAN=4vMpCUNgKYgSR+4rmREpA25v_sLHYcS4nfTk8EQ_0Cg5yyw@mail.gmail.com>
[not found] ` <5d0c4e22-80b0-2fd2-ee75-6902da52d121@eastlink.ca>
[not found] ` <CAH+w=7aeERdOcpPzTmKVQFK7HLduh2s1J9VFzumCh6W0SJFqpg@mail.gmail.com>
[not found] ` <57e8e248-bb1a-663a-8557-e3fc13f671d4@eastlink.ca>
[not found] ` <CAH+w=7aW9meLuEKSGsKiZMXoAd7KBc9fgakXZnB_t2iphq=BPQ@mail.gmail.com>
[not found] ` <e35c2f14-abda-93d7-bf2c-6823d6d3215d@eastlink.ca>
[not found] ` <CAN=4vMrZzxYVjc63DwU=Scks39FhzmK+E57XerOwusmd64QOjw@mail.gmail.com>
[not found] ` <c2f348d1-8982-d4a4-2c78-a0dd67319b8c@eastlink.ca>
[not found] ` <CAGdYchv9T6ByD7meADqWzdJwAF2SG2YXhasT0=+AQvV+08ZRrA@mail.gmail.com>
2022-12-01 16:30 ` Bart Schaefer
2022-12-01 19:30 ` Philippe Altherr
2022-12-01 20:05 ` Bart Schaefer
2022-12-01 22:52 ` Philippe Altherr
2022-12-10 11:33 ` Daniel Shahaf [this message]
2022-12-10 14:06 ` Philippe Altherr
2022-12-11 1:24 ` Bart Schaefer
2022-12-12 23:35 ` Philippe Altherr
2022-12-05 23:48 ` one time in 20 error Oliver Kiddle
2022-12-06 0:13 ` Bart Schaefer
2022-12-06 13:21 ` Roman Perepelitsa
2022-12-10 1:04 ` Oliver Kiddle
2022-12-10 9:23 ` Roman Perepelitsa
2022-12-15 1:32 ` Oliver Kiddle
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=20221210113355.GW27622@tarpaulin.shahaf.local2 \
--to=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).