int128 / wslexec

A wrapper to run Linux command inside WSL (Windows Subsystem for Linux) from native apps

wslexec

A wrapper to run a Linux command inside WSL (Windows Subsystem for Linux) from Windows native applications.

If you are looking for Git on WSL solution, andy-5/wslgit is the best.

Getting Started

Visual Studio Code and PHP

You can use PHP on WSL from Windows native Visual Studio Code.

Download the latest release and save as wslphp.exe.

Open Visual Studio Code and configure path as follows:

{
  "php.validate.executablePath": "C:\\Users\\USER\\Documents\\wslphp.exe"
}

Visual Studio and Node.js

WIP

How it works

Rename the binary to command name with prefix wsl. For example, rename the binary to wslgit to run the git command inside WSL.

Windows path translation

Windows paths (e.g. C:\) in command line are translated to WSL paths (e.g. /mnt/c).

For example,

wslgit.exe -C C:\Users\foo\example log

is translated to the following command:

git -C /mnt/c/Users/foo/example log

WSL path translation

WSL paths (e.g. /mnt/c) in standard input are translated to Windows paths (e.g. C:/).

For example,

/mnt/c/Users/foo/example

is translated to the following command:

c:/Users/foo/example

Contributions

Feel free to open issues and pull requests.

wslexec's Issues

Windows Paths are not translated to WSL Path

First big thanks for your work! It is a really cool tool. But for some time i had some problem with identifying WSL PHP in PHPStorm. After some debugging i found the reason. PHPStorm wants to execute the following command:

C:\Dev\wslphp.exe C:\Users\de_zunke\AppData\Local\Temp\ide-phpinfo.php
// Outputs: Could not open input file: C:\Users\de_zunke\AppData\Local\Temp\ide-phpinfo.php

On manually execution with the translated path it works as expected.

C:\Dev\wslphp.exe /mnt/c/Users/Dev/AppData/Local/Temp/ide-phpinfo.php
// Outputs: <?xml version="1.0"?><php version="7.3.8-1+ubuntu18.04.1+deb.sury.org+1" path_separator=":"><path_to_ini path="/etc/php/7.3/cli/php.ini"/> [..]

So i think there could be problem with translating the Windows Path to the WSL Path. I am using the latest Version 1.1. Are you aware of a problem or have any advise to check my system for? It is a current windows 10 pro 1903

Thanks!

Use wslpath tool from Windows 10 1803 update

ref: https://blogs.msdn.microsoft.com/commandline/2018/03/07/windows10v1803/

Since 1803 update, Windows 10 provides WSL <> Windows path converter due to new configuration (/etc/wsl.conf) which can set customized Windows mount path (like use /windir/ instead of /mnt/), and this wslpath tool ensures your configuration of path and convert it correctly.