Microsoft have come a long way in the past few years with Azure and embracing Linux as the developers’ choice. The main one being that I finally built myself a desktop PC and switched away from my trustworthy 7 year-old Macbook Air. I’ve also switched to Windows as my primary development environment due to variety of reasons. After restarting VSCode pressing Ctrl + Shift + C opens up a Windows Terminal (with Powershell in my case) instead of the normal console.Since writing Setting up Oh-my-Zsh, I’ve levelled up in terms of shell usage and customization. Of course you should add it to all the profiles/consoles you want to.Īnd that is it. "startingDirectory": "%_CD_%" // <- Add this line! For documentation on these settings, see: Thanks man! // To view the default settings, hold "alt" while clicking on the "Settings" button. I got that hint from Rick Strahl’s Blog ( ). You can now put the "startingDirectory": "%_CD_%" at the profiles you want to edit the startup directory. In there are the profiles which are currently active.
You can access it opening up a Windows Terminal Instance and Press Ctrl +, again. To let the terminal open up at the path you are at currently open up the profiles.json file of your Windows Terminal. This is of course my local PC, your path may differ. "": "C:\\Users\\Fabian\\AppData\\Local\\Microsoft\\WindowsApps\\wt.exe", Set the "" property to the path to the file wt.exe. To prepare VSCode open an instance and press Ctrl +, to enter the settings. What bothered me was: I love the new Windows Terminal but I wanted it to start as default when I use my preferred combination on my keyboard. I like to have the console in an external window and NOT inside my vscode instance so I often use the combination Ctrl + Shift + C to start an external console window at the folder I am currently with my vscode instance. In this blog post I want to write down how you can set the new windows Terminal as the default external console when working with VSCode.
0 kommentar(er)
