public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: broken CTRL-BREAK handling
Date: Tue, 17 Jul 2001 12:37:00 -0000	[thread overview]
Message-ID: <20010717153654.B10822@redhat.com> (raw)
In-Reply-To: <8F23E55D511AD5119A6800D0B76FDDE1CA2EEE@cpex3.channelpoint.com>

On Tue, Jul 17, 2001 at 01:00:25PM -0600, Troy Noble wrote:
>In exceptions.cc:ctrl_c_handler
>
>I think the following code should be added:
>
>  /* Return FALSE to allow other control handlers to handle CTRL-BREAK */
>  if (type == CTRL_BREAK_EVENT)
>      return FALSE;
>
>before the section of code that checks the pids, sids, pgids etc. and
>eventually culminates in a
>
>      kill (-myself->pid, SIGINT);
>
>Without this code, the current behavior in cygwin 1.3.2 is to send
>SIGINT to the process group whether you press CTRL-C or
>CTRL-BREAK.

Cygwin has considered CTRL-BREAK to be the same thing as CTRL-C for
about five years or so.

The fact that this inconveniences JDK is regrettable but I'm not going
to change well established behavior just to accomodate some non-cygwin
program.

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/

  reply	other threads:[~2001-07-17 12:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-17 12:00 Troy Noble
2001-07-17 12:37 ` Christopher Faylor [this message]
2001-07-17 13:06 Troy Noble
2001-07-17 13:15 ` Christopher Faylor
2001-07-17 13:28   ` Christopher Faylor
2001-07-17 13:25 Puttkammer, Roman
2001-07-17 14:10 ` Larry Hall (RFK Partners, Inc)
2001-07-17 15:38   ` Michael Schaap
2001-07-17 13:50 Troy Noble
2001-07-17 19:55 ` Christopher Faylor
2001-07-18  9:32 Troy Noble
2001-07-18  9:56 ` Christopher Faylor
2001-07-18 16:36 ` Michael A. Chase
2001-07-18 12:55 Troy Noble
2001-07-18 13:42 Heribert Dahms
2001-07-18 14:01 Troy Noble
2001-07-18 16:48 Karr, David

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=20010717153654.B10822@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).