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_YG,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Message-ID: <COL102-W511A3BA55667290B3DD564B5730@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: Thu, 9 Sep 2010 14:14:13 -0700
In-Reply-To: <4C894A05.10504@fgm.com>
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>,<4C894A05 DOT 10504 AT fgm DOT com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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: Thu, 9 Sep 2010 16:56:37 -0400
> From: daniel
> To: cygwin
> Subject: Re: Windows-style pathname does not work as command - why?
>
>
> Not yet. Cygpath certainly supports Windows-style paths. Are you
> claiming that places like that are the only place that it is "accepted"
> to use Windows-styles paths (that is, if something like "ls 'C:\x\y'" quit
> working, it likely wouldn't be fixed)?
>
I'm answering more generally than just "ls".
Everything is ultimately on a case by case basis. If it stops working
because of a conflict with an important posixy thing, then it is likely
gone. If it just stops working because of an update to some package,
then if someone (the package maintainer or some motivated user) wants it
fixed, it can be fixed. But clearly SHTDI.
=20
I think that it is time for this thread to move to the cygwin talk list.
=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