Automatically merge in new keybindings #3602

Closed
opened 2026-01-30 23:25:20 +00:00 by claunia · 3 comments
Owner

Originally created by @richardszalay on GitHub (Aug 28, 2019).

Description of the new feature/enhancement

When new key binding actions are added (eg. openNewTabDropdown in 0.4.2382.0), they're not particularly discoverable for upgrading users since they're not added to an existing settings file. It would be nice if new key binding actions were automatically added if they don't conflict with other bindings (and this behavior would probably need to be optional)

Proposed technical implementation details (optional)

Unclear, and I appreciate that this is much more difficult than it first appears since you'd really need to take into consideration what version they were on in order to determine which key binding actions are new and which were simply removed by the user.

Originally created by @richardszalay on GitHub (Aug 28, 2019). # Description of the new feature/enhancement When new key binding actions are added (eg. `openNewTabDropdown` in 0.4.2382.0), they're not particularly discoverable for upgrading users since they're not added to an existing settings file. It would be nice if new key binding actions were automatically added if they don't conflict with other bindings (and this behavior would probably need to be optional) # Proposed technical implementation details (optional) Unclear, and I appreciate that this is much more difficult than it first appears since you'd really need to take into consideration what version they _were_ on in order to determine which key binding actions are _new_ and which were simply removed by the user.
Author
Owner

@richardszalay commented on GitHub (Aug 28, 2019):

Feel free to close if this is inherently dealt with as part of #2515

@richardszalay commented on GitHub (Aug 28, 2019): Feel free to close if this is inherently dealt with as part of #2515
Author
Owner

@DHowett-MSFT commented on GitHub (Aug 28, 2019):

Yep, this is covered by #2515. Thanks!

@DHowett-MSFT commented on GitHub (Aug 28, 2019): Yep, this is covered by #2515. Thanks!
Author
Owner

@ghost commented on GitHub (Sep 24, 2019):

:tada:This issue was addressed in #2515, which has now been successfully released as Windows Terminal Preview v0.5.2661.0.🎉

Handy links:

@ghost commented on GitHub (Sep 24, 2019): :tada:This issue was addressed in #2515, which has now been successfully released as `Windows Terminal Preview v0.5.2661.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.5.2661.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?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#3602