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!
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!
edit: quick youtube example how it works together https://www.youtube.com/watch?v=cMrDePs86Uo
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.
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.
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.
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
- 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.