Re: cygpath 2.6.0: -m " C:" and garbled output

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 wrote: > A filename can legitimately start with a space and it is a r

Re: cygpath 2.6.0: -m " C:" and garbled output

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 fi

Re: cygpath 2.6.0: -m " C:" and garbled output

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 unic

cygpath 2.6.0: -m " C:" and garbled output

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