-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
Ctrl-C doesn't terminate process in tmux inside VSCode terminal #46731
Comments
(Experimental duplicate detection) |
@joaomoreno @bpasero have you noticed ctrl+c not being responsive? |
@Tyriar no never, works fine. |
Same here. |
@Mellbourn for macOS we just send the shell (tmux) ^C (SIGINT) and let it handle it how it sees fit. Perhaps this is something related to your environment since @bpasero and @joaomoreno both run this setup and see no issues? |
@Tyriar strange. Ok, I'll try to investigate further on my own, to figure out why it is happening. Thanks for your time! |
@Mellbourn let us know if you find out more info. |
I have the setup that was described by João Moreno (@joaomoreno) in his blog post https://medium.com/@joaomoreno/persistent-terminal-sessions-in-vs-code-8fc469ed6b41
However, it seems to me that Control-C does not work as good as it used to.
It is particularly noticeable when I run
nodemon
. When I run it in tmux iniTerm
, I can exit the run without problem by using Control-C. If I runnodemon
inside tmux inside VSCode, I cannot. Instead it just renders^C
in the terminal window.Strangely, the problem is intermittent. Restarting VSCode sometimes help.
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: