Live data from Hacker News

Integrated Terminal Performance Improvements

code.visualstudio.com

71–74 of 74 posts

Re: Integrated Terminal Performance Improvements

#71
post #25

Earlier quoted context omitted.

For 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

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. 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. F…

> 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.

Re: Integrated Terminal Performance Improvements

#72
post #13

Love the integrated terminal in VS Code! Great work by the team on this and appreciate the writeup. Curious what keyboard shortcut people use to move focus from editors to the Terminal and create new terminals? Anyone use tmux inside terminal?

I added the following to my keybindings.json file. It changes ctrl+` behavior to toggle open/close the terminal.

``` { "key": "ctrl+`", "command": "workbench.action.terminal.focus", "when": "!terminalFocus" } ```

Re: Integrated Terminal Performance Improvements

#73

Are there any macOS terminals like iTerm but with performance and resource efficiency as the top goals?

You can try Alacritty

Alacritty is extremely fast, but you need to use a terminal multiplexer like tmux or screen if you want commonly used features like tabs or scrolling. Which would be fine, except that both tmux and vim run significantly slower than expected in Alacritty on macOS; there's a performance bug somewhere.

Re: Integrated Terminal Performance Improvements

#74
post #69
post #11

I really wish Microsoft had used a different platform to build VS code on, like C#/Mono, Java, anything except Javascript/Electron basically. I just started using VS code for C++ development, trying to switch from Vim, an I basically like everything about the concept, but the execution and quality/polish of the software is mediocre at best. At least three times a day random stuff breaks: code completion stops working…

They have one - Visual Studio. It hang all time, crashes and painfully slow. Despite the fact that its written with C# and C++.

Downvoted - but it's true. I've using it for 10 years.
Post reply on HN