starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[PR #15590] (WIP) Reset to alphabet input mode on <Escape> or <Enter> key #30679

New Issue
Open
opened 2026-01-31 09:42:16 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:42:16 +00:00
Owner
Copy Link

Original Pull Request: https://github.com/microsoft/terminal/pull/15590

State: closed
Merged: No

Summary of the Pull Request

When pressing <Escape> or <Enter> key, reset (CJK) keyboard IME input state to alphabet input mode.

References and Relevant Issues

Adds new feature:
#1304 Feature Request: IME mode after pressing Escape or Enter key in CJK input.

Detailed Description of the Pull Request / Additional comments

  • Use case: CJK user types shell command line using CJK input IME, or edits text file using Linux text editors like Vim (vi), nano or emacs editor.
  • Problem: After typing CJK words and phrases in CJK-script composition mode, user have to manually exit CJK input mode by pressing the composition key again and return to alphabet input mode. All shell commands and editor commands are alphabet/English word or key. So, CJK input after <Escape> or <Enter> key always causes command error. It is very error-prone and very, very annoying.
  • Solution: This PR solves such annoyance by switching IME input mode to alphabet input mode automatically upon pressing <Escape> or <Enter> key. This can be turned on/off at terminal/interaction setting pane.
  • Caveats: To type multi-line CJK phrases, user have to press CJK composition key after pressing each <Enter> key to go next line.
  • TODO: Setting toggle switch works as expected. Done.

Validation Steps Performed

This feature is widely supported in many open-source or commercial CJK-aware terminal emulator/SSH/Telnet client software or editors like Korean-localized xterm, hanterm, iPuTTY, XShell, and some MinTTY. It is such universally requested feature for Korean command line users.

PR Checklist

  • Closes Build Issues (#1304)
  • Tests added/passed
  • Documentation updated
    • If checked, please file a pull request on our docs repo and link it here: #xxx
  • Schema updated (if necessary)
**Original Pull Request:** https://github.com/microsoft/terminal/pull/15590 **State:** closed **Merged:** No --- ## Summary of the Pull Request When pressing \<Escape> or \<Enter> key, reset (CJK) keyboard IME input state to alphabet input mode. ## References and Relevant Issues Adds new feature: #1304 Feature Request: IME mode after pressing Escape or Enter key in CJK input. ## Detailed Description of the Pull Request / Additional comments * Use case: CJK user types shell command line using CJK input IME, or edits text file using Linux text editors like `Vim (vi)`, `nano` or `emacs` editor. * Problem: After typing CJK words and phrases in CJK-script composition mode, user have to manually exit CJK input mode by pressing the composition key again and return to alphabet input mode. All shell commands and editor commands are alphabet/English word or key. So, CJK input after \<Escape> or \<Enter> key always causes command error. It is very error-prone and very, very annoying. * Solution: This PR solves such annoyance by switching IME input mode to alphabet input mode automatically upon pressing \<Escape> or \<Enter> key. This can be turned on/off at terminal/interaction setting pane. * Caveats: To type multi-line CJK phrases, user have to press CJK composition key after pressing each \<Enter> key to go next line. * TODO: Setting toggle switch works as expected. Done. ## Validation Steps Performed This feature is widely supported in many open-source or commercial CJK-aware terminal emulator/SSH/Telnet client software or editors like Korean-localized `xterm`, `hanterm`, `iPuTTY`, `XShell`, and some `MinTTY`. It is such universally requested feature for Korean command line users. ## PR Checklist - [ ] Closes #1304 - [ ] Tests added/passed - [ ] Documentation updated - If checked, please file a pull request on [our docs repo](https://github.com/MicrosoftDocs/terminal) and link it here: #xxx - [ ] Schema updated (if necessary)
claunia added the pull-request label 2026-01-31 09:42:16 +00:00
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 pull-request
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#30679
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?