From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: bash/cmd CTRL-C problem...
Date: Tue, 08 Jan 2002 17:13:00 -0000 [thread overview]
Message-ID: <20020109011311.GB28659@redhat.com> (raw)
In-Reply-To: <044301c198a8$8f0b61a0$0200a8c0@lifelesswks>
On Wed, Jan 09, 2002 at 11:57:04AM +1100, Robert Collins wrote:
>----- Original Message -----
>From: "Christopher Faylor" <cgf@redhat.com>
>
>> So, I think the easiest fix for the current problem is just to do a
>> 'signal (SIGINT, SIG_IGN)' prior to calling CreateProcess, restoring
>> the previous signal handler if the CreateProcess fails.
>
>You do realise, that thats what I've done, but via the more efficient
>way of returning TRUE to the signal.
Sure. I understand what you are doing. It usually only takes me a
couple of tries to "get it".
I'm specifically trying not to do the "TRUE" thing, though, since AFAICT
it isn't always appropriate.
For the record, I really appreciate your tracking this down. I finally
understand the issues here. These issues have been around for a long time
and the problems that you uncovered are probably responsible for some
longstanding cygwin strangeness.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-01-09 1:13 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 23:48 Michael Rumpf
2001-12-20 1:28 ` Michael Rumpf
2001-12-21 2:17 ` Michael Rumpf
2001-12-21 7:27 ` Corinna Vinschen
2001-12-21 8:46 ` Michael Rumpf
2002-01-04 3:51 ` Michael Rumpf
2002-01-04 9:04 ` Christopher Faylor
2002-01-07 0:46 ` Michael Rumpf
2002-01-07 1:10 ` Robert Collins
2002-01-07 1:58 ` Michael Rumpf
2002-01-07 2:30 ` Robert Collins
2002-01-07 2:56 ` Michael Rumpf
2002-01-07 5:15 ` CGF: please review my logic " Robert Collins
2002-01-07 6:18 ` Michael Rumpf
2002-01-07 8:50 ` CGF: " Christopher Faylor
2002-01-07 15:00 ` Robert Collins
2002-01-07 15:45 ` Christopher Faylor
2002-01-07 16:15 ` Robert Collins
2002-01-07 16:21 ` Christopher Faylor
2002-01-07 16:43 ` Robert Collins
2002-01-07 23:00 ` Robert Collins
2002-01-08 8:19 ` Christopher Faylor
2002-01-08 14:16 ` Robert Collins
2002-01-08 16:39 ` Christopher Faylor
2002-01-08 16:43 ` Robert Collins
2002-01-08 16:55 ` Christopher Faylor
2002-01-08 16:57 ` Robert Collins
2002-01-08 17:13 ` Christopher Faylor [this message]
2002-01-08 17:16 ` Robert Collins
2002-01-09 18:46 ` Christopher Faylor
2002-01-09 19:42 ` Christopher Faylor
2002-01-09 23:59 ` Robert Collins
2002-01-10 7:53 ` Christopher Faylor
2002-01-08 17:46 ` Charles Wilson
[not found] ` <027401c19855$68842f60$c51811ac@brokat.de>
[not found] ` <03a901c1989b$69c8e190$0200a8c0@lifelesswks>
2002-01-09 0:14 ` Michael Rumpf
2002-01-07 8:09 Gregory W. Bond
2002-01-07 8:27 ` Michael Rumpf
2002-01-07 9:06 ` Gregory W. Bond
2002-01-07 9:18 ` Michael Rumpf
2002-01-07 9:32 ` Christopher Faylor
2002-01-07 9:28 Gregory W. Bond
2002-01-07 10:07 ` Christopher Faylor
2002-01-07 12:14 ` Gregory W. Bond
[not found] <3C3E059B.2080401@ece.gatech.edu>
2002-01-11 4:01 ` Andy Piper
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=20020109011311.GB28659@redhat.com \
--to=cgf@redhat.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).