# Cool WSL (Windows Subsystem for Linux) tips and tricks

It's no secret I dig WSL (Windows Subsystem for Linux) and now that WSL2 is available in Windows Insiders Slow it's a great time to really explore the options that are available. What I'm finding is so interesting about WSL and how it relates to the Windows system around it is how you can cleanly move data between worlds. This isn't an experience you can easily have with full virtual machines, and it speaks to the tight integration of Linux and Windows.

Look at all this cool stuff you can do when you mix your peanut butter and chocolate!

## Run Windows explorer from Linux and access your distro's files

When you're at the WSL/bash command line and you want to access your files visually, you can run «explorer.exe .» where is the current directory, and you'll get a Windows Explorer window with your Linux files served to you over a local network plan9 server.

### Use real Linux commands (not CGYWIN) from Windows

I've blogged this before, but there are now aliases for PowerShell functions that allow you to use real Linux commands from within Windows.

You can call any Linux command directly from DOS/Windows/whatever by just putting it after WSL.exe, like this!

C:\temp> wsl ls -la | findstr "foo"
-rwxrwxrwx 1 root root     14 Sep 27 14:26 foo.bat

C:\temp> dir | wsl grep foo
09/27/2016  02:26 PM                14 foo.bat

C:\temp> wsl ls -la > out.txt

C:\temp> wsl ls -la /proc/cpuinfo
-r--r--r-- 1 root root 0 Sep 28 11:28 /proc/cpuinfo

C:\temp> wsl ls -la "/mnt/c/Program Files"
...contents of C:\Program Files...

## Use real Windows commands (not wine) from Linux

Windows executables are callable/runnable from WSL/Linux because the the Windows Path is in the \$PATH until Windows. All you have to do is call it with .exe at the end, explicitly. That's how «Explorer.exe .» works above. You can also notepad.exe, or whatever.exe!

### Run Visual Studio Code and access (and build!) your Linux apps natively on Windows

You can run «code .» when you're in a folder within WSL and you'll get prompted to install the VS Remote extensions. That effectively splits Visual Studio Code in half and runs the headless VS Code Server inside Linux with the VS Code client in the Windows world.

You'll also need to install Visual Studio Code and the Remote — WSL extension. Optionally, check out the beta Windows Terminal for the best possible terminal experience on Windows.

Here's a great series from the Windows Command LIne blog. You can find the full series here:

Here's the benefits of WSL 2

• Virtual machines are resource intensive and create a very disconnected experience.
• The original WSL was very connected, but had fairly poor performance compared to a VM.
• WSL 2 brings a hybrid approach with a lightweight VM, a completely connected experience, and high performance.

Again, now available on Windows 10 Insiders Slow.

## Run multiple Linuxes in seconds, side by side

Here I'm running «wsl --list --all» and I have three Linuxes already on my system.

C:\Users\scott>wsl --list --all
Windows Subsystem for Linux Distributions:
Ubuntu-18.04 (Default)
Ubuntu-16.04
Pengwin

I can easily run them, and also assign a profile to each so they appear in my Windows Terminal dropdown.

## Run an X Windows Server under windows using pengwin

Pengwin is a custom WSL-specific Linux distro that's worth the money. You can get it at the Windows Store. Combine Pengwin with an X Server like X410 and  you've got a very cool integrated system.

## Easily move WSL distros between windows systems

Ana Betts points out this great technique where you can easily move your perfect WSL2 distro from one machine to n machines.

wsl --export MyDistro ./distro.tar

# put it somewhere, dropbox, onedrive, elsewhere

mkdir ~/AppData/Local/MyDistro
wsl --import MyDistro ~/AppData/Local/MyDistro ./distro.tar --version 2 

That's it. Get your ideal Linux setup sync'ed on all your systems.

## Use the windows Git credential provider within WSL

All of these things culminate in this lovely blog post by Ana Betts where she integrates the Windows Git Credential Provider in WSL by making /usr/bin/git-credential-manager into a shell script that calls the Windows git creds manager. Genius. This would only be possible given this clean and tight integration.

Now, go out there, install WSL, Windows Terminal, and make yourself a shiny Linux Environment on Windows.
Microsoft
Microsoft — мировой лидер в области ПО и ИТ-услуг