Another rvxt vs. minTTY 0.3.4

Another rvxt vs. minTTY 0.3.4

[Paul McFerrin]

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.  Seems that minTTY is 
starting the child process with SIGINT signals disabled.

At the prompt, Control-C is recognized.

- Paul

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

Re: Another rvxt vs. minTTY 0.3.4

[Andy Koppe]

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/

RE: Another rvxt vs. minTTY 0.3.4

[Gary R. Van Sickle]

> From:  Andy Koppe
> 
> 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.
> 

Yeah, it worked all day for me today as well.  Heavy duty makes, mix of
Cygwin and native programs being invoked, plenty of CTRL-C's, never had one
not get recognized.

-- 
Gary R. Van Sickle
 


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