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

Windows Terminal 1.1 breaks WinCompose input #9880

New Issue
Closed
opened 2026-01-31 02:06:34 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 02:06:34 +00:00
Owner
Copy Link

Originally created by @mordquist on GitHub (Jul 27, 2020).

Environment

Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 1.1.2021.0

Any other software?
Ubuntu 20.04 LTS (WSL2)
WinCompose v0.9.4 (https://github.com/samhocevar/wincompose/releases/tag/v0.9.4)

Steps to reproduce

  1. Start WinCompose and Windows Terminal (cmd, powershell, or WSL does not matter)
  2. Input any character using the WinCompose compose key
    e.g. rightAlt + o a

Expected behavior

The correct character ('å' in the above example) is sent to the terminal.

Actual behavior

Seemingly no character is sent, at least nothing is displayed.

Probably related to #6309 as setting "experimental.input.forceVT": true gives the expected behavior.

Originally created by @mordquist on GitHub (Jul 27, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.19041.0 Windows Terminal version (if applicable): 1.1.2021.0 Any other software? Ubuntu 20.04 LTS (WSL2) WinCompose v0.9.4 (https://github.com/samhocevar/wincompose/releases/tag/v0.9.4) ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Start WinCompose and Windows Terminal (cmd, powershell, or WSL does not matter) 2. Input any character using the WinCompose compose key e.g. `rightAlt` + `o` `a` # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> The correct character ('å' in the above example) is sent to the terminal. # Actual behavior <!-- What's actually happening? --> Seemingly no character is sent, at least nothing is displayed. Probably related to #6309 as setting `"experimental.input.forceVT": true` gives the expected behavior.
claunia added the Issue-BugArea-InputNeeds-Tag-FixProduct-TerminalPriority-1 labels 2026-01-31 02:06:34 +00:00
claunia commented 2026-01-31 02:06:35 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 27, 2020):

Huh. This doesn't exactly work in the traditional console either, and it was somewhat of a fluke that it worked in WT. It should, though.

This is what I get if I peek at the key events coming out of WC into the traditional console:

v 001 0010 002a 0000 ^@   00000010
^ 001 0010 002a 0000 ^@   00000000
v 001 0000 0000 00f6 �    00000000
^ 001 00e7 0000 00f6 �    00000000
^ 001 004f 0018 006f o    00000000

and here's what I'm getting over the tap:

␛[255;0;0;1;16;1_␛[255;0;0;0;16;1_

that 255 definitely ain't right

@DHowett commented on GitHub (Jul 27, 2020): Huh. This doesn't exactly work in the traditional console either, and it was somewhat of a fluke that it worked in WT. It _should_, though. This is what I get if I peek at the key events coming out of WC into the traditional console: ``` v 001 0010 002a 0000 ^@ 00000010 ^ 001 0010 002a 0000 ^@ 00000000 v 001 0000 0000 00f6 � 00000000 ^ 001 00e7 0000 00f6 � 00000000 ^ 001 004f 0018 006f o 00000000 ``` and here's what I'm getting over the tap: `␛[255;0;0;1;16;1_␛[255;0;0;0;16;1_` that 255 definitely ain't right
claunia commented 2026-01-31 02:06:35 +00:00
Author
Owner
Copy Link

@samhocevar commented on GitHub (Nov 26, 2020):

So, how should a third-party application send Unicode characters to Windows Terminal if SendInput() no longer works by default?

@samhocevar commented on GitHub (Nov 26, 2020): So, how should a third-party application send Unicode characters to Windows Terminal if `SendInput()` no longer works by default?
claunia commented 2026-01-31 02:06:35 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Nov 26, 2020):

As far as I can see, this issue was fixed in #7900. I'll close this issue for now as WinCompose works just fine on my end with the latest WT version.

The good thing is that I now finally understood, why we've been receiving weird key events, containing invalid scan codes, for third party applications employing SendInput: WT doesn't use TranslateMessage(Ex) properly. (I mean there's a very specific reason it doesn't... Namely the necessity to receive key events even for character keys.)

@lhecker commented on GitHub (Nov 26, 2020): As far as I can see, this issue was fixed in #7900. I'll close this issue for now as WinCompose works just fine on my end with the latest WT version. The good thing is that I now finally understood, why we've been receiving weird key events, containing invalid scan codes, for third party applications employing `SendInput`: WT doesn't use `TranslateMessage(Ex)` properly. (I mean there's a very specific reason it doesn't... Namely the necessity to receive key events even for character keys.)
claunia commented 2026-01-31 02:06:35 +00:00
Author
Owner
Copy Link

@mordquist commented on GitHub (Nov 30, 2020):

I can confirm that it works for me as well on Terminal 1.4 even with "experimental.input.forceVT" unset.

@mordquist commented on GitHub (Nov 30, 2020): I can confirm that it works for me as well on Terminal 1.4 even with `"experimental.input.forceVT"` unset.
claunia commented 2026-01-31 02:06:36 +00:00
Author
Owner
Copy Link

@smooth038 commented on GitHub (Apr 15, 2023):

I don't know if maybe this problem got recently reintroduced, but WinCompose currently does not work with any window terminal on my machine (cmd, powershell or windows terminal). When typing rightAlt ' a, it just outputs 'a and the compose key is ignored.

I tried the "experimental.input.forceVT" setting, but it doesn't seem to do anything.

Can anyone else reproduce this?

@smooth038 commented on GitHub (Apr 15, 2023): I don't know if maybe this problem got recently reintroduced, but WinCompose currently does not work with any window terminal on my machine (cmd, powershell or windows terminal). When typing `rightAlt` `'` `a`, it just outputs `'a` and the compose key is ignored. I tried the `"experimental.input.forceVT"` setting, but it doesn't seem to do anything. Can anyone else reproduce this?
claunia commented 2026-01-31 02:06:36 +00:00
Author
Owner
Copy Link

@smooth038 commented on GitHub (Apr 15, 2023):

I just found the problem. It didn't work because I was running the terminals in administrator mode, but WinCompose did not have admin privileges. When WinCompose is run as admin, everything works fine.

@smooth038 commented on GitHub (Apr 15, 2023): I just found the problem. It didn't work because I was running the terminals in administrator mode, but WinCompose did not have admin privileges. When WinCompose is run as admin, everything works fine.
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-Input Issue-Bug Needs-Tag-Fix Priority-1 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#9880
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?