![]() ![]() Hyper is an open-source terminal built using Electron. One recommendation I received was Hyper.js. I have a dual-screen setup, and after coming from the world of Visual Studio, it felt very natural for me to use one screen for my code, and the second screen for other purposes such as debugging, terminals, problems and any other outputs I want to display.Īs a result, I started looking into using a standalone terminal for times when the VS Code integrated terminal isn't quite enough. One thing I wish would change, however, is the fact that you can't use VS Code across multiple monitors. In general, I find the integrated terminal perfectly adequate for what I need. You can find the rest of my VS Code key bindings in my dotfiles repo. Using ctrl + s as an example, it's actually used on 3 occasions, but only triggers on certain conditions that I have specified, making each command unique: ![]() One nice feature with VS Code is that you can add conditional factors for when a keybinding will trigger. You'll notice that some of the bindings I use are fairly common and likely taken by other commands, ctrl + s for example. You can set your own key bindings up by using ctrl + k ctrl + s, this will bring up the keybindings page. ctrl + shift + t - Switch focus from terminal pane to editor (and vice versa).ctrl + x - Toggle terminal pane being maximised.ctrl + down - Resize the terminal pane to make it smaller.ctrl + up - Resize the terminal pane to make it larger.I've tried to mitigate this to an extent by adding a few of my own key bindings to make the most out of the somewhat limited space: I personally find the size of the terminal restrictive. If you want to open additional terminals, you can do so with ctrl + shift + ' Once you've opened your project in WSL, you can open the terminal pane with ctrl + ' The natural choice when it came to using a terminal was to use the one integrated into VS Code. I predominantly operate within VS Code as part of any work and personal projects I'm doing. Over the time I've used WSL I've worked with a couple myself and wanted to tell you about my experiences with them, as well as how I configured them for WSL 2. In this post, I wanted to talk about setting up a standalone terminal for WSL 2. My previous post focussed on configuring Docker Desktop so that you could integrate seamlessly with WSL 2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |