From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24620 invoked from network); 21 Jul 1999 10:28:48 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 21 Jul 1999 10:28:48 -0000 Received: (qmail 23855 invoked by alias); 21 Jul 1999 10:28:35 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 7234 Received: (qmail 23848 invoked from network); 21 Jul 1999 10:28:34 -0000 Date: Wed, 21 Jul 1999 12:28:32 +0200 (MET DST) Message-Id: <199907211028.MAA02785@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Peter Stephenson's message of Wed, 21 Jul 1999 11:34:19 +0200 Subject: Re: coprocesses Peter Stephenson wrote: > Are coprocesses still working? I got some strange results after trying > them in order to make the manual a bit clearer, but I don't use them often > enough to be sure. > > coproc cat > print foo >&p > read line <&p > > simply hung --- it did that without job control, too. In ksh it read the > expected line and the coprocess terminated. Trying to close the coprocess > input seemed to provoke some even stranger things. 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 (without the cat terminating after the first `print' which, as I think, is correct). Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de