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

Unexpected buffered Keyboard inputs #12178

New Issue
Closed
opened 2026-01-31 03:08:09 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 03:08:09 +00:00
Owner
Copy Link

Originally created by @SunghoLee on GitHub (Jan 25, 2021).

Environment

Windows build number: Windows 10 Home. 19041.746
Windows Terminal version: 1.4.3243.0

Steps to reproduce

I cannot reproduce this unexpected behavior, since I do not know the condition triggering it.

Expected behavior

Shell or other programs running on Windows Terminal recognize user keyboard inputs, and response for them immediately.

Actual behavior

User keyboard inputs look like being buffered, so shell or other programs running on Windows Terminal do not react for the inputs immediately. When typing some texts, the texts are shown on Windows Terminal as gray-scaled and underlined texts and they are actually recognized by the shell or programs after typing tab, arrows, and etc. This behavior makes me really inconvenient to use Vim or other text editors on Windows Terminal. I attached a GIF for the behavior.
issue

Originally created by @SunghoLee on GitHub (Jan 25, 2021). # Environment Windows build number: Windows 10 Home. 19041.746 Windows Terminal version: 1.4.3243.0 # Steps to reproduce I cannot reproduce this unexpected behavior, since I do not know the condition triggering it. # Expected behavior Shell or other programs running on Windows Terminal recognize user keyboard inputs, and response for them immediately. # Actual behavior User keyboard inputs look like being buffered, so shell or other programs running on Windows Terminal do not react for the inputs immediately. When typing some texts, the texts are shown on Windows Terminal as gray-scaled and underlined texts and they are actually recognized by the shell or programs after typing tab, arrows, and etc. This behavior makes me really inconvenient to use Vim or other text editors on Windows Terminal. I attached a GIF for the behavior. ![issue](https://user-images.githubusercontent.com/5790819/105685843-e6823680-5f39-11eb-87bf-24e92141cf60.gif)
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 03:08:09 +00:00
claunia commented 2026-01-31 03:08:10 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Jan 25, 2021):

Are you using an IME of some sort? This looks like what IME does.

@skyline75489 commented on GitHub (Jan 25, 2021): Are you using an IME of some sort? This looks like what IME does.
claunia commented 2026-01-31 03:08:10 +00:00
Author
Owner
Copy Link

@SunghoLee commented on GitHub (Jan 25, 2021):

@skyline75489, As you mentioned, an IME may introduce it, since I'm using an IME for Korean. But the same behavior does not occur on other terminals (cmd and powershell) except for Windows Terminal. I additionally attached a GIF for what I tested on the three terminals.
comp_issue

@SunghoLee commented on GitHub (Jan 25, 2021): @skyline75489, As you mentioned, an IME may introduce it, since I'm using an IME for Korean. But the same behavior does not occur on other terminals (cmd and powershell) except for Windows Terminal. I additionally attached a GIF for what I tested on the three terminals. ![comp_issue](https://user-images.githubusercontent.com/5790819/105689420-17646a80-5f3e-11eb-8fcb-e380170de06c.gif)
claunia commented 2026-01-31 03:08:11 +00:00
Author
Owner
Copy Link

@SunghoLee commented on GitHub (Jan 25, 2021):

@skyline75489, thank you for giving me insight to check this problem. After I disabled the IME that I'm using, the behavior was disappeared. I think that the Hancom Korean IME is not compatible well with Windows Terminal. I just removed the IME.. Thanks again! I close this issue.

@SunghoLee commented on GitHub (Jan 25, 2021): @skyline75489, thank you for giving me insight to check this problem. After I disabled the IME that I'm using, the behavior was disappeared. I think that the Hancom Korean IME is not compatible well with Windows Terminal. I just removed the IME.. Thanks again! I close this issue.
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 Needs-Tag-Fix Needs-Triage
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#12178
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?