git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git bash bug

From
PJPreston, David J. <david.preston@onegas.com>
Date
Jul 9, 2025, 17:20 UTC
Message-ID
<PH7PR11MB65466DEE20BA470C600C7B9B9549A@PH7PR11MB6546.namprd11.prod.outlook.com>
Bug report attached.

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) started happening after an update to a newer version of git... has been happening for a while, so i am not sure what version it started with

What did you expect to happen? (Expected behavior) when using git bash in windows environment, when a previously typed command is executing and i start typing, i expect that what i type will eventually show up on the command line, in the order i typed it, once the executing command completes.

What happened instead? (Actual behavior) letters that i have typed show up in a different order than i typed them. basically, i think there is some async processing going on, and keyboard input is being handled in such a way that the keystrokes are output to the console in an order that is random based on race conditions in the async code.

What's different between what you expected and what actually happened? keys output in a different order than i typed them in.

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.49.0.windows.1
cpu: x86_64
built from commit: cca1f38702730b35f52c29efd62864b85e85ddcc
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
feature: fsmonitor--daemon
libcurl: 8.12.1
OpenSSL: OpenSSL 3.2.4 11 Feb 2025
zlib: 1.3.1
uname: Windows 10.0 22631 
compiler info: gnuc: 14.2
libc info: no libc information available
$SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe
[Enabled Hooks]
Next: brian m. carlson
Message 1 of 3 in “git bash bug”
  1. Preston, David J.Jul 9, 2025
  2. brian m. carlsonJul 9, 2025
  3. Johannes SchindelinJul 11, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.