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 X-WM-Posted-At: avacado.atomice.net; Wed, 22 May 02 22:53:30 +0100 Message-ID: <004101c201db$1c7f8520$0100a8c0@advent02> From: "Chris January" To: References: <003301c201c7$06f822c0$0100a8c0 AT advent02> <20020522202454 DOT GA20138 AT redhat DOT com> <001501c201d7$7d1f60c0$0100a8c0 AT advent02> <20020522213321 DOT GD19052 AT redhat DOT com> Subject: Re: Question about tty.cc Date: Wed, 22 May 2002 22:53:30 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > I wonder if, these days, there are any better ways of doing what this > code is doing. As I said, this code has been this way for years. > Increasing the timeout is going to have a negative effect on cygwin tty > programs. > > Wait. Hmm. This is only going to be a problem for programs run directly > via a windows console, right? It shouldn't be a problem for a child of > bash since it is inheriting the tty handle explicitly. > > So, a slowdown should only be in an initial cygwin process. Is this what > you're seeing? The problem occurs clicking on a shortcut in explorer - the console window takes a little while to open and sometimes it simply takes too long for the tty code to catch it. Chris -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/