Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 1 May 2005 20:18:57 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: "read" bug in Cygwin 1.5.16? Message-ID: <20050502001857.GA27373@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20050501235613 DOT 71599 DOT qmail AT web30205 DOT mail DOT mud DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050501235613.71599.qmail@web30205.mail.mud.yahoo.com> User-Agent: Mutt/1.5.8i On Sun, May 01, 2005 at 04:56:13PM -0700, Peter Farley wrote: >Hi all, > >I tried to forward this message to the main cygwin >list yesterday, but had a little trouble getting it >there, probably because I mentioned "xterm" in the >subject. I'm trying again in case this is NOT an "X" >problem but a base cygwin problem. > >I have attached the test program xtermbug.c instead >of pasting it inline. I hope that is OK for this >list. Thanks for the test program. There was a problem with setting VMIN == VTIME == 0 on ttys/ptys. I've just checked in a fix. It will be in today's snapshot, when it shows up: http://cygwin.com/snapshots/ . cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/