Settings (override) per profile? #12725
-
Are you considering supporting a settings.json per profile to augment or override the global settings? Please excuse me if this is in the roadmap or features request already, I couldn't find it easily. This tool is AWESOME, I love it. Thank you |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I think you're specifically looking for #5790, which we're using to track "profile-specific keybindings". It's not really on the roadmap at the moment. We kinda need to figure out global actions (#6899), and also keymaps (#2205). Once those two are done, we need to figure out what layering keymaps looks like. Like, presumably there's a default keymap that ships with the terminal, but you probably don't want to start with nothing when authoring a new keymap. Like, you probably want to just start from the default keymap and make some modifications. So the spec for that is a bit complicated. Since it's got a bit of prerequisite work we haven't really gotten around to committing it to a timeframe yet. For more discussion I'd follow up in #5790. |
Beta Was this translation helpful? Give feedback.
I think you're specifically looking for #5790, which we're using to track "profile-specific keybindings". It's not really on the roadmap at the moment. We kinda need to figure out global actions (#6899), and also keymaps (#2205). Once those two are done, we need to figure out what layering keymaps looks like. Like, presumably there's a default keymap that ships with the terminal, but you probably don't want to start with nothing when authoring a new keymap. Like, you probably want to just start from the default keymap and make some modifications.
So the spec for that is a bit complicated. Since it's got a bit of prerequisite work we haven't really gotten around to committing it to a timef…