Replies: 3 comments 1 reply
-
+1 from me. { "<leader>t", group = " Terminal", desc = " Terminal", nowait = true, remap = false, mode = { "n", "v" } },
... doesn't display group name, still |
Beta Was this translation helpful? Give feedback.
-
Here is how I did mine while keeping all my bindings I already had set in a bunch of plugin configs but I just wanted to name groups. It works for me. Just first define group for the main keybinding and the you can add subgroups also py just adding the next subgroup to the keybind with a description. So for example, in mine, I have 4 subgroups within my Telescope "page" so now when I hit leader I will see f: Telescope ,on first page, second page has all my keybindings and descriptions already setup before, plus i will see h: Harpoon, etc. for the subgroups. Hope this helps.
|
Beta Was this translation helpful? Give feedback.
-
This works for me. Based on the example snippet shown on the home page:
|
Beta Was this translation helpful? Give feedback.
-
Hello! Like what the title says how can I add group name to a key?
I've already looked answers in the internet but it seems whichkey.register() is already deprecated and
:checkhealth which-key
command recommends usingmapping = {}
spec but I don't have any idea how to do so since the which-key docs doesn't provide any example for reference and I don't find any similar issues regarding this.I'd like to add group name to Telescope plugin keys without making/adding keys at all since the keys are already defined in
Telescope plugin spec with
keys = {}
for lazyloading.Beta Was this translation helpful? Give feedback.
All reactions