From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh-workers@zsh.org
Subject: $pipestatus broken?
Date: Sat, 10 Dec 2011 13:24:30 +0100 [thread overview]
Message-ID: <87borgzkap.fsf@ft.bewatermyfriend.org> (raw)
Hey list,
I've been playing with $pipestatus to solve the subversion1.7 issues in
vcs_info... Because it turns out, it can be a whole bunch of error
messages.
So the idea was not to match output but to look at subversion's exit
status. Since "svn info" is called in a pipe, I was using $pipestatus.
The result was mixed - literally. Sometimes, $pipestatus would contain
"0 0" and sometimes it would contain just a single "1".
Now I was extracting the offending code into a test script and then
later replaced the call to "svn info" by a call to fortune(1). The
result is the same.
Here's my test script:
[snip]
local -A svninfo
fortune |& while IFS=: read a b; do
svninfo[${a// /_}]="${b## #}"
done
ps=( "${pipestatus[@]}" )
rc=${ps[1]}
print "${ps[@]}"
[snap]
And here is a test-run:
[snip]
% repeat 10 zsh ./test
1
0 0
1
1
0 0
0 0
0 0
1
0 0
1
[snap]
Am I using `$pipestatus' the wrong way or is this a bug?
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next reply other threads:[~2011-12-10 12:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 12:24 Frank Terbeck [this message]
2011-12-10 12:48 ` Frank Terbeck
2011-12-10 14:58 ` Bart Schaefer
2011-12-11 14:37 ` Frank Terbeck
2011-12-23 10:49 ` Frank Terbeck
2011-12-23 21:31 ` Bart Schaefer
2011-12-23 22:11 ` Frank Terbeck
2011-12-24 9:32 ` Bart Schaefer
2011-12-24 9:59 ` Frank Terbeck
2011-12-24 18:23 ` Bart Schaefer
2011-12-24 18:46 ` Bart Schaefer
2011-12-24 17:37 ` Bart Schaefer
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=87borgzkap.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=zsh-workers@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).