From: Bart Schaefer <schaefer@brasslantern.com>
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 20:56:59 -0800 [thread overview]
Message-ID: <120307205659.ZM13143@torch.brasslantern.com> (raw)
In-Reply-To: <1331149023.9089.8.camel@air.fifi.org>
On Mar 7, 11:37am, Philippe Troin wrote:
}
} > } coproc cat &
} > } pid=$!
} > } stdout="$( ( print "printed on stdout"; print -u 2 "printer on stderr" ) 2>&p )"
} > } sleep 1
} > } kill "$pid"
} > } stderr="$(cat <&p)"
} >
} > 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.
Look at the part subtitled "Where might I go wrong with coproc?" ... it
doesn't answer the whole problem, but it tells you how to cleanly close
the descriptors. The full solution is more like:
coproc cat &
exec {p}<&p # Copy the <&p descriptor
stdout="$( ( print "printed on stdout";
print -u 2 "printed on stderr") 2>&p )"
coproc exit # Close both <&p and >&p descriptors
stderr="$(cat <&$p)" # Read from copy descriptor
exec {p}<&- # Close the copy (optional)
I also dug this up: http://www.zsh.org/mla/workers/2000/msg03684.html
but that predates the fancy {p}<&p syntax.
} I like Nikolai's solution best, except that it's somewhat cryptic
Yeah, I may have some thoughts on that one, too.
next prev parent reply other threads:[~2012-03-08 4:57 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
2012-03-08 4:56 ` Bart Schaefer [this message]
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=120307205659.ZM13143@torch.brasslantern.com \
--to=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).