Conversation
|
Specifying key combinations rather than actions feels backwards – the user cares about how to do an action (eg. Quit = Ctrl-q), not necessarily what a specific key combination is bound to (Ctrl-q = Quit). (Although I realize doing it that way would be much trickier to implement.) |
…ers (&, |, ,) to avoid matching similarily named actions
Yep, currently
We should add a validator for this option, which checks for bindable actions, right? Edit: |
Dynamically display keybindings using a configurable string of actions:

Might be a good idea to also document this in the help page somewhere