vscode: ctrl+c doesn't exit commands in terminal

Does this issue occur when all extensions are disabled?: yes

  • VS Code Version: 1.79.0 (07/06/2023) (3 days ago)
  • OS Version: OSX 10.14.16

Steps to Reproduce:

  1. In the vscode terminal (any terminal, bash zsh, it doesn’t matter)
  2. Run a command - sleep 10 for example - then immediately press ctrl+c
  3. and it doesn’t exit that command

It’s been like that for more than a month now, what are you guys doing 😅

2023-06-11 14 52 02

There is no error in console like https://github.com/microsoft/vscode/issues/181939 thus why I created this issue

Version: 1.79.0 Commit: b380da4ef1ee00e224a15c1d4d9793e27c2b6302 Date: 2023-06-07T14:29:00.206Z (3 days ago) Electron: 22.5.5 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: 10.8.168.25-electron.0 OS: Darwin x64 18.7.0

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 36
  • Comments: 21 (7 by maintainers)

Most upvoted comments

Also have you manually installed shell integration? Check your .zshrc/etc. scripts

ctrl+c works as expected on the osx terminal app, which uses zshrc as well

I did tried removing my .zshrc file to see it that was the cause but beside changing the theme of the terminal and name format, the ctrl+c remains unsuccessful

does disabling shell integration via terminal.integrated.shellIntegration.enabled fix it?

I tried set to false, restarted terminal, or even vscode, no change…

I rollback to 1.77.3 to resolve this problem

This issue is not solved why do you always close related issues

I rollback to 1.77.3 to resolve this problem

thanks buddy, it works.

same the issue with me on macOS Mojave 10.14.6, This question has been bothering me for a month。 @Tyriar @meganrogge Version: 1.79.1 Commit: 4cb974a7aed77a74c7813bdccd99ee0d04901215 Date: 2023-06-12T16:16:49.215Z Electron: 22.5.7 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: 10.8.168.25-electron.0 OS: Darwin x64 18.7.0 Sandboxed: Yes

does disabling shell integration via terminal.integrated.shellIntegration.enabled fix it?