Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 20 Jan 2002 17:36:06 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: interrupt failure after upgrading 1.3.6-6 to 1.3.7-1 Message-ID: <20020120223606.GA19154@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Sun, Jan 20, 2002 at 05:25:42PM -0500, FergusDaly AT aol DOT com wrote: >I upgraded from Cygwin 1.3.6-6 to 1.3.7-1 and lost the "interrupt" >capability. > >e.g.1. just at the console, I ran a diff -r command to compare two large >directories. Pressing failed to interrupt this time-consuming >activity, which carried on chugging away to the bitter end. > >e.g.2. inside an application, I accidentally triggered a huge print to >stdout command. Pressing failed ... etc etc. > >I reverted to 1.3.6-6 (easy! THANK YOU setup.exe) and all the required > capability was recovered. > >For the moment I'll stick with 1.3.6-6. Anybody found the same thing, or is >it me? ls -lR seems to terminate just fine with CTRL-C. 'cygcheck -r -s -v' might help track this down. >PS. I tried sending from my "real" address fergus AT bonhard DOT uklinux DOT net but >you've blocked me using some anti-spam drawbridge. That ainit fair. Sure it's fair. If you are subscribed to the mailing list you won't be subject to spam blockage. And, if you don't want to do that, there's another way to bypass the spam blockage which is mentioned in the bounce message. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/