From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 820 invoked from network); 20 Oct 2000 07:56:04 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 20 Oct 2000 07:56:04 -0000 Received: (qmail 19595 invoked by alias); 20 Oct 2000 07:56:00 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 13047 Received: (qmail 19588 invoked from network); 20 Oct 2000 07:55:59 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de) From: "Andrej Borsenkow" To: Subject: RE: PATCH: ptyread eating CPU on Cygwin Date: Fri, 20 Oct 2000 11:55:53 +0400 Message-ID: <000d01c03a6b$2b8b6040$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: <200010200701.JAA01039@beta.informatik.hu-berlin.de> > > I even think about removin non-blocking ptys altogether -- and add > allow `zpty -w' with a timeout, too. Hm, the print builtin can't be > given a timeout, but the -t option for it is still unused. Should we? > zpty -w with timeout is right stuff. I think, we better leave non-blocking mode in - may be, there are some exotic cases when it may be useful. And in case of non-bocking read with pattern add return code 'did not match' (it cannot happen in case of blocking read without either EOF or timeout). But we need better semantic for zpty -r then. Without pattern, how much exactly should it read? A character at a time? A line? -andrej