Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interrupts in integrated terminal #49470

Closed
tom-programming opened this issue May 8, 2018 · 1 comment
Closed

Interrupts in integrated terminal #49470

tom-programming opened this issue May 8, 2018 · 1 comment
Assignees
Labels
terminal General terminal issues that don't fall under another label

Comments

@tom-programming
Copy link

Issue Type: Bug

1 Use Linux system. Open the integrated terminal and run "yes". I am assuming that the experience on the integrated terminal should be the same as with a regular terminal

2 Ctrl - C should send a SIGINT and stop the process. It doesn't (but it works somehow in "top")
3 Ctrl-\ should send a SIGQUIT and stop the process with a core dump, but it is masked by a keyboard shortcut that creates a new terminal tab. Even removing this shortcut no signal is sent (again it appears that it works in "top")

VS Code version: Code 1.22.2 (3aeede7, 2018-04-12T16:34:44.222Z)
OS version: Linux x64 4.4.0-121-generic

System Info
Item Value
CPUs Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz (12 x 3899)
Load (avg) 1, 1, 1
Memory (System) 31.34GB (13.77GB free)
Process Argv /usr/share/code/code --unity-launch
Screen Reader no
VM 0%
Extensions: none
@vscodebot vscodebot bot added the terminal General terminal issues that don't fall under another label label May 8, 2018
@Tyriar
Copy link
Member

Tyriar commented May 11, 2018

Depending on your hardware yes could run faster than the parser. Luckily a community contribution is currently in progress to boost the speed of the parser which should improve the situation xtermjs/xterm.js#1399

@Tyriar Tyriar closed this as completed May 11, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Jun 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
terminal General terminal issues that don't fall under another label
Projects
None yet
Development

No branches or pull requests

2 participants