X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.4 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Message-ID: <4F7B501C.5020900@towo.net> Date: Tue, 03 Apr 2012 21:31:40 +0200 From: Thomas Wolff User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: input delay issues References: <4F7A022B DOT 6040702 AT towo DOT net> <20120402205607 DOT GD9912 AT ednor DOT casa DOT cgf DOT cx> In-Reply-To: <20120402205607.GD9912@ednor.casa.cgf.cx> X-TagToolbar-Keys: D20120403213140009 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Am 02.04.2012 22:56, schrieb Christopher Faylor: > 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. OK, so there is a clear background explaining the console behavior; however, I described it only for completeness and to compare, the actual problem is with mintty/xterm/urxvt: Input which is available is not being detected - this is likely to be a problem with select() or O_NONBLOCKed read() (whichever bash uses) or both. Thomas -- 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