Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 1 May 2001 00:28:50 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: When will cygwin ever be stable? Message-ID: <20010501002850.B6940@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4.3.2.7.2.20010430105401.00eb8220@san-francisco.beasys.com> <3AEE2E6F.1044C4C6@ece.gatech.edu> <20010501000437.C5077@redhat.com> <3AEE3849.4C0CA25@ece.gatech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3AEE3849.4C0CA25@ece.gatech.edu>; from cwilson@ece.gatech.edu on Tue, May 01, 2001 at 12:15:05AM -0400 On Tue, May 01, 2001 at 12:15:05AM -0400, Charles S. Wilson wrote: >Christopher Faylor wrote: >> WHAT ^C issue? What are we talking about????? >> >> The only issue I'm aware of is being unable to stop a cygwin process if >> all of its standard input/output has been redirected. That was fixed >> a couple of days ago but it was hardly a new problem. > >That's the most recent appearance. Perhaps I'm misremembering, but I >had thought there were several "signal-handling" things that have >cropped up since January. CTRL-Z not suspending windows apps, CTRL-C >not able to interrupt a process (regardless of whether its I/O was >redirected), ... CTRL-Z was an issue. CTRL-Z is a very special animal as far as signals go. CTRL-C was not an issue, AFAIK. Regardless, the simple fix that was proposed a few days ago only solves one specific problem. The problem that was fixed has been in cygwin for quite a while. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple