DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=oebRhU8
	vWPOW/4Ni9p42HB6ohpn4BlffLG7elRhaQjGrjCAFkdvqAGfGFCgpK4S1IlUfEOM
	thdyeCMBOrl8BC1k1TuMq/slxOED9W6jLtq3T3k9h+j0lZkH9s25xNeNwp6JtA5K
	T7y1jEiKN9tZkMes23fzP1tbcnyrYPjG4vio=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
In-Reply-To: <87zimhp9df.fsf@Rainer.invalid>
References: <CAFKkpzpSu7bOCKf3uAwHrEiHcs5M9RCzVV4o2V=Lpo7PrgnGJg AT mail DOT gmail DOT com> <87zimhp9df DOT fsf AT Rainer DOT invalid>
From: Andre Maroneze <maroneze AT gmail DOT com>
Date: Thu, 6 Oct 2016 22:47:17 +0200
Message-ID: <CAFKkpzp8a_JRk8j5=o6uJUG3hxVLPsFV_0_spifFEXCOf=fbEA@mail.gmail.com>
Subject: Re: cygpath 2.6.0: -m " C:" and garbled output
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8

Just to clarify, " C:" is not the entire filepath I was giving to
cygpath, it's more like " C:/Temp/a.txt", but I reduced to it when
trying to isolate the difference between versions.

On Thu, Oct 6, 2016 at 9:26 PM, Achim Gratz <Stromeko AT nexgo DOT de> wrote:
> A filename can legitimately start with a space and it is a relative filename in that case.  So dropping the space just to get something that looks like a drive letter is wrong.

Indeed! I hadn't thought it that way, and it nicely explains why no
conversion happens without the space (in which case it would be
considered an absolute file path, despite starting with "C:").

> That's how the otherwise forbidden ":" character gets encoded into the filename.

I do know that ":" is forbidden in a filename, but because I (assumed
I) was giving it a file path (and one which was supposed to be
absolute), I didn't consider that the rules about special filenames
would apply. But having a relative file path changes everything.

>> In cygpath 2.5.2 (and 2.4.1, which I also could test), it outputs C:, as I would expect.
>
> No, that's wrong as explained above.

I should have said, "as I got used to expect due to past behavior". I
would guess those versions were more lenient towards absolute file
paths, which would however be an issue for filenames starting with
spaces.

Thanks to both of you for the clarifications. In the end, the extra
whitespace was incorrectly inserted by a makefile function call, so I
fixed it anyway, but I wanted to fully understand the issue to avoid
incurring into similar problems later.

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