Integrating with legendary.nvim so keys
are registered with it?
#517
Unanswered
technicalpickles
asked this question in
Q&A
Replies: 1 comment 1 reply
-
First of all, your keymaps are wrong. You do something like: But it should be: In your keymaps, you can add descriptions, like so: {"<leader>xx", "<CMD>TroubleToggle<CR>", silent = true, remap = false, desc = "Toggle Trouble"} Whichkey automatically gets the description from the Neovim keymaps, so that's all you need. I don't use legendary, but it seems it integrates with WhichKey? If so, then adding the descriptions like above is all you need. If that's not how it works, then you should post a question there instead. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to setup legendary.nvim to have a command-palette like thing. Currently, I'm using plugin specs to define my
keys
which will lazy load plugins when the keys are used, for example:It also supports taking keys from
which-key
.I could imagine a few ways to do this:
keys
definitions to legendary's keys. the downside is that keys are all in one place if I want them to show upconfig
which does the normalsetup
and then setup with legendary (can its setup be called multiple times?) orrequire('which-key).register
The first is likely the easiest and most direct, but I'm hoping to have keys defined with their plugin.
Beta Was this translation helpful? Give feedback.
All reactions