From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Thomas Lauer <thomas.lauer@virgin.net>
Cc: Bart Schaefer <schaefer@brasslantern.com>, Zsh Users <zsh-users@zsh.org>
Subject: Re: zsh function breaks after error
Date: Thu, 10 Feb 2022 17:48:12 +0100 [thread overview]
Message-ID: <CAN=4vMrGe9oep-a-_5oqwnz0Fxyu5JtgbKfeNYUD=r0abnUicg@mail.gmail.com> (raw)
In-Reply-To: <0oea0h1nt14oll0drq3450vng70ro0ga43@tlc.com>
On Thu, Feb 10, 2022 at 5:20 PM Thomas Lauer <thomas.lauer@virgin.net> wrote:
>
> > From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
> >
> > What happens if you add `emulate -L zsh` (without quotes) at the top of the
> > function?
>
> Something good happens... it now works as I'd expect! Thanks, will have
> to read up about this!
This means that err_return option is set in your interactive zsh. This
is likely the result of invoking a function that has `setopt
err_return` in it without `emulate -L zsh` and without `setopt
local_options`. That function needs to be fixed. For example, you
could replace `setopt err_return` with `emulate -L zsh -o err_return`.
You can read about zsh options and `emulate -L` here:
https://zsh.sourceforge.io/Doc/Release/Options.html
Roman.
next prev parent reply other threads:[~2022-02-10 16:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 17:16 Thomas Lauer
2022-02-09 15:18 ` Bart Schaefer
2022-02-09 18:45 ` Thomas Lauer
2022-02-09 20:16 ` Bart Schaefer
2022-02-10 13:55 ` Thomas Lauer
2022-02-10 13:59 ` Roman Perepelitsa
2022-02-10 16:20 ` Thomas Lauer
2022-02-10 16:48 ` Roman Perepelitsa [this message]
2022-02-10 17:20 ` Thomas Lauer
2022-02-10 21:26 ` Ray Andrews
2022-02-10 21:45 ` Thomas Paulsen
2022-02-10 23:37 ` Daniel Shahaf
2022-02-11 15:07 ` Thomas Lauer
2022-02-11 14:58 ` Thomas Lauer
2022-02-11 15:59 ` Ray Andrews
2022-02-11 23:31 ` Bart Schaefer
2022-02-12 3:39 ` Ray Andrews
2022-02-22 3:58 ` Matthew Martin
2022-02-12 16:45 ` Thomas Lauer
2022-02-12 17:48 ` Ray Andrews
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='CAN=4vMrGe9oep-a-_5oqwnz0Fxyu5JtgbKfeNYUD=r0abnUicg@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=thomas.lauer@virgin.net \
--cc=zsh-users@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).