Re: Unexpected behavior from cygpath command

2019-11-17 Thread Andrey Repin
Greetings, Lee! >>> I think on both systems the handling of 8.3 names is configured >>> differently. You can check this with the Window command fsutil. (This >>> command requires elevated permissions) >>> >>> I get the following output on my system. >>> >>> C:\WINDOWS\system32>fsutil 8dot3name que

Re: Unexpected behavior from cygpath command

2019-11-14 Thread Lee
On 11/13/19, Alfred von Campe wrote: > On Nov 13, 2019, at 2:08, Frank Redeker wrote: > >> I think on both systems the handling of 8.3 names is configured >> differently. You can check this with the Window command fsutil. (This >> command requires elevated permissions) >> >> I get the following out

Re: Unexpected behavior from cygpath command

2019-11-13 Thread Brian Inglis
On 2019-11-13 11:29, Alfred von Campe wrote: > On Nov 13, 2019, at 2:08, Frank Redeker wrote: > >> I think on both systems the handling of 8.3 names is configured >> differently. You can check this with the Window command fsutil. (This >> command requires elevated permissions) >> >> I get the foll

Re: Unexpected behavior from cygpath command

2019-11-13 Thread Alfred von Campe
On Nov 13, 2019, at 2:08, Frank Redeker wrote: > I think on both systems the handling of 8.3 names is configured > differently. You can check this with the Window command fsutil. (This > command requires elevated permissions) > > I get the following output on my system. > > C:\WINDOWS\system32>f

Re: Unexpected behavior from cygpath command

2019-11-12 Thread Frank Redeker
Am 12.11.2019 um 23:16 schrieb Alfred von Campe: > I have two almost identical build servers, but cygpath is not behaving as > expected on one of them. Here is the output from the “good” build server: > > $ cygpath.exe —version | head -1 > cygpath (cygwin) 2.11.2 > > $ cygpath -d 'E:\Pr