This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: rxvt ctrl-c killing process
Sven KÃhler:
> 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. ÂSome googling around uncovered
>> that I should try "rxvt". ÂMy experience with rxvt is pretty good, after
>> reading online some basic configuration tips. ÂBut unfortunately I've come
>> across a deal-breaker and I'm not sure exactly what the culprit is. ÂIf 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. ÂI
>> found a quickie Java code sample online that anyone can quickly compile and
>> try for themselves: Âhttp://waelchatila.com/2006/01/13/1137143896635.html
>> save to CtrlC.java then type "javac CtrlC" then "java -cp . CtrlC" Â and
>> then hit ctrl-c. ÂIt 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).
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.
Andy
--
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