From: Hayk Avetisyan Date: Wed, 01 Jul 2026 11:46:50 GMT Subject: A bug Message-ID: Please, find the bug report attached. -- Kind Regards, *Hayk AvetisyanSenior Software Engineer* M +32 476 030611 • hayk.avetisyan@tvh.com *TVH PARTS HOLDING NV* Vichtseweg 129 • BE-8790 WAREGEM T +32 56 43 42 11 • F +32 56 43 44 88 • www.tvh.com -- **** DISCLAIMER  **** This message is delivered to all addressees subject to the conditions set forth in the attached disclaimer, which is an integral part of this message. Your privacy is important to us. We use your personal data only in compliance with data protection laws. For further information on how we process your personal data, please consult our Privacy Policy . By communicating with us, you unambiguously consent to our use of your personal data as explained in the Privacy Policy. The information contained in this communication may be confidential and may be subject to the attorney-client privilege. 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) In the last two Git for Windows releases (2.55.0 and the version immediately before it), Git Bash changed how it handles keyboard input while a long‑running Git command is executing. Previously, while a Git command was still running, you could already type the next command. When the running command finished, your pre‑typed command would appear correctly in the prompt, and you only needed to press Enter to execute it. In the recent versions, this no longer works correctly. If you type a command during the execution of a previous one — for example: "git rebase -i HEAD~3" — and the running command finishes while you are still typing, only the last part of your input appears at the Bash prompt. The beginning of the command is instead inserted into the Vim editor that opens for the interactive rebase. For example, if the previous command finishes right when you type the final part "AD~3", Bash will show only "AD~3". Pressing Enter results in an error such as: "Sorry, but such a command does not exist: 'AD~3'". After retyping and executing the full command again, Vim opens as expected. However, inside the rebase todo list, extra characters appear before the commit hash. For instance, a line that should be "pick ab54687" becomes "HEab54687". The inserted "HE" comes from the beginning of "HEAD~3". It appears inside Vim because the -i flag automatically puts Vim into insert mode, so the prematurely captured keystrokes are typed directly into the editor instead of the Bash prompt. In summary: When typing a command during the execution of a previous Git command, part of the input is incorrectly sent to Vim instead of remaining in Git Bash. What did you expect to happen? (Expected behavior) I expected the pre-typed command to appear once the current command was done. What happened instead? (Actual behavior) Instead the command was typed as a simple text in the VIM editor, once it went open. What's different between what you expected and what actually happened? The difference is that it corrupted the file, which was not expected. Anything else you want to add: 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.55.0.windows.1 cpu: x86_64 built from commit: bf5afdecc10478397d7059d07573630902fb2e2f sizeof-long: 4 sizeof-size_t: 8 shell-path: D:/git-sdk-64-build-installers/usr/bin/sh rust: disabled feature: fsmonitor--daemon gettext: enabled libcurl: 8.21.0 OpenSSL: OpenSSL 3.5.7 9 Jun 2026 zlib: 1.3.2 SHA-1: SHA1_DC SHA-256: SHA256_BLK default-ref-format: files default-hash: sha1 uname: Windows 10.0 26100 compiler info: gnuc: 16.1 libc info: no libc information available $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe [Enabled Hooks] post-checkout post-commit post-merge :re-push