{"thread":{"id":"65904","subject":"A bug","startedAt":"2026-07-01T11:47:17Z","lastAt":"2026-07-01T12:53:10Z","messageCount":2,"participants":["Hayk Avetisyan","Kristofer Karlsson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"546881","messageId":"CACwZ3KFCJSqj-fwU8WH0=_53mPSZ-uaxdCcSuEEL7=eyJu4APw@mail.gmail.com","threadId":"65904","inReplyTo":null,"subject":"A bug","fromName":"Hayk Avetisyan","fromEmail":"hayk.avetisyan@tvh.com","sentAt":"2026-07-01T11:46:50Z","receivedAt":"2026-07-01T11:47:17Z","isPatch":false,"body":"Please, find the bug report attached.\n-- \n\nKind Regards,\n\n\n*Hayk AvetisyanSenior Software Engineer*\nM +32 476 030611 • hayk.avetisyan@tvh.com\n\n*TVH PARTS HOLDING NV*\nVichtseweg 129 • BE-8790 WAREGEM\nT +32 56 43 42 11 • F +32 56 43 44 88 • www.tvh.com\n\n-- \n\n\n**** DISCLAIMER \n<https://media.tvh.com/content/pdf/various/Email-disclaimer.pdf> ****\n\nThis \nmessage is delivered to all addressees subject to the conditions set forth \nin the attached disclaimer, which is an integral part of this message. Your \nprivacy is important to us. We use your personal data only in compliance \nwith data protection laws. For further information on how we process your \npersonal data, please consult our Privacy Policy \n<https://www.tvh.com/privacy-policy>. By communicating with us, you \nunambiguously consent to our use of your personal data as explained in the \nPrivacy Policy. The information contained in this communication may be \nconfidential and may be subject to the attorney-client privilege.\n\n\nThank you for filling out a Git bug report!\nPlease answer the following questions to help us understand your issue.\n\nWhat did you do before the bug happened? (Steps to reproduce your issue)\nIn 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.\n\nWhat did you expect to happen? (Expected behavior)\nI expected the pre-typed command to appear once the current command was done.\n\nWhat happened instead? (Actual behavior)\nInstead the command was typed as a simple text in the VIM editor, once it went open.\n\nWhat's different between what you expected and what actually happened?\nThe difference is that it corrupted the file, which was not expected.\n\nAnything else you want to add:\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n\n[System Info]\ngit version:\ngit version 2.55.0.windows.1\ncpu: x86_64\nbuilt from commit: bf5afdecc10478397d7059d07573630902fb2e2f\nsizeof-long: 4\nsizeof-size_t: 8\nshell-path: D:/git-sdk-64-build-installers/usr/bin/sh\nrust: disabled\nfeature: fsmonitor--daemon\ngettext: enabled\nlibcurl: 8.21.0\nOpenSSL: OpenSSL 3.5.7 9 Jun 2026\nzlib: 1.3.2\nSHA-1: SHA1_DC\nSHA-256: SHA256_BLK\ndefault-ref-format: files\ndefault-hash: sha1\nuname: Windows 10.0 26100 \ncompiler info: gnuc: 16.1\nlibc info: no libc information available\n$SHELL (typically, interactive shell): C:\\Program Files\\Git\\usr\\bin\\bash.exe\n\n\n[Enabled Hooks]\npost-checkout\npost-commit\npost-merge\n:re-push\n"},{"id":"546896","messageId":"CAL71e4NFn70P9npbppynrjKJuip71HGJwzOZf7ztR9cR6fAsqw@mail.gmail.com","threadId":"65904","inReplyTo":"CACwZ3KFCJSqj-fwU8WH0=_53mPSZ-uaxdCcSuEEL7=eyJu4APw@mail.gmail.com","subject":"Re: A bug","fromName":"Kristofer Karlsson","fromEmail":"krka@spotify.com","sentAt":"2026-07-01T12:52:56Z","receivedAt":"2026-07-01T12:53:10Z","isPatch":false,"body":"Hi, I looked briefly into the bug report and I am not at all\nan expert here but this seems more like an issue related to\nGit For Windows [1] than git core.\n\nThere is an issue that looks similar, maybe related? [2]\n\n- Kristofer\n\n[1] https://github.com/git-for-windows/git/issues\n[2] https://github.com/git-for-windows/git/issues/5632\n"}]}