From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: broken CTRL-BREAK handling
Date: Tue, 17 Jul 2001 13:28:00 -0000 [thread overview]
Message-ID: <20010717162846.A11316@redhat.com> (raw)
In-Reply-To: <20010717161453.A11212@redhat.com>
On Tue, Jul 17, 2001 at 04:14:53PM -0400, Christopher Faylor wrote:
>On Tue, Jul 17, 2001 at 02:06:21PM -0600, Troy Noble wrote:
>>b20.1 handled it differently. If I press the [X] or
>>CTRL-BREAK in a b20.1 window, JDK dutifully dumps the
>>stack trace.
>
>Hmm. I'll have to investigate this next week. I can't easily retrieve
>the B20 sources right now.
Ok. I lied. I can check this. I reverted some sources to around the
B20 time frame. AFAICT, my original assertion is true. B20 should
have treated CTRL-BREAK as equivalent to CTRL-C. If it didn't then
it sure appears to be a bug. I can't figure out how CTRL-C could work
if CTRL-BREAK wasn't also working the same way.
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:[~2001-07-17 13:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 13:06 Troy Noble
2001-07-17 13:15 ` Christopher Faylor
2001-07-17 13:28 ` Christopher Faylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-18 16:48 Karr, David
2001-07-18 14:01 Troy Noble
2001-07-18 13:42 Heribert Dahms
2001-07-18 12:55 Troy Noble
2001-07-18 9:32 Troy Noble
2001-07-18 9:56 ` Christopher Faylor
2001-07-18 16:36 ` Michael A. Chase
2001-07-17 13:50 Troy Noble
2001-07-17 19:55 ` 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 12:00 Troy Noble
2001-07-17 12:37 ` Christopher Faylor
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=20010717162846.A11316@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).