Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <902870527300AD44AA59BADBCFC8A94701DC5208@i2km03-ukbr.domain1.systemhost.net>
From: duncan DOT loveday AT bt DOT com
To: cygwin AT cygwin DOT com
Subject: SIGINT to bash behaves differently in rxvt as compared to console

Date: Tue, 21 Jan 2003 18:37:12 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

I find on a Windows NT4 (SP6) platform with the latest versions (downloaded
today) of cygwin1.dll, rxvt, bash etc that if I run a windows command
script, say a.cmd, which in turn runs some other process (e.g. a pause), if
I hit ^C then the behaviour is different in rxvt as compared to the cygwin
console.

In the console, the process being run by the command script is always
interrupted and then sometimes the rest of the command script continues to
execute but sometimes it says 'Terminate batch job (Y/N)' in which case if I
answer 'Y' the whole command script stops.

In rxvt, the ^C returns me to a prompt but the process being run is not
interrupted and continues in the background.

What I'd really like is for the ^C to consistently abort the whole command
script.

Has anyone come across this and/or is able to offer advice/solutions ?

Duncan

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