Keybinding editor could be clearer #15357

Open
opened 2026-01-31 04:36:11 +00:00 by claunia · 3 comments
Owner

Originally created by @elsaco on GitHub (Sep 27, 2021).

Windows Terminal version (or Windows build number)

Windows Terminal Preview Version: 1.11.2421.0

Other Software

No response

Steps to reproduce

  • open terminal settings
  • in "Actions" add a new command

Expected Behavior

  • new command edit working

Actual Behavior

new command edit not working

This is an example trying to add the first drop-down option "Break into the debugger". The intended key cord was "alt+shift+b". Notice how "a", "l", "t" are echoed in the entry box, then when trying to add "+" it just show "shift+plus":

https://user-images.githubusercontent.com/3933920/134908242-c3c6dc01-eae0-477c-b28a-4586eda3d9a2.mp4

Originally created by @elsaco on GitHub (Sep 27, 2021). ### Windows Terminal version (or Windows build number) Windows Terminal Preview Version: 1.11.2421.0 ### Other Software _No response_ ### Steps to reproduce - open terminal settings - in "Actions" add a new command ### Expected Behavior - new command edit working ### Actual Behavior new command edit not working This is an example trying to add the first drop-down option "Break into the debugger". The intended key cord was "alt+shift+b". Notice how "a", "l", "t" are echoed in the entry box, then when trying to add "+" it just show "shift+plus": https://user-images.githubusercontent.com/3933920/134908242-c3c6dc01-eae0-477c-b28a-4586eda3d9a2.mp4
claunia added the Issue-TaskProduct-TerminalArea-SettingsUI labels 2026-01-31 04:36:11 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Sep 27, 2021):

Ah okay I see what's going on here. That's not a text entry field, you're supposed to just press the key chord you want to bind. So as you're typing alt, it's showing those keys one at a time. I think we've got an open issue already for making that more clear - something @carlos-zamora can link if he likes.

@zadjii-msft commented on GitHub (Sep 27, 2021): Ah okay I see what's going on here. That's not a text entry field, you're supposed to just press the key chord you want to bind. So as you're typing <kbd>a</kbd><kbd>l</kbd><kbd>t</kbd>, it's showing those keys one at a time. I think we've got an open issue already for making that more clear - something @carlos-zamora can link if he likes.
Author
Owner

@zadjii-msft commented on GitHub (Sep 27, 2021):

I'm reopening this to track the discussion we had as a team:

  • this box should automatically stop being in "edit mode" as soon as a non-modifier vkey is pressed
  • When modifiers are pressed/released in edit mode, then the box should show ctrl+shift+, and update in realtime

that'll help make this clearer

@zadjii-msft commented on GitHub (Sep 27, 2021): I'm reopening this to track the discussion we had as a team: * this box should automatically stop being in "edit mode" as soon as a non-modifier vkey is pressed * When modifiers are pressed/released in edit mode, then the box should show `ctrl+shift+`, and update in realtime that'll help make this clearer
Author
Owner

@DHowett commented on GitHub (Oct 5, 2021):

@lhecker and I had a discussion about this weeks ago, and I think we never filed an issue for it.

Thanks!

@DHowett commented on GitHub (Oct 5, 2021): @lhecker and I had a discussion about this weeks ago, and I think we never filed an issue for it. Thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15357