zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Thomas Lauer <thomas.lauer@virgin.net>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: zsh function breaks after error
Date: Wed, 9 Feb 2022 12:16:24 -0800	[thread overview]
Message-ID: <CAH+w=7ZxtKCSCsmLqQovDGtPF-cbMi6um2JbVQhi7Zu8qOpZJQ@mail.gmail.com> (raw)
In-Reply-To: <e1u70ht8crjuu5l4f4saggu1rji626uns3@tlc.com>

On Wed, Feb 9, 2022 at 10:45 AM Thomas Lauer <thomas.lauer@virgin.net> wrote:
>
> Well... as I wrote in my OP: if I replace the rofi call with a tiny
> script that does precisely the same thing but *always* exits with error
> code 0, all works as it should. So I am pretty sure that rofi exiting
> with 1 is indeed the culprit here.

If you use your tiny script and replace "exit 0" with "exit $?" (so it
exits with the same status as rofi) does that still reproduce the
problem?

Incidentally, what's the $ZSH_PATCHLEVEL ?


  reply	other threads:[~2022-02-09 20:17 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 [this message]
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
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='CAH+w=7ZxtKCSCsmLqQovDGtPF-cbMi6um2JbVQhi7Zu8qOpZJQ@mail.gmail.com' \
    --to=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).