![]() In the lower left hand corner of the screen on VS code youll see the icon which will. You can anyway see and change the current shortcut from Tools/Options/Environment/Keyboard. runInTerminal, set to false by default, that you can set to true. It’s really important The default shortcut is: Mac: Control + Windows: Ctrl + I changed it to: Mac: Command + Option + Windows: Ctrl + Alt + How to change: Search for Integrated Terminal in the keyboard shortcuts panel. (yes, that key press twice) (Which in fact worked better on my keyboard layout, since those keys are so much closer than Ctrl+\, so it becomes a one hand operation.) This keyboard shortcut opens and closes the Integrated Terminal. On my mixed Norwegian/English setup, the key press to start it up was Ctrl+|,Ctrl+|. By default, when the Terminal is launched it will: Set the working directory to the path of the current solution. Use the terminal command from the search bar. Trap: It should by default use the Ctrl+\,Ctrl+\, but that seems to depend on your Windows installation, probably localization. To open the Terminal: Use the Ctrl + keyboard shortcut with the backtick character to show or hide the Terminal window. Scott Hanselman has a nice blogpost on WhackWhack here, which also explains some of the background. You can download the Whack Whack terminal from the Visual Studio marketplace, and the project is open sourced at Github. It runs default with Powershell, and if you have installed Posh-git with your powershell, it also lights up inside WhackWhack, which is super cool! If you don’t know posh-git, it adds some cool extras to the command prompt for git, like shown above – you see the current branch and the git status straight off the command prompt and tab completes for commands and branches. Visual Studio Code has it’s own Terminal window built-in, so why not Visual Studio itself? Well, now it is here, a pre-pre tool called Whack Whack (named so because of how you open it). If you work with multiple Visual Studio at the same time, you loose track of which command window belongs to which Visual Studio instance. The Command Line extension has been a good substitute, but it opens up in a separate window. ![]() Visual Studio 2017 lack a proper internal terminal. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |