starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Typed input is sometimes wrongly ordered #22185

New Issue
Open
opened 2026-01-31 08:05:56 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:05:56 +00:00
Owner
Copy Link

Originally created by @Vampire on GitHub (Aug 29, 2024).

Windows Terminal version

1.20.11781.0

Windows build number

10.0.19045.3930

Other Software

Bash from Git for Windows

Steps to reproduce

I cannot tell exactly how to reproduce.
But it happens regularly.
The prompt is not ready yet because it still executes the last command or evaluates the PROMPT_COMMAND of Bash.
Then I already type the next command like git b -a (b here is a Git alias for branch -vv).

Now regularly it happens that once the prompt is ready what is inserted is misordered, like agit b -, so the characters typed later are input before characters typed earlier.

I first thought I just mistyped, but I'm absolutely sure now, that I did not mistype, but the characters were not inserted in the order I typed them.
I guess there is some race condition somewhere that causes this.

Expected Behavior

Input appears in the order I typed it.

Actual Behavior

Input is mixed up.

Originally created by @Vampire on GitHub (Aug 29, 2024). ### Windows Terminal version 1.20.11781.0 ### Windows build number 10.0.19045.3930 ### Other Software Bash from Git for Windows ### Steps to reproduce I cannot tell exactly how to reproduce. But it happens regularly. The prompt is not ready yet because it still executes the last command or evaluates the `PROMPT_COMMAND` of Bash. Then I already type the next command like `git b -a` (`b` here is a Git alias for `branch -vv`). Now regularly it happens that once the prompt is ready what is inserted is misordered, like `agit b -`, so the characters typed later are input before characters typed earlier. I first thought I just mistyped, but I'm absolutely sure now, that I did not mistype, but the characters were not inserted in the order I typed them. I guess there is some race condition somewhere that causes this. ### Expected Behavior Input appears in the order I typed it. ### Actual Behavior Input is mixed up.
claunia added the Area-OutputIssue-BugProduct-Terminal labels 2026-01-31 08:05:56 +00:00
claunia commented 2026-01-31 08:05:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 4, 2024):

  • Does this repro outside of Git for Windows?
  • Did this repro on older versions of the Terminal?
  • What version of git for windows / bash/?

Our current hypothesis is that this is something weird that cygwin is doing, but it's hard/impossible for us to investigate without a more consistent repro

@zadjii-msft commented on GitHub (Sep 4, 2024): * Does this repro outside of Git for Windows? * Did this repro on older versions of the Terminal? * What version of git for windows / bash/? Our current hypothesis is that this is something weird that cygwin is doing, but it's hard/impossible for us to investigate without a more consistent repro
claunia commented 2026-01-31 08:05:57 +00:00
Author
Owner
Copy Link

@Vampire commented on GitHub (Sep 5, 2024):

Does this repro outside of Git for Windows?

I almost exclusively use Bash from Git for Windows as shell, so I don't know.

Did this repro on older versions of the Terminal?

I'm not 100% sure, but if it happened, then not that often that I felt like reporting it and I'm usually fast with reporting issues.

What version of git for windows / bash/?

Just updated 2 hours ago to 2.46.0.windows.1, I think it was 2.45.0.windows.1 before.
as I just upgraded it and did not do much work since then, I don't yet know whether it still reproduces.

Our current hypothesis is that this is something weird that cygwin is doing,

That's quite unlikely, as Cygwin is not at all involved. :-D
Git for Windows is MSYS-based, not Cygwin-based. :-)

it's hard/impossible for us to investigate without a more consistent repro

Totally understand that, I'm just not able to provide a better or more reliable reproduction recipe for this. :-(

@Vampire commented on GitHub (Sep 5, 2024): > Does this repro outside of Git for Windows? I almost exclusively use Bash from Git for Windows as shell, so I don't know. > Did this repro on older versions of the Terminal? I'm not 100% sure, but if it happened, then not that often that I felt like reporting it and I'm usually fast with reporting issues. > What version of git for windows / bash/? Just updated 2 hours ago to 2.46.0.windows.1, I think it was 2.45.0.windows.1 before. as I just upgraded it and did not do much work since then, I don't yet know whether it still reproduces. > Our current hypothesis is that this is something weird that cygwin is doing, That's quite unlikely, as Cygwin is not at all involved. :-D Git for Windows is MSYS-based, not Cygwin-based. :-) > it's hard/impossible for us to investigate without a more consistent repro Totally understand that, I'm just not able to provide a better or more reliable reproduction recipe for this. :-(
claunia commented 2026-01-31 08:05:57 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 5, 2024):

Git for Windows is MSYS-based, not Cygwin-based. :-)

Ah, but MSYS is itself Cygwin-based! 🙂

Image

@DHowett commented on GitHub (Sep 5, 2024): > Git for Windows is MSYS-based, not Cygwin-based. :-) Ah, but MSYS is itself Cygwin-based! 🙂 ![Image](https://github.com/user-attachments/assets/69d3fcd5-3317-4303-a7a6-2a9b86fe8db2)
claunia commented 2026-01-31 08:05:58 +00:00
Author
Owner
Copy Link

@Vampire commented on GitHub (Sep 30, 2024):

Ah, sorry, it seems I forgot that msys2 is a Cygwin fork.

Just updated 2 hours ago to 2.46.0.windows.1, I think it was 2.45.0.windows.1 before.
as I just upgraded it and did not do much work since then, I don't yet know whether it still reproduces.

Now I know that it still reproduces.

@Vampire commented on GitHub (Sep 30, 2024): Ah, sorry, it seems I forgot that msys2 is a Cygwin fork. > Just updated 2 hours ago to 2.46.0.windows.1, I think it was 2.45.0.windows.1 before. as I just upgraded it and did not do much work since then, I don't yet know whether it still reproduces. Now I know that it still reproduces.
claunia commented 2026-01-31 08:05:58 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 2, 2024):

Thanks! We think this is an issue with Cygwin, so we'll keep this open for now, but we'll touch base on it later.

@carlos-zamora commented on GitHub (Oct 2, 2024): Thanks! We think this is an issue with Cygwin, so we'll keep this open for now, but we'll touch base on it later.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Output Issue-Bug Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22185
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?