WIP: Feat/which key descriptions

[jgollenz]

closes #314

TODO

• multi-key rebinding
• basic rebinding (user passes a string, not a table)
• discuss descriptions

[jgollenz]

@kristijanhusak this should work. I need some confirmation on the descriptions I added

[kristijanhusak]

Descriptions look fine, I just don't know if which-key gives some context around mappings? If a mapping has description Earlier, will user see something like Orgmode - Earlier or something like that?

[jgollenz]

I just don't know if which-key gives some context around mappings? If a mapping has
description Earlier, will user see something like Orgmode - Earlier or something like that?

Hm, it doesn't look like that is possible via opts.desc alone. It is possible to explicitly markup o (or whatever) with orgmode. Mappings with multiple keys for lhs, are organized in a tree structure:

If nothing is declared for o or oi it will be displayed as +prefix. So no implicit context, unless we specify it

[kristijanhusak]

So no implicit context, unless we specify it

Ok, lets add it. I think it will be more useful if users know the context, especially if they override some of the <Leader>o mappings.

[kristijanhusak]

These mappings are really starting to complicate. Lets hold on this for a bit, I'll rewrite it today so it's more readable and testable. I'm worried we will break something with these changes.

[jgollenz]

These mappings are really starting to complicate

Absolutely. It's special cases galore. Didn't want to introduce any breaking changes, that's why I did it this way. Ideally, all the mappings have the same format. Right now there is ~5 different ways to do it

[jgollenz]

And as can be seen with the help overlay, things are already starting to break

[jgollenz]

new PR is #352