User keybindings for profiles in the flyout should have priority over default keybindings #4175

Closed
opened 2026-01-30 23:40:08 +00:00 by claunia · 4 comments
Owner

Originally created by @linuxrebel on GitHub (Sep 30, 2019).

Example:

If I change the code for launching my Ubuntu instance from ctrl+shift+4 to ctrl+alt+u in the json, the UI still lists the original key combo in the UI. I feel that if it's available for modification, it should also reflect the new value.

Originally created by @linuxrebel on GitHub (Sep 30, 2019). Example: If I change the code for launching my Ubuntu instance from ctrl+shift+4 to ctrl+alt+u in the json, the UI still lists the original key combo in the UI. I feel that if it's available for modification, it should also reflect the new value.
Author
Owner

@zadjii-msft commented on GitHub (Sep 30, 2019):

Oh, this is tricky.

With the v0.5 change, when you add a keybinding for

{ "command": "newTabProfile3", "keys": ["ctrl+alt+u"] },

It doesn't remove the default "newTabProfile3" keybinding, which is still bound to ctrl+shift+4. Then when we go look up the text for the keybinding, it finds the default one first, and uses that keybinding.

We should probably make sure that user-defined ones are found first, right? Not sure if that's possible, considering it's an unordered map.

@zadjii-msft commented on GitHub (Sep 30, 2019): Oh, this is tricky. With the v0.5 change, when you add a keybinding for ```json { "command": "newTabProfile3", "keys": ["ctrl+alt+u"] }, ``` It doesn't _remove_ the default "newTabProfile3" keybinding, which is still bound to <kbd>ctrl+shift+4</kbd>. Then when we go look up the text for the keybinding, it finds the default one _first_, and uses that keybinding. We should probably make sure that user-defined ones are found first, right? Not sure if that's possible, considering it's an unordered map.
Author
Owner

@zadjii-msft commented on GitHub (Jun 25, 2020):

This similarly affects the bindings we display in the command palette.

@zadjii-msft commented on GitHub (Jun 25, 2020): This similarly affects the bindings we display in the command palette.
Author
Owner

@ghost commented on GitHub (Jan 28, 2021):

:tada:This issue was addressed in #8725, which has now been successfully released as Windows Terminal v1.5.10271.0.🎉

Handy links:

@ghost commented on GitHub (Jan 28, 2021): :tada:This issue was addressed in #8725, which has now been successfully released as `Windows Terminal v1.5.10271.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.5.10271.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Author
Owner

@ghost commented on GitHub (Jan 28, 2021):

:tada:This issue was addressed in #8725, which has now been successfully released as Windows Terminal Preview v1.6.10272.0.🎉

Handy links:

@ghost commented on GitHub (Jan 28, 2021): :tada:This issue was addressed in #8725, which has now been successfully released as `Windows Terminal Preview v1.6.10272.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.6.10272.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4175