Provide a means to dump / export all currently active keyboard shortcuts #20471

Open
opened 2026-01-31 07:14:48 +00:00 by claunia · 0 comments
Owner

Originally created by @sba923 on GitHub (Sep 13, 2023).

Description of the new feature/enhancement

It would be useful to be able to export / dump all currently active keyboard shortcuts (both the built-in ones and the ones defined by the user) to a file.

This would help, among others, in the following scenario:

  1. The user is running PowerShell within Windows Terminal
  2. The user wants to define a new keyboard shortcut using Set-PSReadLineKeyHandler, using the documentation at https://learn.microsoft.com/en-us/powershell/module/psreadline/set-psreadlinekeyhandler?view=powershell-7.3
  3. The user discovers that this doesn't work (e.g., the example that uses -Chord Ctrl+B)
  4. The user presumes that this might be related to Windows Terminal intercepting that shortcut
  5. The user looks for a "free" shortcut that is not used by Windows Terminal, and not already used by PSReadLine (the latter can be easily determined using (Get-PSReadLineKeyHandler).Key | Sort-Object -Unique)

Of course, this won't help determining shortcuts that are defined elsewhere than by Windows Terminal. But still, that would help IMVHO.

Proposed technical implementation details (optional)

Originally created by @sba923 on GitHub (Sep 13, 2023). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> # Description of the new feature/enhancement <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> It would be useful to be able to export / dump all currently active keyboard shortcuts (both the built-in ones and the ones defined by the user) to a file. This would help, among others, in the following scenario: 1. The user is running PowerShell within Windows Terminal 2. The user wants to define a new keyboard shortcut using `Set-PSReadLineKeyHandler`, using the documentation at https://learn.microsoft.com/en-us/powershell/module/psreadline/set-psreadlinekeyhandler?view=powershell-7.3 3. The user discovers that this doesn't work (e.g., the example that uses `-Chord Ctrl+B`) 4. The user presumes that this might be related to Windows Terminal intercepting that shortcut 5. The user looks for a "free" shortcut that is not used by Windows Terminal, and not already used by `PSReadLine` (the latter can be easily determined using `(Get-PSReadLineKeyHandler).Key | Sort-Object -Unique`) Of course, this won't help determining shortcuts that are defined elsewhere than by Windows Terminal. But still, that would help IMVHO. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 07:14:48 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20471