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

Terminal CTRL key is not working properly if Terminal was launched while Windows input language set to Russian #18800

New Issue
Closed
opened 2026-01-31 06:24:41 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:24:41 +00:00
Owner
Copy Link

Originally created by @Kadeluxe on GitHub (Nov 1, 2022).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.15.2874.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

  1. Set keyboard layout to Russian;
  2. Launch Windows Terminal;
  3. Try to press CTRL+C, CTRL+Z, anything while holding CTRL, for example, hold CTRL and press QWERTY.

Expected Behavior

CTRL key shortcuts work (CTRL+C, CTRL+U, etc)

Actual Behavior

Holding CTRL and pressing keys prints Russian letters instead of treating it as a shortcut.
Even if I switch to English layout, CTRL + <key> prints that letter from Russian layout.

In other words, if I launch WT while Russian layout is active, and then try to press CTRL+QWERTY inside Terminal, Terminal instead prints йцукен (these are Russian layout letters of the QWERTY keys) and it doesn't work like a shortcut at all.

WindowsTerminal_aEBahR2AW4

Originally created by @Kadeluxe on GitHub (Nov 1, 2022). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.15.2874.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce 1. Set keyboard layout to Russian; 2. Launch Windows Terminal; 3. Try to press CTRL+C, CTRL+Z, anything while holding CTRL, for example, hold CTRL and press QWERTY. ### Expected Behavior CTRL key shortcuts work (CTRL+C, CTRL+U, etc) ### Actual Behavior Holding CTRL and pressing keys prints Russian letters instead of treating it as a shortcut. Even if I switch to English layout, CTRL + \<key> prints that letter from Russian layout. In other words, if I launch WT while Russian layout is active, and then try to press CTRL+QWERTY inside Terminal, Terminal instead prints `йцукен` (these are Russian layout letters of the QWERTY keys) and it doesn't work like a shortcut at all. ![WindowsTerminal_aEBahR2AW4](https://user-images.githubusercontent.com/63540878/199204777-017ac00d-d9eb-4725-b45f-b45be54ea13d.gif)
claunia added the Issue-BugArea-InputResolution-ExternalProduct-Terminal labels 2026-01-31 06:24:41 +00:00
claunia commented 2026-01-31 06:24:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 15, 2022):

Are any of Ctrl+QWERTY bound in you settings?
The terminal typically avoids binging anything to Ctrl+key directly, and we prefer Ctrl+shift+key instead.

wait what, watching through to the second half of that gif, that's nuts.

Does this repro in PowerShell only, or does this happen in a Comman Prompt tab too?

Any idea if this is a recent regression? Did you happen to notice it on previous versions?

@zadjii-msft commented on GitHub (Dec 15, 2022): ~Are any of Ctrl+QWERTY bound in you settings? The terminal typically avoids binging anything to Ctrl+key directly, and we prefer Ctrl+shift+key instead.~ wait _what_, watching through to the second half of that gif, that's nuts. Does this repro in PowerShell only, or does this happen in a Comman Prompt tab too? Any idea if this is a recent regression? Did you happen to notice it on previous versions?
claunia commented 2026-01-31 06:24:42 +00:00
Author
Owner
Copy Link

@Kadeluxe commented on GitHub (Dec 15, 2022):

It seems that it only affects modern (?) PowerShell inside Windows Terminal. I use latest PowerShell now (7.3.1), it's still there.

I think I observed this for the first time months ago, like more than 6 months or something, maybe even more. I haven't used WT much so I forgot about it. Meanwhile I reinstalled the system, the gif in the first post is from pretty much fresh Windows installation.

Actually I tried to launch "Developer PowerShell for VS 2022" and there is no issue here. That PS version is 5.1.19041.2364 though. Not sure then, is it a PowerShell issue?

Just to be clear: it's not tied to QWERTY keys. Any key prints a respective character from Russian layout, despite input language being set to English.

@Kadeluxe commented on GitHub (Dec 15, 2022): It seems that it only affects modern (?) PowerShell inside Windows Terminal. I use latest PowerShell now (7.3.1), it's still there. I think I observed this for the first time months ago, like more than 6 months or something, maybe even more. I haven't used WT much so I forgot about it. Meanwhile I reinstalled the system, the gif in the first post is from pretty much fresh Windows installation. Actually I tried to launch "Developer PowerShell for VS 2022" and there is no issue here. That PS version is `5.1.19041.2364` though. Not sure then, is it a PowerShell issue? Just to be clear: it's not tied to QWERTY keys. Any key prints a respective character from Russian layout, despite input language being set to English.
claunia commented 2026-01-31 06:24:43 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 15, 2022):

That sure DOES sound like a PowerShell issue to me! Especially if it doesn't repro on 5.x, but does on 7.x.

There's probably two good places to report this, depending on a simple test. If you do a Remove-Module PSReadline, and the issue goes away, I'd report it to https://github.com/PowerShell/PSReadLine. Otherwise, I'd report this to https://github.com/PowerShell/PowerShell.

Thanks for following up!

@zadjii-msft commented on GitHub (Dec 15, 2022): That sure DOES sound like a PowerShell issue to me! Especially if it doesn't repro on 5.x, but does on 7.x. There's probably two good places to report this, depending on a simple test. If you do a `Remove-Module PSReadline`, and the issue goes away, I'd report it to https://github.com/PowerShell/PSReadLine. Otherwise, I'd report this to https://github.com/PowerShell/PowerShell. Thanks for following up!
claunia commented 2026-01-31 06:24:43 +00:00
Author
Owner
Copy Link

@Kadeluxe commented on GitHub (Dec 16, 2022):

It indeed starts to work if I do Remove-Module PSReadline. Interesting, thanks for clarifying!
Actually found this: https://github.com/PowerShell/PSReadLine/issues/2865

@Kadeluxe commented on GitHub (Dec 16, 2022): It indeed starts to work if I do `Remove-Module PSReadline`. Interesting, thanks for clarifying! Actually found this: https://github.com/PowerShell/PSReadLine/issues/2865
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 Product-Terminal Resolution-External
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#18800
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?