Date: Mon, 2 Apr 2012 16:56:07 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: input delay issues
Message-ID: <20120402205607.GD9912@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4F7A022B DOT 6040702 AT towo DOT net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4F7A022B.6040702@towo.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Mon, Apr 02, 2012 at 09:46:51PM +0200, Thomas Wolff wrote:
>When input is typed-ahead, on a Unix or Linux systems it will be 
>buffered and used as soon as an application looks for it. Try this:
>- Run a slow command (e.g. sleep 5)
>- Type "abc" while running
>On Linux, "abc" will be echoed on the screen (disturbing output if there 
>is any). After the command terminates, the shell will look for input, 
>find "abc" and redisplay it properly on the command line.
>
>In the cygwin console, "abc" remains invisible while the command is 
>running, but it is redisplayed afterwards.
>In mintty, "abc" is echoed while typed-ahead, but is *not* read and 
>echoed by the shell after the command terminates. Only after you then 
>type another character, the whole command line is refreshed.

Yes.  The console is a windows device and that's the way that Windows
works.  Doing it anyway else would mean keeping a separate thread in
Cygwin and essentially adding back CYGWIN=tty, which we're obviously
not going to do.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple