From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Another rvxt vs. minTTY 0.3.4
Date: Thu, 15 Jan 2009 22:34:00 -0000 [thread overview]
Message-ID: <496FABB3.1000703@gmail.com> (raw)
In-Reply-To: <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/
next prev parent reply other threads:[~2009-01-15 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 13:06 Paul McFerrin
2009-01-15 22:34 ` Andy Koppe [this message]
2009-01-16 11:18 ` Gary R. Van Sickle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=496FABB3.1000703@gmail.com \
--to=andy.koppe@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).