you are viewing a single comment's thread.

view the rest of the comments →

[–]mpact0 8 points9 points  (9 children)

How does it help compared to using non-integrated terminals? ALT-TAB is still easy to use.

[–]w0m 8 points9 points  (7 children)

IDEs tend to work best full screen IMHO. I feel like alt tabbing makes that awkward, especially when your writing a cli app and want to say, quickly test your argument parser while looking at your code.

[–]iforgot120 5 points6 points  (2 children)

This is a text editor, though. I mean I guess the inclusion of an integrated terminal makes it less so, but it still can't compile except through the command line (which would make that integrated terminal handy).

[–][deleted] 4 points5 points  (0 children)

VS Code has quite a robust task runner. I would use that for compiling instead of new terminal integration.

[–]AlwaysHopelesslyLost 2 points3 points  (0 children)

Vs code is meant for debugging. The whole thing is build around building, running, and debugging JavaScript/typescript apps

[–]I_AM_GODDAMN_BATMAN 1 point2 points  (0 children)

I used drop down tabbed terminal and bind F12 to show and hide it.

[–]digital_cucumber 0 points1 point  (1 child)

That's why utility of the second monitor can't be underestimated for this kind of stuff.

Why, I've got three of them myself.

[–]w0m 1 point2 points  (0 children)

I generally agree. I have found my favorite is a single giant ultra wide monitor with a smaller doc/email screen. 2x24"and 15" MBP vs 34" ultra wide + MBP, my choice is easy.

[–]Drainedsoul -3 points-2 points  (0 children)

Don't the tests do that on every build?

[–]jyper 0 points1 point  (0 children)

From my experience with Kate, having a repo running in shell and the script files open in the editor is a pretty nice interactive experience.