From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: broken CTRL-BREAK handling
Date: Wed, 18 Jul 2001 09:56:00 -0000 [thread overview]
Message-ID: <20010718125553.E15332@redhat.com> (raw)
In-Reply-To: <8F23E55D511AD5119A6800D0B76FDDE1CA2EF5@cpex3.channelpoint.com>
On Wed, Jul 18, 2001 at 10:32:35AM -0600, Troy Noble wrote:
>Bottom line... that still feels broken to me if the intent is for
>cygwin (more specifically, the bash shell running with cygwin) to
>be able to launch/stop native win32 apps with the same semantics one
>has come to expect when running cmd shell.
>If that's not the goal, then it's a non-issue.
I don't think that that has ever been a stated goal for cygwin.
What would a program, ported from UNIX expect in this situation? With
your patch, I believe that it would just unceremoniously terminate with
no way to handle cleanup other than to add windows-specific code for
dealing with ctrl-break.
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-18 9:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 9:32 Troy Noble
2001-07-18 9:56 ` Christopher Faylor [this message]
2001-07-18 16:36 ` Michael A. Chase
-- 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-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 13:06 Troy Noble
2001-07-17 13:15 ` Christopher Faylor
2001-07-17 13:28 ` Christopher Faylor
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=20010718125553.E15332@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).