3 ms·
What's the case for using the terminal in VSCode? I use a modern multitasking computer where VSCode is in one area or screen and my terminal in another (and oth
by Waterluvian 9y ago
What's the case for using the terminal in VSCode? I use a modern multitasking computer where VSCode is in one area or screen and my terminal in another (and other things in others).
By using my own terminal I get to keep everything custom about that terminal rather than having another one.
Surely there's reasons that I'm missing?
Edit: thanks for all the responses. A lot of great new things I didn't think of before!
- nwrk 9y agoFor example, you can use linter in terminal which makes click on output messages interactive -> going directly to source code. edit: quick youtube example how it works together https://www.youtube.com/watch?v=cMrDePs86Uo https://www.youtube.com/watch?v=cMrDePs86Uo
- simlevesque 9y agoThis is a real time saver.
- lobster_johnson 9y agoWouldn't it be better to run the linter in the background and have the editor mark the problem lines? I have keyboard shortcuts bound to "next marker" and "previous marker" so I can jump to the next problem. They don't work across an entire workspace, sadly, and I have an outstanding Github issue about it that has not seen any activity for years. Project-wide linting is something that VSCode really lacks right now. For example, it's easy to change something in one file that breaks another file, but you won't get any error markers until you go to the broken file.
- jamesgeck0 9y ago> Wouldn't it be better to run the linter in the background and have the editor mark the problem lines? I have keyboard shortcuts bound to "next marker" and "previous marker" so I can jump to the next problem. The ESLint plugin does both these things; linting is just an example. I use the terminal's click-to-open file feature for opening files that have have merge conflicts during git rebase, and for opening spec files that failed. It's just handy to have.
- celim307 9y agoFor me it's keeping things organized in my mindspace. When I tab to a VS window, it has my code right there alongside it's relevant git cli and server output. Helpful when I'm running a lot of services locally or simultaneously adding code to a package and using it locally with npm link in a different codebase, before publishing. With something like iterm it's a little more sluggish to remember which tile corresponds to which codebase, especially when it's spitting out a lot of logs and obscures it's current directory
- batmansmk 9y ago- You open a project, the terminal is already set in the working directory of your project. It saves you to have to cd to the right directory. - When you debug, you see the logs of your server at the same time as the stack trace, the breakpoints without having to play with the windows. - you can put in the vscode project some developers command, like linting, building, launching in debug mode... adding buttons to your interface to run them. - No need to start two programs, close two programs that you always use together.
- epicide 9y agoAs someone who regularly has several browser-based projects open, it's nice having a small part of the window that shows the current progress of the build. I've gone back and forth using a "normal" terminal and using the one in VSCode. I often end up using the latter since it keeps the build progress with the proper project. Having the project folder as the CWD automatically is a really nice time saver, too.