From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-users@sunsite.auc.dk
Subject: Re: coproc tutorial (Re: questions)
Date: Mon, 4 Oct 1999 18:42:32 +0000 [thread overview]
Message-ID: <991004184232.ZM3484@candle.brasslantern.com> (raw)
In-Reply-To: <199910041610.MAA20728@betelgeuse.ccs.neu.edu>
On Oct 4, 12:10pm, Jay Sekora wrote:
> Subject: Re: coproc tutorial (Re: questions)
> It seems a little bit non-orthoganal that you can only have one
> coprocess.
It's not the case that there can be only one coprocess. The restriction
is that there can be only one pair of file descriptors referred to by the
special "p" name, and closing them frequently has the effect of stopping
the coprocess; but if you've copied those descriptors elsewhere you can
still use the copies to communicate with the process.
E.g.
coproc tr a-z A-Z
exec 5>&p ;: descriptor 5 is now the input of tr
exec 6<&p ;: descriptor 6 is now the output of tr
coproc sed s/DOG/CAT/ 5>&-
exec 7>&p ;: descriptor 7 is now the input of sed
exec 8<&p ;: descriptor 8 is now the output of sed
coproc exit ;: close p
cat <&6 >&7 5>&- 7>&- & : tr is now connected to sed
exec 6<&- 7>&- ;: close shell copies of descriptors
echo dog >&5 ;: send tr some input
exec 5>&- ;: close 5 so tr will exit
cat <&8 ;: should print CAT
There are some oddities here ... first, note how I had to explicitly close
descriptor 5 in the second coproc, and 5 and 7 in the backgrounded "cat".
That's because they don't have the close-on-exec flag set; if I don't close
them, "tr" and "sed" never see end-of-file. I'm not sure whether that is
correct behavior or not.
Second, this doesn't actually work in 3.0.6, because zsh "leaks" copies of
descriptors 5 and 7 as descriptors 13 and 14 ("strace" is your friend), so
even after all my careful descriptor-closing I still can't get "tr" to see
EOF. It works in 3.1.6, so I may have a look at fixing it in 3.0.
next prev parent reply other threads:[~1999-10-04 18:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-04 16:10 Jay Sekora
1999-10-04 18:42 ` Bart Schaefer [this message]
1999-10-05 1:23 ` Elusive coproc bug (Re: coproc tutorial (Re: questions)) Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
1999-10-12 6:53 coproc tutorial (Re: questions) Sven Wischnowsky
1999-10-12 8:42 ` Thomas Köhler
1999-10-11 10:45 Sven Wischnowsky
1999-10-11 12:55 ` Thomas Köhler
1999-10-03 8:30 questions Chris Hansen
1999-10-03 11:10 ` questions Stefan Berglund
1999-10-03 18:45 ` coproc tutorial (Re: questions) Bart Schaefer
1999-10-03 21:08 ` Chris Hansen
1999-10-04 2:01 ` coproc Chris Hansen
1999-10-04 4:41 ` coproc tutorial (Re: questions) Bart Schaefer
1999-10-04 5:21 ` Chris Hansen
1999-10-04 6:22 ` 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=991004184232.ZM3484@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-users@sunsite.auc.dk \
/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).