X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4C3F02F7.5040301@hones.org.uk> Date: Thu, 15 Jul 2010 13:45:43 +0100 From: Cliff Hones User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Problem with select() on console References: <4C3E59E3.4050003@hones.org.uk> <20100715054952.GB10561@trixie.casa.cgf.cx> <4C3EF7BB.4040204@hones.org.uk> In-Reply-To: <4C3EF7BB.4040204@hones.org.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: -0.0 (/) (dominator.watchfront.net.uk) X-Spam-Report: dominator.watchfront.net.uk has scanned this email for spam. Results:- T_RP_MATCHES_RCVD=-0.01 (total -0.0, current threshold 4.0) X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Cliff Hones wrote: > I must look at the console source... And now I have, and I see that fhandler_console does its own line editing, so is perfectly aware of the input line state. So blocking as soon as any key is typed seems a shortcoming of cygwin, not windows? I see there may be a difficulty with storing incomplete lines, or with synchronizing processing of new console events seen by different cygwin threads/processes, and it may be deemed unworthwhile (especially as it doesn't seem to be a frequently raised question), but to it seems doable. -- Cliff -- 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