Replies: 1 comment 3 replies
-
I am facing same problem, to elaborate with example: wk.add({
{ "<leader>x", function() require('which-key').show({ keys = "<leader>g", loop = true }) end },
}) The above works as expected, if I press wk.add({
{ "<leader>g", function() require('which-key').show({ keys = "<leader>g", loop = true }) end },
}) but it endlessly recurses and doesn't work. Is there something simple I am missing? |
Beta Was this translation helpful? Give feedback.
3 replies
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.
-
Hey everyone,
first of all, thanks for the big v3 update! It looks pretty impressive.
The following update enabling hydra-like mappings is what got me really interested in looking at my configuration again.
From what I got from the docs it's currently not possible to setup a trigger to be a hydra / looping mapping.
For example in mini.clue it's possible to map to be a recursive mapping. Each time a mapping is executed the trigger-mapping will be removed and the original mapping would be executed. Afterwards the trigger would be mapped and called again create a hydra-like use case.
Would that be possible for which-key triggers too?
Or is there something I just have missed to get this working without creating an recursion?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions