Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: FergusDaly AT aol DOT com
Message-ID: <ac.21433e43.297c9de6@aol.com>
Date: Sun, 20 Jan 2002 17:25:42 EST
Subject: <Ctrl-c> interrupt failure after upgrading 1.3.6-6 to 1.3.7-1
To: cygwin AT cygwin DOT com
CC: fergus AT bonhard DOT uklinux DOT net
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 7.0 for Windows UK sub 52

I upgraded from Cygwin 1.3.6-6 to 1.3.7-1 and lost the <Ctrl-c> "interrupt"
capability.

e.g.1. just at the console, I ran a diff -r command to compare two large
directories. Pressing <Ctrl-c> 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 <Ctrl-c> failed ... etc etc.

I reverted to 1.3.6-6 (easy! THANK YOU setup.exe) and all the required
<Ctrl-c> capability was recovered.

For the moment I'll stick with 1.3.6-6. Anybody found the same thing, or is
it me?

Thank you.

Fergus

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.

--
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/