From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12931 invoked from network); 19 Oct 2000 14:25:43 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 19 Oct 2000 14:25:43 -0000 Received: (qmail 340 invoked by alias); 19 Oct 2000 14:25:38 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 13040 Received: (qmail 333 invoked from network); 19 Oct 2000 14:25:36 -0000 From: "Bart Schaefer" Message-Id: <1001019142431.ZM5250@candle.brasslantern.com> Date: Thu, 19 Oct 2000 14:24:31 +0000 In-Reply-To: <001501c039b1$d0ab8470$21c9ca95@mow.siemens.ru> Comments: In reply to "Andrej Borsenkow" "RE: PATCH: ptyread eating CPU on Cygwin" (Oct 19, 1:49pm) References: <001501c039b1$d0ab8470$21c9ca95@mow.siemens.ru> X-Mailer: Z-Mail (5.0.0 30July97) To: Subject: Re: PATCH: ptyread eating CPU on Cygwin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Oct 19, 1:49pm, Andrej Borsenkow wrote: } } So I suggest adding "read-with-timeout" possibilty, and making blocking read } default. It is also useful to distinguish between EOF and timeout with } different return code. This sounds right to me, too. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net