Andre Maroneze writes: > 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)
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. > In cygpath 2.6.0, this outputs C? (C followed by the unicode character > 0xF03A, which is a ":" (0x3A) character, but prefixed with "F0"). That's how the otherwise forbidden ":" character gets encoded into the filename. > 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. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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
