Satish Balay <[email protected]> writes: > On Wed, 12 Apr 2017, Jed Brown wrote: > >> >> This is the error message that old blog post refers to >> >> >> >> >> >> https://blogs.msdn.microsoft.com/commandline/2016/10/19/interop-between-windows-and-bash/ >> >> >> >> and the new post runs exactly the same command without error. Can you >> >> run "notepad.exe sizeof.c"? >> > >> > I get the same error as the blog.. >> >> The new one runs that exact command successfully. See > > I'm on the new one. (version 1703, buid: 15063.138) >> >> Windows <-> Linux Interop >> >> https://blogs.msdn.microsoft.com/commandline/2017/04/11/windows-10-creators-update-whats-new-in-bashwsl-windows-console/ >> > > Notice the path (/mnt/c/temp) - its Windows FS - not WSL FS. That > works fine [as I mentioned earlier with my example usage]
For shits and giggles, I set up a windows 10 vagrant box because I didn't believe Microsoft would have solved path mapping between Windows and WSL / ubuntu files. I get the same errors Satish posted (Satish, as always, you right). vagrant@win10:~$ cd vagrant@win10:~$ echo foo >> foo.txt vagrant@win10:~$ notepad.exe foo.txt # error; can't find file vagrant@win10:~$ cd /mnt/c vagrant@win10:/mnt/c$ mkdir foo; cd foo vagrant@win10:/mnt/c/foo$ echo foo >> foo.txt vagrant@win10:/mnt/c/foo$ notepad.exe foo.txt # works vagrant@win10:/mnt/c/foo$ notepad.exe $PWD/foo.txt # error ¯\_(ツ)_/¯
signature.asc
Description: PGP signature
