[go-nuts] Re: Why does Go transform os.Args[] with colons in this way (win32/x64)

2020-06-11 Thread Russtopia
Ah, bad form posting before I tried it in a plain CMD.EXE context. The args are not transformed running from the vanilla command environment. Guess it's a nasty interaction with MSYS. -Russ On Thu, 11 Jun 2020 at 20:03, Russtopia wrote: > On windows, Go 1.14 running in my case under MSYS64 > >

Re: [go-nuts] Re: Why does Go transform os.Args[] with colons in this way (win32/x64)

2020-06-12 Thread 'Axel Wagner' via golang-nuts
I'd assume it has nothing to do with Go at all. You should try this with a minimal C program and look at the results. I assume it's something the shell is doing. On Fri, Jun 12, 2020 at 5:09 AM Russtopia wrote: > Ah, bad form posting before I tried it in a plain CMD.EXE context. > The args are n

Re: [go-nuts] Re: Why does Go transform os.Args[] with colons in this way (win32/x64)

2020-06-12 Thread Kurtis Rader
On Thu, Jun 11, 2020 at 8:09 PM Russtopia wrote: > Ah, bad form posting before I tried it in a plain CMD.EXE context. > The args are not transformed running from the vanilla command environment. > Guess it's a nasty interaction with MSYS. > TL;lDR: http://www.mingw.org/wiki/Posix_path_conversion