On 10/6/2016 8:38 AM, Andre Maroneze wrote:
I just noticed a difference in behavior between versions 2.5.2 and
2.6.0 of cygpath (the ones I could test): if I run
cygpath -m " C:"
(notice the space before the C, inside the double quotes)
In cygpath 2.6.0, this outputs C? (C followed by the unicode character
0xF03A, which is a ":" (0x3A) character, but prefixed with "F0").
In cygpath 2.5.2 (and 2.4.1, which I also could test), it outputs C:,
as I would expect.
This happens on both Windows 7 and Windows 8.1, and not only on my
machine, so it seems fairly deterministic.
Is it some sort of undefined behavior to give an argument to cygpath
starting with a space inside double quotes?
I think you'll find the explanation here:
https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars
I don't know why this doesn't happen with earlier versions of cygwin.
Ken
--
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