Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <2C08D4EECBDED41184BB00D0B74733420473EE68@exchanger.cacheflow.com>
From: "Karr, David" <david DOT karr AT cacheflow DOT com>
To: cygwin AT cygwin DOT com
Subject: RE: broken CTRL-BREAK handling
Date: Wed, 18 Jul 2001 16:48:53 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"

I've seen several discussions over the last few months which essentially
boil down to some people wanting convenience vs. other people wanting
"clarity of purpose", for lack of a better term.  I'm very sympathetic to
Unix users wanting their "ported-to-cygwin" apps to work as similarly as
possible on Cygwin.  I worked on Unix for many years before working the last
few in a "mixed" environment.

Frankly, I think the best approach is to consider a "pragmatic" approach.  I
wouldn't want to do anything to prevent Unix applications from working
without change, but I also think it's odd to try to "hide" from the fact
that you're running on Windows.  It seems perfectly reasonable (and
convenient) to have "pragmatic" features in Cygwin, which accepts the fact
that we're in a Windows environment.  I think this issue probably falls into
that area, and others like understanding "c:/filepath" also.

I'm not as informed on these issues as I'd like, but this is just my
impression from my experience.

-----Original Message-----
From: Michael A. Chase [mailto:mchase AT ix DOT netcom DOT com]
Sent: Wednesday, July 18, 2001 4:27 PM
To: Troy Noble; cygwin AT cygwin DOT com
Subject: Re: broken CTRL-BREAK handling


----- Original Message -----
From: "Troy Noble" <troy DOT noble AT channelpoint DOT com>
To: <cygwin AT cygwin DOT com>
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/

--
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/