X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_CG,TW_YG,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
Message-ID:	<COL102-W82DEE004A9F43F7BB77E6B5720@phx.gbl>
From:	Karl M <karlm30 AT hotmail DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Windows-style pathname does not work as command - why?
Date:	Wed, 8 Sep 2010 14:19:47 -0700
In-Reply-To:	<20100908193909.GB7484@ednor.casa.cgf.cx>
References:	<4C7FE2C2 DOT 8060104 AT fgm DOT com> <4C7FE938 DOT 6060806 AT redhat DOT com> <20100902211830 DOT GC527 AT ednor DOT casa DOT cgf DOT cx> <4C87B2A3 DOT 1050702 AT fgm DOT com> <4C87BB59 DOT 1020808 AT cygwin DOT com> <AANLkTi=uqk0JjWhCG96OxVWeG-JrdpCNp-XZfuyjfF7k AT mail DOT gmail DOT com> <4C87DA5D DOT 2070204 AT cygwin DOT com>,<20100908193909 DOT GB7484 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version:	1.0
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

> Date: Wed, 8 Sep 2010 15:39:09 -0400
> From: cgf
> To: cygwin
> Subject: Re: Windows-style pathname does not work as command - why?
>
> >>>> Isn't the whole reason for Cygwin actually to enable doing Unixy thi=
ngs
> >>>> in Windows (that is, providing Windows/Unix interoperablity?
> >>>
> >>> No, that's not a key goal. From the Cygwin main web page:
> >>>
> >>> Cygwin is a Linux-like environment for Windows
> >>
> >> Well, I (and my employer) would not be using Cygwin if it wasn't for
> >> the Windows integration, in particular the ability to plug POSIX and
> >> Windows programs together.
> >>
> >> If I just wanted to run Linux software on Windows, I'd use a virtual
> >> machine or coLinux. While Cygwin's lower resource usage is nice to
> >> have, that's easily outweighed by the inevitable compatibility and
> >> performance drawbacks that come with building on top of Win32.
> >
> >There are allot of different reasons people choose to use Cygwin.
>
> Correct. And, people apparently find Cygwin useful even when their
> usage does not 100% align with the stated project goals. That does not
> mean that we're going to change the goals and, given the project goals,
> it certainly doesn't mean that it's a bug when a Windows-specific usage
> like a MS-DOS path doesn't work in a Cygwin program.
>
To be fair (as opposed to just mean) Cygwin does provide other tools to
aid in interoperability, such as, cygpath and run (and run2). Being Unixy
(Linuxy) is just more important than supporting Windowsisms. If the
priorities were reversed, Cygwin would be less useful overall.
=20
Thanks,
=20
...Karl=20=09=09=20=09=20=20=20=09=09=20=20

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -