From: Thomas Lauer <thomas.lauer@virgin.net>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: zsh function breaks after error
Date: Wed, 09 Feb 2022 18:45:17 +0000 [thread overview]
Message-ID: <e1u70ht8crjuu5l4f4saggu1rji626uns3@tlc.com> (raw)
In-Reply-To: <CAH+w=7YwMwbo-HDOceDKX=oU4LQw9xg2Y_d9fWO9zk5hPummcA@mail.gmail.com>
> On Tue, Feb 8, 2022 at 9:16 AM Thomas Lauer <thomas.lauer@virgin.net> wrote:
> >
> > The trouble starts when rofi is terminated
> > not via selecting one of the shown directories (exit value 0) but with
> > Esc/Ctrl-G (exit value 1).
> >
> > In this case the function just breaks
>
> Are you sure the exit status is 1?
Yes.
> Could instead for example the grep
> be receiving a SIGPIPE because rofi stopped reading too soon?
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.
next prev parent reply other threads:[~2022-02-09 18:46 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 [this message]
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
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=e1u70ht8crjuu5l4f4saggu1rji626uns3@tlc.com \
--to=thomas.lauer@virgin.net \
--cc=schaefer@brasslantern.com \
--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).