{"id":683,"date":"2018-09-17T10:00:48","date_gmt":"2018-09-17T08:00:48","guid":{"rendered":"https:\/\/craftcoders.app\/?p=683"},"modified":"2024-08-14T14:27:54","modified_gmt":"2024-08-14T12:27:54","slug":"5-things-i-love-about-wsl","status":"publish","type":"post","link":"https:\/\/craftcoders.app\/5-things-i-love-about-wsl\/","title":{"rendered":"5 Things I love about WSL"},"content":{"rendered":"\r\n
I got a new PC and love it! But a new PC also means a whole new setup and a lot of work. One of the first things I\u2019ve setup has been the Windows Subsystem for Linux. I know I am a developer and most of you would not expect me to work on a windows machine. Guys I must tell you windows is fucking awesome and with WSL it\u2019s just getting more awesome! Here five things I really love about WSL<\/p>\r\n\r\n\r\n\r\n
Starting with Windows build 14951 Microsoft added the possibility to (1) invoke Linux binaries from the Windows Console (2) invoke Windows binaries from the Linux Console and (3) sharing environment variables between Windows and Linux. Furthermore, with the Fall creates Update Microsoft include the windows path in the Linux $Path so it is easy to call windows binaries from Linux. So, to call Windows binaries from windows you just must type:<\/p>\r\n\r\n\r\n\r\n
[binaries name].exe<\/pre>\r\n\r\n\r\n\r\nFor instance, you could open the windows file explorer at the current location of your windows console by simply calling:<\/p>\r\n\r\n\r\n\r\n
explorer.exe .<\/pre>\r\n\r\n\r\n\r\n