Re: New problem with ERR_RETURN ?

[Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>]

> On 07/12/2022 17:02 Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> On Wed, Dec 7, 2022 at 8:55 AM Peter Stephenson
> <p.w.stephenson@xxxxxxxxxxxx> wrote:
> >
> > +
> > +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 script for this purpose.
> 
> Um, no, it doesn't return to the prompt, it kills the shell.

Yes, that would presumably require testing with a different
option, wouldn't it?

diff --git a/Doc/Zsh/options.yo b/Doc/Zsh/options.yo
index 445052617..b2213eb44 100644
--- a/Doc/Zsh/options.yo
+++ b/Doc/Zsh/options.yo
@@ -1744,6 +1744,9 @@ Exiting due to tt(ERR_EXIT) has certain interactions with asynchronous
 jobs noted in
 ifzman(the section JOBS in zmanref(zshmisc))\
 ifnzman(noderef(Jobs & Signals)).
+
+Note this behaviour is not disabled in interactive shells ---
+a non-zero status on the command line causes the shell to exit.
 )
 pindex(ERR_RETURN)
 pindex(NO_ERR_RETURN)
@@ -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)