-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Git Bash Terminal input is blocked after edit #193809
Comments
Just cross-checked, it doesn't happen with the default Command Prompt. It's some issue related to the Git mintty. |
I cannot repro this with Git Bash, does this still occur reliably for you? |
Yes it does. The profile config looks default too. It auto-detected the git bash and I can directly open it inside VSCode. |
I'm also having this exact issue. VS Code 1.92.1, Git 2.46.0 |
I also can't reproduce so unfortunately this isn't actionable and closing. Something that could improve this you could try is to move to the new backend on Windows by setting |
Unfortunately |
Ah good hint, it works in a separate Git Bash, but not when opening the git bash in Windows Terminal. |
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
I'm using a Git Bash Terminal (https://gitforwindows.org/ 2.42.0.2 with default install options) inside VSCode and the git setting
git config core.editor 'code --wait'
.When I run
git add -p
and then entere
it correctly opens the patch in the same VSCode window for editing and after closing progresses in the terminal to the next hunk.Scrolling etc is still possible but it doesn't accept any input anymore.
Ctrl+C etc has no effect. The only way to exit this deadlock is to kill the terminal, but that also leaves the git index untouched.
The text was updated successfully, but these errors were encountered: