From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Peter Stephenson" <p.w.stephenson@ntlworld.com>
Cc: zsh-workers@zsh.org
Subject: Re: New problem with ERR_RETURN ?
Date: Thu, 08 Dec 2022 01:05:00 -0500 [thread overview]
Message-ID: <cb8df6b1-4ea6-454b-846e-c6f582ff3a86@app.fastmail.com> (raw)
In-Reply-To: <1536100214.2124060.1670432862096@mail.virginmedia.com>
On Wed, Dec 7, 2022, at 12:07 PM, Peter Stephenson wrote:
> @@ -1772,6 +1775,12 @@ function, code inside it is considered
> separately: it may force a return
> from tt(summit) (assuming the option remains set within tt(summit)),
> but
> not from the enclosing context. This behaviour is different from
> tt(ERR_EXIT) which is unaffected by function scope.
> +
> +It should also be noted that this option forces an immediate
> +return to the command prompt when the non-zero status occurs
> +in a sequence of commands typed on the command line. In other
> +words, the sequence of commands typed by the user may be
> +thought of as a function for this purpose.
> )
> pindex(EVAL_LINENO)
> pindex(NO_EVAL_LINENO)
Bikeshedding perhaps, but this sentence already exists just above:
This will trigger an exit at the outermost level of a
non-interactive script.
Maybe any new text should come right after this? That would keep
the explanations about how ERR_RETURN affects behavior at the top
level in one place.
--
vq
next prev parent reply other threads:[~2022-12-08 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 16:17 Bart Schaefer
2022-12-07 16:37 ` Peter Stephenson
2022-12-07 16:41 ` Philippe Altherr
2022-12-07 16:53 ` Peter Stephenson
2022-12-07 17:02 ` Bart Schaefer
2022-12-07 17:07 ` Peter Stephenson
2022-12-08 6:05 ` Lawrence Velázquez [this message]
2022-12-08 9:24 ` Peter Stephenson
2022-12-07 16:58 ` Bart Schaefer
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=cb8df6b1-4ea6-454b-846e-c6f582ff3a86@app.fastmail.com \
--to=larryv@zsh.org \
--cc=p.w.stephenson@ntlworld.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).