英文:
Interrupt command (Control + C) no longer working in VS Code 1.79 terminal on macOS
问题
在我打开的每个终端顶部都会显示以下文本:“bash: no job control in this shell”。
我不记得在VS Code中做了任何更改,但现在我无法再使用“control + c”来停止终端中的操作(如“npm run dev”和“node app.js”)。
在我的计算机终端中仍然一切正常 - 只是VS Code出现了问题。
我尝试了一些方法,因为我在网上找不到关于这个确切问题的信息。我尝试了ChatGPT建议的一些配置更改,但都没有起作用。
英文:
At the top of every terminal I open is the text:
"bash: no job control in this shell"
I don't remember changing anything in VS Code but now I can no longer use 'control + c' to stop stuff in my terminal (like 'npm run dev' and 'node app.js')
Everything still works perfectly in my computer's terminal - it's just VS Code that's having issues.
I haven't tried much because I couldn't really find anything online about this exact issue. I tried ChatGPT, which told me to add some configurations to my settings.json file, but none of them worked.
答案1
得分: 1
I'm pretty sure this is a case of this open issue: MacOS: "no job control in this shell" #184713, which is affecting macOS users using VS Code 1.79. I suggest that you give that issue ticket a thumbs up to show that you have the issue, and subscribe to it to get notified about discussion and progress.
As a current workaround, others have found that the issue does not occur to them after downgrading to VS Code 1.78 or 1.77. Others have found that the issue goes away if they put export PROMPT_COMMAND="set -m"
in one of their bash startup files, such as ~/.bash_profile
.
It seems that none of the affected users who have reported their system info in that issue ticket are on a macOS version >= Big Sur. It's been suggested that the issue might be due to use of a missing posix_spawn api in the affected versions.
英文:
I'm pretty sure this is a case of this open issue: MacOS: "no job control in this shell" #184713, which is affecting macOS users using VS Code 1.79. I suggest that you give that issue ticket a thumbs up to show that you have the issue, and subscribe to it to get notified about discussion and progress.
As a current workaround, others have found that the issue does not occur to them after downgrading to VS Code 1.78 or 1.77. Others have found that the issue goes away if they put export PROMPT_COMMAND="set -m"
in one of their bash startup files, such as ~/.bash_profile
.
It seems that none of the affected users who have reported their system info in that issue ticket are on a macOS version >= Big Sur. It's been suggested that the issue might be due to use of a missing posix_spawn api in the affected versions.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库,让每个人都能够通过互相帮助和分享经验来进步。
评论