The Cygwin User Guide on path names

Mark Hansen
Fri Aug 26 13:08:00 GMT 2016

On 8/25/2016 7:53 PM, Andrey Repin wrote:
> Greetings, Linda Walsh!
>> Andrey Repin wrote:
>>> Greetings, Ken Brown!
>>>> The documentation also says, "The usage of Win32 paths, though possible,
>>>> is deprecated...."  I wonder if this should be strengthened to say
>>>> something like, "The usage of Win32 paths, though possible, is strongly
>>>> deprecated and may be removed in a future release of Cygwin."
>>> That would be the day Cygwin die for me.
>>> --
>>> With best regards, Andrey Repin
>>> Wednesday, August 24, 2016 12:50:55
>>> Sorry for my terrible english...
>> ---
>> Curious -- but why?  How do you make use of win32 pathnames
>> ( "C:\bin" versus "/bin" or "/c/bin" or "/cygdrive/c/bin" )
>> depending on how your cygwin is configured).
> I make use of win32 paths directly.
> diff and grep are the most used tools.
>> I'm wondering if maybe there is a misunderstanding?
> I don't think so.
>> For the most part -- many cygwin apps may not work
>> correctly if given a win32 path in the same place you'd
>> put a *nix path due to the backslashes being turned into
>> quote sequences.
> That's too bad for such poor apps.
>> I mean, you can't type:
>>> ls C:\bin
>>   (instead of )
>>> ls /c/bin

Can we differrentiate between C:/bin and C:\bin?

I've always used C:/bin. Using drive identifiers and UNIX-style path separators.

Is the proposal that this no longer be valid under cygwin?

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list