Enable mappings for different modes

[jgollenz]

This PR adds support for mappings in other modes than normal-mode, as discussed in #249 .

@kristijanhusak fyi I'm still working on the part concerning your vim.keymap.set example ;)

[kristijanhusak]

I think we should use this check:

type(mappings[category][name]) == 'table' and not vim.tbl_islist(mappings[category][name])

Because we have situation where we have a mapping that is a table list, but is actually a single normal mapping with an additional parameter, like this one

[jgollenz]

If I'm not mistaken that example should work regardless, because it should still go into the else branch (since the length operator would return non-zero) 🤔 But you are absolutely right, my check is ugly and I just didn't know how to do it properly 😁 Thanks a lot, will add the change :)

[kristijanhusak]

This looks good now. You will cover the other options also in this PR?

[jgollenz]

You will cover the other options also in this PR?

Yes, should find time for it this week

[jgollenz]

some_multi_mapping = {
    x = 'org_mappings.previous_visible_heading_visual', -- different function if needed. If not, use the same value as for normal mapping
    o = {'org_mappings.previous_visible_heading_operator', true }, -- pass down the arguments to a function if needed.
}

@kristijanhusak we could make the first mapping equal to x = { 'org_mappings.previous_visible_heading_visual' }, demanding it to be a table. That would make it more consistent with how the basic mapping works and remove one additional way to do things.

[kristijanhusak]

@jgollenz yeah, do that. More consistent is better.

[jgollenz]

@kristijanhusak sorry, it took a while. Should be working now

[kristijanhusak]

Looks good, thanks!