From: Sweth Chandramouli <sweth@astaroth.nit.gwu.edu>
To: zsh-users@math.gatech.edu
Subject: Re: Re: exit value of intermediate program in pipe
Date: Sun, 3 May 1998 18:15:09 -0400 [thread overview]
Message-ID: <19980503181509.09250@astaroth.nit.gwu.edu> (raw)
In-Reply-To: <980503023014.ZM31001@candle.brasslantern.com>
On Sun, May 03, 1998 at 02:30:14AM -0700, Bart Schaefer wrote:
> That just means redirect both stdout and stderr as the pipe input. It is
> a csh-ism, and not equivalent to the ksh syntax. See the FAQ. (I think
> that means that you want the "coproc" builtin and <&p and >&p redirection
> for setting up a "two-way pipe.")
man, if i could just learn to rtfm... i saw that section a while
ago in the man page, but since it was under "simple commands", i just
skimmed it and moved on.
even reading it carefully, though, i'm still not sure what the
coproc syntax is. to recreate the function we're discussing with a two-way
pipe (which would background one process so that the exit statuses could
be separated), in ksh i would do
{
grep -v bar |&
print -p `/bin/blah ; exitstatus=$?`
read -p output
echo $output
return $exitstatus
}
or something like that. for zsh, would i just do
{
grep -v bar coproc |
>&p `/bin/blah ; exitstatus=$?`
<&p output ; echo $output
return $exitstatus
}
?
(i'm not checking mail on a machine that i could test this
on, or i would just go ahead and do so.)
what zsh really needs is something like the hawksbill book from
oreilly for ksh, that gives a lot of examples and compares it to other
shells; i'm sure that half of my failures at zsh scripting come from
trying to use ksh-isms that i assume are implemented.
-- sweth.
--
"Countin' on a remedy I've counted on before
Goin' with a cure that's never failed me
What you call the disease
I call the remedy" -- The Mighty Mighty Bosstones
next prev parent reply other threads:[~1998-05-03 22:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-02 22:24 Steve Talley
1998-05-03 0:50 ` Sweth Chandramouli
1998-05-03 1:38 ` Timothy J Luoma
1998-05-03 2:08 ` Bart Schaefer
1998-05-03 6:17 ` Sweth Chandramouli
1998-05-03 9:30 ` Bart Schaefer
1998-05-03 22:15 ` Sweth Chandramouli [this message]
1998-05-04 1:35 ` Bart Schaefer
1998-05-04 4:54 ` Sweth Chandramouli
1998-05-04 9:43 ` Bernd Eggink
1998-05-04 11:42 ` Bart Schaefer
1998-05-04 12:03 ` Bernd Eggink
1998-05-04 15:59 ` Bart Schaefer
1998-05-05 11:39 ` Bernd Eggink
1998-05-05 17:03 ` zsh vs. ksh coproc redirection semantics Bart Schaefer
1998-05-06 10:47 ` Bernd Eggink
1998-05-06 16:00 ` Bart Schaefer
1998-05-07 7:17 ` Zoltan Hidvegi
1998-05-07 8:34 ` Andrew Main
1998-05-07 9:26 ` Bart Schaefer
1998-05-07 9:34 ` Andrew Main
1998-05-07 17:02 ` Zoltan Hidvegi
1998-05-07 9:18 ` Bart Schaefer
1998-05-07 17:10 ` Zoltan Hidvegi
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=19980503181509.09250@astaroth.nit.gwu.edu \
--to=sweth@astaroth.nit.gwu.edu \
--cc=zsh-users@math.gatech.edu \
/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).