These are two somewhat different requests, at two quite distinct levels of complexity:
- @pbattersby’s is simpler, as it only requires remapping (i.e. reconfiguring) already existent shortcuts; @itplainedge’s requires creating new mappings, and with sequences of functions no less.
- @pbattersby’s only requires giving users write access to the keyboard shortcut table (and the UI components to do so); @itplainedge’s requires some sort of macro language and/or recording to create sequences of steps, and finally assign them a hotkey.
Fortunately, there are workarounds for both of them, so users don’t have to wait for the day these get implemented (if at all!):
- @pbattersby’s can be solved with a key remapper;
- @itplainedge’s can be solved using AutoHotKey (on Windows, or similar on other OS’s).