Microsoft is making it available to download the new Microsoft command prompt at its early stages and then compile the code and build the project themselves to have an early release access to the utility. Windows Terminal is a new, modern terminal console that allows accessing all of these environments from a single location. Hence, the recent news from Microsoft is the new Windows Terminal console. However, Microsoft is wanting to make things easier to access the various environments using a single console. PowerShell is accessed from the PowerShell console via powershell.exe. Up until now, generally speaking, if you ware accessing the traditional command prompt, you do this from cmd.exe. Microsoft is at it again, releasing cool new tools that are taking code development and infrastructure operations a step forward. Hopefully you found this post helpful, if you have any questions you can find me on Twitter.***Update*** Windows Terminal Preview Microsoft Store Link posted *** See Below The Windows Terminal only knows about paths from Windows' perspective, so if you try to put in the home directory path directly it won't work: I've only tested this with WSL2 but I think it's the same for WSL1 NOTE: Setting a non-network path won't work Now when you launch WSL in the terminal it will start in good old ~
Once in the settings json file find the WSL entry and set the startingDirectory to the network path of your WSL home directory: " ,
To fix it you need to modify the settings.json file of Windows Terminal (which you can open with keyboard shotrcut: Ctrl + ,). If you are like me you want it to start in your linux home directory /home/wes not your Windows home folder. I wanted to give the new Windows Terminal a go and the first thing I noticed is that when I open WSL in windows terminal it defaults to my home folder on Windows /mnt/c/Users/wes. Now that Windows 10 Slow Ring builds have WSL2 I've been doing more dev work on my Windows computer ( VS Code Remote WSL is really good y'all).
0 kommentar(er)
