For those unfamiliar with msys2, it is a port of *nix programs to Windows. There, I could do things like:
$ some-prog ~/.profile $ some-prog /c/Windows/System32/drivers/etc/hosts
some-prog could be any binary, regardless of whether they were general Windows programs or programs compiled with compilers in msys2. The paths would be transparently translated, thus giving that very *nix-ish vibe even when working with programs not part of msys2.
Currently, I'm checking out WSL/"Bash on Windows" (Creators Update), and I seem to have a problem.
For a Linux program, everything works fine:
~ $ nano ~/.
As expected, nano opens up with contents of
When trying to invoke a Windows program though, there's an error:
~ $ "/mnt/c/Program Files/Sublime Text 3/subl.exe" ~/.profile Unable to translate current working directory. Using C:\Users\Admin
And it opens up
C:\home\<wsl_username>\.profile in Sublime Text, whereas the actual file should be
Windows paths aren't better either:
~ $ "/mnt/c/Program Files/Sublime Text 3/subl.exe" /mnt/c/Windows/System32/drivers/etc/hosts Unable to translate current working directory. Using C:\Users\Admin
This opens up
C:\mnt\c\Windows\System32\drivers\etc\hosts, which is again the wrong path.
Is there a way I can have a correct, msys2-like path integration on WSL?