Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) When doing a git add --patch, I used the "e" option to edit a diff I couldn't split sufficiently. This worked, however when it moved on to the next diff, my keyboard became unresponsive. What did you expect to happen? (Expected behavior) Not make my keyboard unresponsive. What happened instead? (Actual behavior) I was unable to enter any option to proceed with the patch, and even Ctrl+C failed to kill the git command. I ended up having to close my Git Bash process and open a new one. What's different between what you expected and what actually happened? Keyboard unresponsive. Anything else you want to add: I've reproduced this every subsequent time I've tried this, and it's specific to using the "e" option with --patch. Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.42.0.windows.2 cpu: x86_64 sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Windows 10.0 19045 compiler info: gnuc: 13.2 libc info: no libc information available $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe [Enabled Hooks]
