Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Integrated Terminal Performance Improvements

code.visualstudio.com

Post reply on HN
Print view View original

61–70 of 74 posts

Re: Integrated Terminal Performance Improvements

#61

Post by Tyriar »

lobster_johnson wrote: post #59
Tyriar wrote: post #57

Earlier quoted context omitted.

For excessive Code Helper CPU usage, you should be able to surface what the file/arguments were used to launch a Code Helper instance (how you do this depends on the OS). That will tell exactly which component is acting up, eg. TypeScript, search, terminal, extension, etc.

This may be a recent change? The last time I tried reporting excessive CPU usage, the Code Helper process didn't have any context info in the command line.

You find this through task manager on Windows, `ps aux | less` will work on macOS/Linux.

Re: Integrated Terminal Performance Improvements

#62

Post by anontrot »

I've been using VSCode for a while. I have this one issue with it, I couldn't figure out how to switch between the Terminal & the editor. Often I just (CMD+ Tab) to go to an independent terminal and execute some command. The only way I could figure out to do this within VSCode is "Contrl + ~", but have to do it twice if it's already open. So, does any of you know if there's an easy way of switching between the editor and the terminal?

Re: Integrated Terminal Performance Improvements

#63

Post by anontrot »

lobster_johnson wrote: post #53
Tyriar wrote: post #17

Earlier quoted context omitted.

Author of the blog post here. The standard shortcuts are ctrl+` for toggling the panel and ctrl+shift+` for creating a new terminal. This is what I use on top of that: { "key": "ctrl+`", "command": "workbench.action.terminal.focus", "when": "!terminalFocus" } This will focus the terminal if the focus is anywhere else, if the terminal is focused it will close it. You can add this one if you want ctrl+` to only toggle…

Last I checked, this only makes sense on US keyboards. On most non-US keyboards, the backtick requires option/alt and isn't practical as a shortcut.

I think you could just add a custom keybinding now that you know the commands.

Re: Integrated Terminal Performance Improvements

#64

Post by jordache »

batmansmk wrote: post #26
jordache wrote: post #3

Why are they focusing on this when there is a huge usability problem on osx + high res displays

You should file an issue, as we have no problem here on macOS 10.12 and high resolution displays. 20 developers using this setup.

The issue has been open for several months now...

Re: Integrated Terminal Performance Improvements

#66

Post by suswombat »

anontrot wrote: post #62

I've been using VSCode for a while. I have this one issue with it, I couldn't figure out how to switch between the Terminal & the editor. Often I just (CMD+ Tab) to go to an independent terminal and execute some command. The only way I could figure out to do this within VSCode is "Contrl + ~", but have to do it twice if it's already open. So, does any of you know if there's an easy way of switching between the editor…

If i understand you correctly this should help you, especially the answer by Tyriar. https://github.com/Microsoft/vscode/issues/12054

Re: Integrated Terminal Performance Improvements

#68

Post by anontrot »

suswombat wrote: post #66
anontrot wrote: post #62

I've been using VSCode for a while. I have this one issue with it, I couldn't figure out how to switch between the Terminal & the editor. Often I just (CMD+ Tab) to go to an independent terminal and execute some command. The only way I could figure out to do this within VSCode is "Contrl + ~", but have to do it twice if it's already open. So, does any of you know if there's an easy way of switching between the editor…

If i understand you correctly this should help you, especially the answer by Tyriar. https://github.com/Microsoft/vscode/issues/12054

Oh boy you just saved my ass, thank you!

Re: Integrated Terminal Performance Improvements

#69

Post by AlfeG »

w0utert wrote: 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++.

Re: Integrated Terminal Performance Improvements

#70

Post by w0utert »

chillee wrote: post #49
w0utert wrote: post #22

Earlier quoted context omitted.

My setup is just the official, latest release, with the Microsoft plugin for C++, the Vim bindings everyone uses, and one additional plugin for switching between header and source. I customized nothing besides a few keybindings and enabling neovim mode. This is on Ubuntu by the way. I also used VS code a little on macOS for web development, and to be fair, I didn’t run into any of these problems there. But that’s for…

Could you elaborate on what you mean by "the vim keybindings acting up"?

It just stops working and I cannot enter any text in the editor area anymore, even though all keyboard shortcuts and the terminal area still work. Enabling/disabling the extension fixes the problem, until it occurs again. I've disabled neovim mode for now, so far this seems to help but time will tell. Interestingly there is at least one bug open in the vscodevim issue tracker for the exact same problem, but it's closed because 'it hasn't been possible to reproduce this for a long time' :-/
Post reply on HN