X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Wed, 8 Sep 2010 15:39:09 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Windows-style pathname does not work as command - why?
Message-ID: <20100908193909.GB7484@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <4C7FE2C2.8060104@fgm.com> <4C7FE938.6060806@redhat.com> <20100902211830.GC527@ednor.casa.cgf.cx> <4C87B2A3.1050702@fgm.com> <4C87BB59.1020808@cygwin.com> <AANLkTi=uqk0JjWhCG96OxVWeG-JrdpCNp-XZfuyjfF7k@mail.gmail.com> <4C87DA5D.2070204@cygwin.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C87DA5D.2070204@cygwin.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Wed, Sep 08, 2010 at 02:47:57PM -0400, Larry Hall (Cygwin) wrote:
>On 9/8/2010 1:24 PM, Andy Koppe wrote:
>> On 8 September 2010 17:35, Larry Hall (Cygwin) wrote:
>>>> Isn't the whole reason for Cygwin actually to enable doing Unixy things
>>>> 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.

cgf

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

