You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Terminal Key-Map Sets for/from iTerm & other Terminals #2205
This feature request was requested by an early-adopter of Terminal at a review meeting.
It'd be great if Terminal could implement a set of key-mappings that mimic most/many of iTerm's most common key-mappings.
This would help users who're already familiar with iTerm
We should also take a look at key mappings for other common Terminals and see if we can introduce "key-mapping sets" or preconfigured "key-maps" allowing the user to select and/or switch between key-maps on the fly, perhaps per-tab since some shells/apps/tools may be better suited to one set of key-maps than others.
If other Terminals store their key-mappings in settings/config, we could even permit importing of keymaps & converting them into Terminal key-mappings.
I think our unofficial plan has been to add support for "keymaps". This would follow the work for #1571 / #6899. Then, keymaps would contain objects which bind keys to various actions. The user could then just specify keymap: "foo" to replace all their keybindings with the ones in foo, no layering involved. Adding keys to actions directly would just update the "default" keymap, which is used when no keymap is specified.
Profiles could also just set a keymaprelatively easy then. That's still weird - different profiles having different keys for an app-level command like newTab, but hey, if that's what people want, that's what they get.
Activity
DHowett-MSFT commentedon Aug 5, 2019
Somebody has to spec this. Rich Turner (@bitcrazed), want to do the honors?
zadjii-msft commentedon Aug 19, 2019
Ooh this is a subset of #2237
zadjii-msft commentedon Jan 7, 2022
Documenting publicly for posterity:
I think our unofficial plan has been to add support for "keymaps". This would follow the work for #1571 / #6899. Then,
keymapswould contain objects which bind keys to various actions. The user could then just specifykeymap: "foo"to replace all theirkeybindingswith the ones infoo, no layering involved. Adding keys to actions directly would just update the "default" keymap, which is used when nokeymapis specified.Profiles could also just set a
keymaprelatively easy then. That's still weird - different profiles having different keys for an app-level command likenewTab, but hey, if that's what people want, that's what they get.