X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<27233683.post@talk.nabble.com>
Date:	Tue, 19 Jan 2010 14:14:26 -0800 (PST)
From:	"David Smiley @MITRE.org" <DSMILEY AT mitre DOT org>
To:	cygwin AT cygwin DOT com
Subject:	Re: rxvt ctrl-c killing process
In-Reply-To:	<416096c61001190902n4870f492ib56a92b86f53c27a@mail.gmail.com>
MIME-Version:	1.0
References:	<27221260 DOT post AT talk DOT nabble DOT com> <hj4ne5$bg6$1 AT ger DOT gmane DOT org> <416096c61001190902n4870f492ib56a92b86f53c27a AT mail DOT gmail DOT com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Mintty is even better (thanks Sven) but suffers from the same problem as An=
dy
is pointing out.  It's odd that when using Cygwin's default terminal
(whatever that thing is) that ctrl-C works there but not in mintty.  Any
work-arounds/alternatives?

~ David


Andy Koppe wrote:
>=20
> Sven K=C3=B6hler:
>> David Smiley:
>>> I have been fed-up with the default GUI shell on Cygwin, being used to
>>> the
>>> great Terminal that comes with Mac OS X. =C2=A0Some googling around unc=
overed
>>> that I should try "rxvt". =C2=A0My experience with rxvt is pretty good,=
 after
>>> reading online some basic configuration tips. =C2=A0But unfortunately I=
've
>>> come
>>> across a deal-breaker and I'm not sure exactly what the culprit is. =C2=
=A0If
>>> I
>>> run a java program from rxvt and control-C it (i.e. SIGINT) then it
>>> seems to
>>> kill -9 it instead of letting the program catch the signal to terminate.
>>> =C2=A0I
>>> found a quickie Java code sample online that anyone can quickly compile
>>> and
>>> try for themselves:
>>> =C2=A0http://waelchatila.com/2006/01/13/1137143896635.html
>>> save to CtrlC.java then type "javac CtrlC" then "java -cp . CtrlC" =C2=
=A0 and
>>> then hit ctrl-c. =C2=A0It works properly in Cygwin's default GUI shell =
but
>>> not
>>> rxvt.
>>>
>>> I *did* try searching the lists but didn't really find a resolution.
>>
>> Please install mintty (via Cygwin setup).
>=20
> I'm afraid that won't help with this issue. All a terminal does when
> Ctrl+C is pressed is write a ^C character to its pseudo terminal
> device (pty), and it's the pty driver that handles it (depending on
> the pty's settings): Cygwin processes are sent a SIGINT signal, but
> Windows processes such as Java are terminated outright.
>=20
> Andy
>=20
> --
> 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
>=20
>=20
>=20

--=20
View this message in context: http://old.nabble.com/rxvt-ctrl-c-killing-pro=
cess-tp27221260p27233683.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

- Raw text -