Hi David, On Wed, 9 Jul 2025, Preston, David J. wrote: > 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. This is essentially the same issue that has been reported at https://github.com/git-for-windows/git/issues/5632. The problem is in the MSYS2 runtime, which is the POSIX emulation layer required to run Bash that Git for Windows employed, which in turn is a friendly fork of the Cygwin runtime. I haven't had time to report this bug over in Cygwin yet (for which I would have to verify that this bug reproduces with their own Bash running in their own MinTTY). Maybe you can help out and install Cygwin (https://cygwin.com) and perform that test? Thanks, Johannes