From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25106 invoked from network); 21 Jul 1999 12:05:47 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 21 Jul 1999 12:05:47 -0000 Received: (qmail 1475 invoked by alias); 21 Jul 1999 12:05:35 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 7236 Received: (qmail 1466 invoked from network); 21 Jul 1999 12:05:30 -0000 Message-Id: <9907211134.AA36022@ibmth.df.unipi.it> To: zsh-workers@sunsite.auc.dk Subject: Re: coprocesses In-Reply-To: "Sven Wischnowsky"'s message of "Wed, 21 Jul 1999 12:28:32 DFT." <199907211028.MAA02785@beta.informatik.hu-berlin.de> Date: Wed, 21 Jul 1999 13:34:32 +0200 From: Peter Stephenson Sven Wischnowsky wrote: > Peter Stephenson wrote: > > coproc cat > > print foo >&p > > read line <&p > > > > simply hung > > If that's on your AIX box, this would probably show that it really has > some problems with IO, because it works fine for me It works in Zeuthen, too, so maybe it's just the climate, or unexpected buffering. Using print -p/read -p in ksh seems to hang it, too. I'm going to have to stop using computers, it's too confusing. > (without the cat > terminating after the first `print' which, as I think, is correct). It depends how you think of it. ksh doesn't with print -p. -- Peter Stephenson Tel: +39 050 844536 WWW: http://www.ifh.de/~pws/ Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy