Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <00a601c10fe1$df3debc0$6464648a@ca.boeing.com> From: "Michael A. Chase" To: "Troy Noble" , References: <8F23E55D511AD5119A6800D0B76FDDE1CA2EF5@cpex3.channelpoint.com> Subject: Re: broken CTRL-BREAK handling Date: Wed, 18 Jul 2001 16:27:04 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 ----- Original Message ----- From: "Troy Noble" To: Sent: Wednesday, July 18, 2001 09:32 Subject: RE: broken CTRL-BREAK handling > 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. My understanding is just about the opposite. The purpose of Cygwin is to allow UNIX applications to build and run under Win32 with as few changes as possible. That you can run Win32 apps from bash as well is just an extra benefit. -- 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/