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

Ability to disable some dead keys #7989

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

Originally created by @gpotter2 on GitHub (May 7, 2020).

Description of the new feature/enhancement

Feature: Ability to disable SOME dead keys.

Motivation

It might be hard to understand for people who have sensible layouts, but many keyboard layouts have dead keys that are very cumbersome when programming.

I personally use the terminal on the daily, and the tilde ~ is used a lot in Linux. On my AZERTY default layout, ~ acts as a dead key: i need to type it then add a space to get a single ~. See the layout below
image
~ needs ALTGR + 2 + space. This is exhausting. We also have a dead ^ that could use this feature.

Notes

  • Ubuntu provides very useful layouts made for coders, that disable the cumbersome dead keys: https://askubuntu.com/questions/56560/what-exactly-is-meant-by-eliminate-dead-keys . Windows doesn't provide this natively, thus this feature request (I would never expect this to be added to the main OS...)
  • Some people will say they use ñ while coding, or ê. Even if the Terminal has great™️ support for UTF8, I'm not among them. I belive this is a tiny minority
  • I'm sure many people have that one dead key they wish they could get rid of. If this feature was builtin the terminal, it would allow a better coding experience for the people that only use those characters in the terminal anyways. This could also be profile based...

Do people also want that

For the user, It could be as simple a config value to disable dead keys using their key codes (?) such as

disable_dead_keys: [50]  # the 2/~ key code

Thanks a lot for you time, the Terminal is absolutely amazing and it just keeps getting better ! Cheers

Originally created by @gpotter2 on GitHub (May 7, 2020). # Description of the new feature/enhancement **Feature:** Ability to disable SOME dead keys. **Motivation** It might be hard to understand for people who have sensible layouts, but many keyboard layouts have dead keys that are very cumbersome when programming. I personally use the terminal on the daily, and the tilde ~ is used a lot in Linux. On my AZERTY default layout, ~ acts as a dead key: i need to type it then add a space to get a single ~. See the layout below ![image](https://upload.wikimedia.org/wikipedia/commons/thumb/b/b9/KB_France.svg/500px-KB_France.svg.png) `~` needs `ALTGR + 2 + space`. This is exhausting. We also have a dead `^` that could use this feature. **Notes** - Ubuntu provides very useful layouts made for coders, that disable the cumbersome dead keys: https://askubuntu.com/questions/56560/what-exactly-is-meant-by-eliminate-dead-keys . Windows doesn't provide this natively, thus this feature request (I would never expect this to be added to the main OS...) - Some people will say they use ñ while coding, or ê. Even if the Terminal has great:tm: support for UTF8, I'm not among them. I belive this is a tiny minority - I'm sure many people have that one dead key they wish they could get rid of. If this feature was builtin the terminal, it would allow a better coding experience for the people that only use those characters in the terminal anyways. This could also be profile based... **Do people also want that** - [Google for "disable dead keys"](https://www.google.com/search?q=disable+dead+keys+windows) - It seems the germans also have tons of dead keys: many articles try to workaround those: https://zauner.nllk.net/post/0014-windows-no-dead-keys/ For the user, It could be as simple a config value to disable dead keys using their key codes (?) such as ``` disable_dead_keys: [50] # the 2/~ key code ``` Thanks a lot for you time, the Terminal is absolutely amazing and it just keeps getting better ! Cheers
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 Area-TerminalControl Help Wanted Issue-Feature Needs-Tag-Fix Product-Terminal Resolution-Fix-Committed
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#7989
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?