Let’s use the brand new Linux shell in there. VSCode’s integrated terminal is a great productivity booster. The Windows Terminal released, and it’s awesome.Īt least, I think so. I’ll use the one that’s integrated into VSCode most of the time anyway. In anticipation of that release, I’m not going to change much there. Good news: they are coming came out with a new one and it looks really awesome! Let’s face it, the terminal that ships with Windows is pretty lackluster. The thing that terminal communicates with and does most of the work, the shell. The thing you see and type into, the terminal. When you open your terminal there are 2 sides at work.

VSCode wil automatically connect to your WSL instance when you launch VSCode from Linux.Į.g. Remember to set the autocrlf setting to input for git. The two I’ll install for Windows are: VSCode and git for Windows. Let’s start loading up our environment with some needed tools.Ī few tools still need to be installed on the Windows side, the rest are all Linux tools. More details on changes are available in Microsoft’s WSL2 release blogpost Installing tools Whoooo, spooky 👻 (but, really, it was a bad idea.) Modifying Linux files from Windows in WSL1 was always warned against, as this could cause bad things to happen. In WSL2 you can now access files from Linux in Windows and the other way around. That way they benefit from file performance increases compared to WSL1. Users of WSL2 are encouraged to place their files inside the Linux file system. In the words of a certain wooden puppet, it is now a real boy.

Previously there was a kernel compatibility layer that could not do quite as much. Windows Subsystem for Linux 2 comes with a real Linux kernel. Opening the distro you installed will show a bash prompt.

Zsh windows terminal