Persistence of key bindings

Every major release I get a broken UX due to a shortcuts change. Furthermore, when I upgraded to 3.0 I’ve lost my favorite feature - export to clipboard as curl command.

But I found that in 3.0 we have commands and configurable key bindings. So I could solve my issue with them. I thought that way, but I was wrong - all bindings I’ve updated got lost as soon as I quited.

I had a quick peek into the source code, but the only explicit initialization of the keymap I found is defaultkeys.map(self.keymap) in master.py.

Is there a way to keep the changes in key bindings between restarts, that I’ve missed?

[cortesi]

Hi there. Unfortunately custom key binding persistence just didn’t quite make it into the 3.0 release. It’s a top priority for the next release, though, and I have everything ready for us to take the next step. There are two ways we could go about this:

• A keybindings.yaml file in the config directory dedicated just to key bindings.
• A more general mechanism that lets us specify a list of commands to run on startup. This would let us then use the console.key.bind command to add custom keybindings. I think I prefer this approach, which will extend to all addons and open a bunch of other doors as well.

If you felt like digging in, I’d love a hand with this. If not, you can expect this to land in master in the coming weeks, and be out in the 4.0 release around the beginning of May.

[cortesi]

I’ll close this ticket, and we can discuss any issues in more specific tickets.