Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <004101c201db$1c7f8520$0100a8c0@advent02>
From: "Chris January" <chris@atomice.net>
To: <cygwin@cygwin.com>
References: <003301c201c7$06f822c0$0100a8c0@advent02> <20020522202454.GA20138@redhat.com> <001501c201d7$7d1f60c0$0100a8c0@advent02> <20020522213321.GD19052@redhat.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

> 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/