Re: cygpath (reprised)

2017-03-01 Thread cyg Simple
On 3/1/2017 8:12 AM, Andrey Repin wrote: > Greetings, cyg Simple! > >> On 2/25/2017 8:13 PM, Andrey Repin wrote: >>> Greetings, cyg Simple! >>> Also a : isn't a valid character for a name in Windows. Cygwin uses some magic to represent it in UNICODE format though. >>> >>> It isn't a

Re: cygpath (reprised)

2017-03-01 Thread Andrey Repin
Greetings, cyg Simple! > On 2/25/2017 8:13 PM, Andrey Repin wrote: >> Greetings, cyg Simple! >> >>> Also a : isn't a valid character for a name in Windows. Cygwin uses >>> some magic to represent it in UNICODE format though. >> >> It isn't a valid file "name" character, yes, but it is still a

Re: cygpath (reprised)

2017-02-28 Thread cyg Simple
On 2/27/2017 9:03 AM, Nellis, Kenneth (Conduent) wrote: > From: cyg Simple >> On 2/21/2017 1:22 PM, Nellis, Kenneth (Conduent) wrote: >>> I suppose one could argue that, by using -w, that cygpath might assume that >>> it >>> is converting *from* a POSIX path, and therefore the colon would not

Re: cygpath (reprised)

2017-02-28 Thread cyg Simple
On 2/25/2017 8:13 PM, Andrey Repin wrote: > Greetings, cyg Simple! > >> Also a : isn't a valid character for a name in Windows. Cygwin uses >> some magic to represent it in UNICODE format though. > > It isn't a valid file "name" character, yes, but it is still a meaningful > character in

RE: cygpath (reprised)

2017-02-27 Thread Nellis, Kenneth (Conduent)
From: cyg Simple > On 2/21/2017 1:22 PM, Nellis, Kenneth (Conduent) wrote: > > I suppose one could argue that, by using -w, that cygpath might assume that > > it > > is converting *from* a POSIX path, and therefore the colon would not > > indicate > > a drive letter--wouldn't that make

Re: cygpath (reprised)

2017-02-25 Thread Andrey Repin
Greetings, cyg Simple! > Also a : isn't a valid character for a name in Windows. Cygwin uses > some magic to represent it in UNICODE format though. It isn't a valid file "name" character, yes, but it is still a meaningful character in pathname under windows. Just the meaning of it is far from

Re: cygpath (reprised)

2017-02-25 Thread cyg Simple
On 2/21/2017 1:22 PM, Nellis, Kenneth (Conduent) wrote: > From: Andrey Repin >>> But, consider the following: >> >>> $ cygpath -w a:b | od -An -tx1c >>> 41 3a 62 0a >>>A : b \n >>> $ >> >>> Instead of the special character colon (:), shouldn't cygpath be showing >>> something in the

RE: cygpath (reprised)

2017-02-21 Thread Nellis, Kenneth (Conduent)
From: Andrey Repin > > But, consider the following: > > > $ cygpath -w a:b | od -An -tx1c > > 41 3a 62 0a > >A : b \n > > $ > > > Instead of the special character colon (:), shouldn't cygpath be showing > > something in the Unicode Private Use area? > > No, it shouldn't. > You've

Re: cygpath (reprised)

2017-02-21 Thread Andrey Repin
Greetings, Nellis, Kenneth (Conduent)! > I followed and understood the discussion to all the recent cygpath postings, > so I understand and expect the following: > $ cygpath -w 'a*b' | od -An -tx1c > 61 ef 80 aa 62 0a >a 357 200 252 b \n > $ > But, consider the following: > $

cygpath (reprised)

2017-02-21 Thread Nellis, Kenneth (Conduent)
I followed and understood the discussion to all the recent cygpath postings, so I understand and expect the following: $ cygpath -w 'a*b' | od -An -tx1c 61 ef 80 aa 62 0a a 357 200 252 b \n $ But, consider the following: $ cygpath -w a:b | od -An -tx1c 41 3a 62 0a A :