X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Sun, 30 May 2010 02:00:43 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: 1.7.5 cannot bg mintty Message-ID: <20100530060043.GC3251@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4BF1B307.20507@ntlworld.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Sat, May 29, 2010 at 11:32:23PM +0100, Andy Koppe wrote: >(There's also another issue with the ^Z not taking effect immediately >due to signal handling being disabled while mintty waits for Windows >events, but that would require some fairly major restructuring to fix, >so leaving that for later. Looking at rxvt, the right thing to do is a >select() on the pty device and /dev/windows instead of mintty's >current approach using multiple threads and >MsgWaitForMultipleObjects.) ...assuming that still works. I wonder if anyone has used that interface in the last few years. But, then, I dunno. Maybe rxvt uses it. 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