From: Vincent Lefevre <vincent@vinc17.net>
To: zsh-users@zsh.org
Subject: Re: Option PRINT_EXIT_VALUE doesn't always work as expected
Date: Thu, 19 Aug 2010 16:25:58 +0200 [thread overview]
Message-ID: <20100819142558.GA25968@prunille.vinc17.org> (raw)
In-Reply-To: <20100731225345.2cad292e@pws-pc>
On 2010-07-31 22:53:45 +0100, Peter Stephenson wrote:
> On Fri, 30 Jul 2010 15:02:04 +0200
> Vincent Lefevre <vincent@vinc17.net> wrote:
> > Also, if tst is a script that does "exit 141", I get as expected:
> >
> > ypig% ./tst | head -n 1
> > zsh: exit 141 ./tst |
> > zsh: done head -n 1
> > ypig% echo $pipestatus
> > 141 0
> >
> > but if tst does "kill -PIPE $$", I get:
> >
> > ypig% ./tst | head -n 1
> > ypig% echo $pipestatus
> > 141 0
>
> The fact that the signal number + 128 is added to get the status isn't
> currently taken account at that point. It should presumably be
> transparent.
Actually I'm wondering whether this is a good idea. I often do
"program | less" and I often quit "less" before looking at the
end of the output, so that one gets a typical broken pipe, with
a useless "zsh: broken pipe" message.
Perhaps there should be an option (useful only with PRINT_EXIT_VALUE)
to ignore the broken pipe specifically. And/or an option so that
exit information is output only when the last command of a pipeline
exits with a non-zero status.
I'm also wondering whether I still need PRINT_EXIT_VALUE since I now
print the exit status (or signal) in my prompt.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
prev parent reply other threads:[~2010-08-19 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 13:02 Vincent Lefevre
2010-07-31 21:53 ` Peter Stephenson
2010-08-19 14:25 ` Vincent Lefevre [this message]
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=20100819142558.GA25968@prunille.vinc17.org \
--to=vincent@vinc17.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).