This is the mail archive of the
mailing list for the Cygwin project.
Re: cygpath (reprised)
- From: cyg Simple <cygsimple at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 1 Mar 2017 09:33:58 -0500
- Subject: Re: cygpath (reprised)
- Authentication-results: sourceware.org; auth=none
- References: <0D835E9B9CD07F40A48423F80D3B5A704BBEEB39@USA7109MB022.na.xerox.net> <firstname.lastname@example.org> <0D835E9B9CD07F40A48423F80D3B5A704BBEEB6F@USA7109MB022.na.xerox.net> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
On 3/1/2017 8:12 AM, Andrey Repin wrote:
> Greetings, cyg Simple!
>> On 2/25/2017 8:13 PM, Andrey Repin wrote:
>>> Greetings, cyg Simple!
>>>> Also a : isn't a valid character for a name in Windows. Cygwin uses
>>>> some magic to represent it in UNICODE format though.
>>> It isn't a valid file "name" character, yes, but it is still a meaningful
>>> character in pathname under windows.
>>> Just the meaning of it is far from regular file name semantics.
>> Not when specifying ./a:b which was the example being discussed.
> We were discussing "a:b", not "./a:b".
Then you need to re-read the elided content. An example of ./a:b was
given and what I responded to.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple