Re:Microsoft Adds an OpenSSH Client to Windows 10
by scooley on Tuesday December 12, 2017 @04:36PM
(#15909744)
We just released a tool to do the right path translation -- wslpath. Unfortunately we haven't added built in usage info yet. Here's a link[1] to usage info in recent Windows Insider flights.
Also, totally fair feedback about the naming. In FCU, we added wsl.exe in addition to bash.exe. It launches into your default shell rather than /bin/bash.
[1] https://github.com/Microsoft/WSL/issues/2715
* I work at Microsoft on WSL
Re:Microsoft Adds an OpenSSH Client to Windows 10
by WorldMaker on Tuesday December 12, 2017 @02:51PM
(#15908851)
I hadn't thought about that (I use PowerShell for most tasks so that is still my "home" shell and it's bash that's the rare one), but I half remembered something to that effect, so I went to the docs:
https://docs.microsoft.com/en-us/windows/wsl/interop
Calling Windows EXEs from bash will automatically retain the current working directory under /mnt/c/*, so it should just work out of the box. Looks like you might be able to get away with just adding native Windows git to your bash path.
Re:Microsoft Adds an OpenSSH Client to Windows 10
by Viper007Bond on Tuesday December 12, 2017 @03:39PM
(#15909245)
Yeah for example I have composer only installed in Windows (EXE) and not within WSL and it works fine within the bash prompt.
Also, they _really_ chose a poor name for that executable; it should have been wsl.exe or some such, not bash.exe. At least lxss.exe isn't already in use by other software in my path...