From: Philippe Troin <phil@fifi.org>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Is it possible to capture stdout and stderr to separate variables in Zsh?
Date: Wed, 07 Mar 2012 11:37:03 -0800 [thread overview]
Message-ID: <1331149023.9089.8.camel@air.fifi.org> (raw)
In-Reply-To: <120306230111.ZM11639@torch.brasslantern.com>
On Tue, 2012-03-06 at 23:01 -0800, Bart Schaefer wrote:
> On Mar 6, 9:16am, Philippe Troin wrote:
> }
> } On Tue, 2012-03-06 at 09:09 +0100, Nikolai Weibull wrote:
> } > Is it possible to capture stdout and stderr to separate variables in Zsh?
> }
> } All I can think of is:
> }
> } coproc cat &
> } pid=$!
> } stdout="$( ( print "printed on stdout"; print -u 2 "printer on stderr" ) 2>&p )"
> } sleep 1
> } kill "$pid"
> } stderr="$(cat <&p)"
> }
> } You'll notice the very ugly sleep+kill hack I had to use as I could not
> } find how you can close a coprocess's standard input cleanly. Removing
> } the sleep+kill makes the cat <&p hang forever.
>
> You need this: http://www.zsh.org/mla/users/2011/msg00095.html :-)
I didn't see anything in there that could suppress the sleep+kill.
> } A completely different solution could involve the tcp zsh module which
> } can multiplex many streams with tcp_expect. But that's probably too
> } involved for this problem.
>
> You might also be able to do something with the zsh/zselect module, but
> just use a temp file. That solution works in bash, too.
I like Nikolai's solution best, except that it's somewhat cryptic and it
munges NULs and trailing newlines.
outs=("${(@0):-"$({ out=$(x) } 2>&1; print $'\0'$out$'\0'$status)"}")
Phil.
next prev parent reply other threads:[~2012-03-07 19:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 8:09 Nikolai Weibull
2012-03-06 17:16 ` Philippe Troin
2012-03-07 7:01 ` Bart Schaefer
2012-03-07 9:26 ` Nikolai Weibull
2012-03-08 14:53 ` Bart Schaefer
2012-03-30 7:15 ` Nikolai Weibull
2012-03-30 14:49 ` Bart Schaefer
2012-09-10 6:16 ` Han Pingtian
2012-03-07 19:37 ` Philippe Troin [this message]
2012-03-08 4:56 ` Bart Schaefer
2012-09-01 11:59 ` Han Pingtian
2012-09-09 19:18 ` Bart Schaefer
2012-08-31 0:40 ` Paul Maisano
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=1331149023.9089.8.camel@air.fifi.org \
--to=phil@fifi.org \
--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).