X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0	tests=AWL,BAYES_00,TW_YG
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4C030C39.8020303@gmail.com>
References: <83d3wff7t5 DOT fsf AT garydjones DOT name>	<837hmmenu0 DOT fsf AT garydjones DOT name>	<AANLkTilbSnkvkJwetC20mzSWld48nOTYtDnKp8OXNQNh AT mail DOT gmail DOT com>	<83d3wdomiy DOT fsf AT garydjones DOT name>	<4C030C39 DOT 8020303 AT gmail DOT com>
Date: Tue, 1 Jun 2010 10:19:57 +0200
Message-ID: <AANLkTil4WCMkMxicHxGwfLVE-dwCHxW7wF7PyhO6zVZf@mail.gmail.com>
Subject: Re: cygpath behaviour when input is not a path
From: "Gary ." <cygwin AT garydjones DOT name>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
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

On 5/31/10, Dave Korn wrote:
> On 30/05/2010 08:51, Gary wrote:
>> Since the tool
>> output is mixed paths and text, I'd hoped cygpath made "intelligent"
>> guesses about what was and was not likely to be a path.
>>
>
>   Well, that is basically what it does; but, being a POSIX tool, the
> consequence is that it assumes that a colon is just a char like any other in
> a
> filename.

Okay. So I'm SOL with tool output like
"Parse error: syntax error, unexpected '}' in
C:\cygwin\home\jg\work\foo.php on line 10"
then, short of parsing it myself :-(

Actually cygpath's response to the tool ouput in this instance was
"cygpath: can't convert empty path"
although that seems to be a barf on a previous, empty, line of output,
because on testing just that line with cygpath -u I got
"Parse error: syntax error, unexpected '}' in C:/cygwin/home/jg/work/foo.php on
line 10"
That is, the path is more posix-like, but certainly isn't "unixified".

-- 
Gary
Non-kook (allegedly)

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