{"id":53080,"date":"2019-11-23T00:00:00","date_gmt":"2019-11-22T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/krutye-lajfhaki-dlya-raboty-s-wsl-podsistema-windows-dlya-linux"},"modified":"2020-02-18T14:00:56","modified_gmt":"2020-02-18T11:00:56","slug":"krutye-lajfhaki-dlya-raboty-s-wsl-podsistema-windows-dlya-linux","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/krutye-lajfhaki-dlya-raboty-s-wsl-podsistema-windows-dlya-linux","title":{"rendered":"Cool life hacks for working with WSL (Windows Subsystem for Linux)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

I am deeply immersed in WSL (Windows Subsystem for Linux), and now that\u00a0WSL2<\/a><\/noindex>\u00a0it is available in\u00a0Windows Insiders<\/a><\/noindex>, it's a great time to truly explore the available options. A very interesting feature I found in WSL is the ability to 'seamlessly' move data between worlds. This is not an experience you can easily achieve with full virtual machines, and it speaks to the tight integration of Linux and Windows.<\/p>\n

Below are some interesting things you can do by mixing peanut butter and chocolate!<\/p>\n

\"Cool<\/a><\/noindex><\/p>\n

Run Windows Explorer from Linux and access your distribution files<\/h2>\n

\nWhen you are in the WSL \/ bash command line and want visual access to your files, you can run 'explorer.exe .' from your current directory, and you'll get a Windows Explorer window where your Linux files will be delivered to you through the plan9 local network server.<\/p>\n

\"Cool
\n<\/p>\n

Use real Linux commands (not Cygwin) from Windows<\/h2>\n

\nI've written about this before, but now there are aliases for PowerShell functions, which allow you to use real Linux commands<\/a><\/noindex>\u00a0from inside Windows.<\/p>\n

You can call any Linux command directly from DOS\/Windows\/whatever by putting it after WSL.exe like this.<\/p>\n

C:temp> wsl ls -la | findstr \"foo\"\n-rwxrwxrwx 1 root root     14 Sep 27 14:26 foo.bat\n\nC:temp> dir | wsl grep foo\n09\/27\/2016  02:26 PM                14 foo.bat\n\nC:temp> wsl ls -la > out.txt\n\nC:temp> wsl ls -la \/proc\/cpuinfo\n-r--r--r-- 1 root root 0 Sep 28 11:28 \/proc\/cpuinfo\n\nC:temp> wsl ls -la \"\/mnt\/c\/Program Files\"\n...contents of C:Program Files...<\/code><\/pre>\n
\nWindows executables can be called\/runned from WSL\/Linux, as the Windows path is in the $PATH before Windows. All you need to do is explicitly call them with .exe at the end. Here's how 'Explorer.exe' works. You can also do notepad.exe or any other file.<\/p>\n
Launch Visual Studio Code and access your Linux applications natively on Windows<\/h2>\n
\nYou can run 'code.' while in a folder in WSL, and you will be prompted to install\u00a0VS Remote extensions.<\/a><\/noindex>. This effectively splits Visual Studio Code in half and runs a 'headless' VS Code Server in Linux with the VS Code client in the Windows world.<\/p>\n
You also need to install\u00a0Visual Studio Code<\/a><\/noindex>\u00a0and the Remote - WSL extension.<\/a><\/noindex>. Optionally, install\u00a0the beta version of Windows Terminal<\/a><\/noindex>\u00a0for a better terminal experience on Windows.<\/p>\n
Here's a great collection of articles from the Windows Command Line blog.<\/p>\n