This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Another rvxt vs. minTTY 0.3.4
- From: Andy Koppe <andy dot koppe at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 15 Jan 2009 21:33:39 +0000
- Subject: Re: Another rvxt vs. minTTY 0.3.4
- References: <496EDD78.5070409@columbus.rr.com>
Paul McFerrin wrote:
I have another difference between 0.3.4 and 0.3.3 of minTTY and rxvt.
If you have a long-running script running, any attemps to stop it with
either Control-C or Control-\ does nothing.
It's working here. Just tried it with a 'configure' script.
Seems that minTTY is
starting the child process with SIGINT signals disabled.
Signals are left untouched on the way to the child command's exec()
call, which means the child process will inherit MinTTY's set of ignored
signals. How are you invoking MinTTY?
Would people like to see this behaviour changed so that all child
process signal handlers are reset to SIG_DFL?
At the prompt, Control-C is recognized.
I think that's because bash disables pty signal generation and processes
control characters directly.
Andy
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/