This is the mail archive of the
mailing list for the Cygwin project.
Re: input delay issues
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 2 Apr 2012 16:56:07 -0400
- Subject: Re: input delay issues
- References: <4F7A022B.firstname.lastname@example.org>
- Reply-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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple