Hi folks! Shame on me, I didn't find this when I started up this extension. It's more like the inspector in that it can scale down to about a third of the screen, and listens for the keybindings to change and shows the list. Since the number of possible commands is large, this really helps cut down what you see at a given time:
Of course, it lies or is inaccurate (e.g. still shows command mode shortcuts in edit), has duplicates, is kinda ugly. But I use lab every day, and still learned some new commands from it.
Some other (variously poor) ideas I had were:
make new shortcuts (hooray, you already did it!)... started, but didn't finish!
sort by most/least frequently used, so that you can learn new shortcuts
when you start typing e.g. Ctrl, filter to commands that start that way
build entirely new commands from other commands (probably out of scope)
storing shortcuts in notebook meta (hi, i like to store everything in metadata) so you can share/reuse them
use the CSS selectors to to visually indicate the scope (might not be needed)
Happy to help, feel free to liberate my code (it's BSD-3), or I can whip up a PR
Hi folks! Shame on me, I didn't find this when I started up this extension. It's more like the inspector in that it can scale down to about a third of the screen, and listens for the keybindings to change and shows the list. Since the number of possible commands is large, this really helps cut down what you see at a given time:
Of course, it lies or is inaccurate (e.g. still shows command mode shortcuts in edit), has duplicates, is kinda ugly. But I use lab every day, and still learned some new commands from it.
Some other (variously poor) ideas I had were: