From: Peter Stephenson <Peter.Stephenson@csr.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: $pipestatus and shell functions
Date: Mon, 11 Apr 2011 17:38:35 +0100 [thread overview]
Message-ID: <20110411173835.385fba1f@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <BANLkTimLwZCd462OWiNCt9Qb6hJAptmJ7Q@mail.gmail.com>
On Mon, 11 Apr 2011 17:52:24 +0200
Jérémie Roquet <arkanosis@gmail.com> wrote:
> $ foo() { false | true }
> $ true | foo ; echo $pipestatus
> 1 0
> $ foo() { false | false }
> $ true | foo ; echo $pipestatus
> 1 1
> $ foo() { true | true | true }
> $ false | foo ; echo $pipestatus
> 0 0 0
>
> So $pipestatus is defeated by multiple pipelining…
>
> Is this by design?
I don't think this particular effect is deliberate. You're falling foul
of (i) a shell function looks like a job to the shell (ii) it appears
that function is being made the current job, so generates the pipe
status when it exits (the same happens if you use a { ... } expression
there, so that's not a workaround). However, there's some truly
horrible handling for job control in complicated cases like this (what
is supposed to get signals and what do you return to if you get one?) so
it's quite possible that those two contributing factors are themselves
deliberate. I'm not entirely convinced, though; it surprises me that
that the notion of the current job changes like that.
> If so, is there some not-so-complicated workaround
> to get the exit code of process A in “ A | B ” for any B (ie. even if
> B is itself a shell function with a pipe)?
Do you need B to be running in the current shell? If not,
A | ( B )
will work.
--
Peter Stephenson <pws@csr.com> Software Engineer
Tel: +44 (0)1223 692070 Cambridge Silicon Radio Limited
Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, UK
Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
next prev parent reply other threads:[~2011-04-11 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 15:52 Jérémie Roquet
2011-04-11 16:38 ` Peter Stephenson [this message]
2011-04-11 16:48 ` Peter Stephenson
2011-04-11 17:33 ` Jérémie Roquet
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=20110411173835.385fba1f@pwslap01u.europe.root.pri \
--to=peter.stephenson@csr.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).