Lazy loading on a keybind without making the keybind?

[gabevenberg]

Some (many) plugins set their own keybinds, such as toggleterm.nvim or nvim-surround. What would the ideomatic way to load those plugins on their keybinds be, would it just be to duplicate those binds in the keys={} section of the spec?

[BirdeeHub]

Yeah, but you dont have to set the action

It is enough to just do keys = { "<leader>idk", "<leader>hi" }

It will remove the trigger, load the spec (which will create the plugin's keybinds if it sets any), and then trigger the keysequence again after your spec hooks have ran, thus triggering the expected behavior of the keybind.

[BirdeeHub]

Oh, also to add to this, you can do this leaving out of rhs with the full spec form too if you want it to still have a description prior to being loaded in stuff like which-key

keys = {
  { "<leader>idk", mode = { "n" }, desc = "does something" } -- <-- full spec with no rhs
  "<leader>hi" -- <-- also you can mix and match both types
}

[BirdeeHub]

In order to get the info automatically, you would need to run the plugins first and see what keybinds they create.

Which obviously defeats the purpose of being lazy.

You could maybe hook up some crazy caching solution to run it once, figure them out, save it for next time unless stuff changed, but that would have to be an extension made by someone else because that is way more effort than it is probably worth.

In theory you could make a handler that does that but the cache invalidation sounds like a nightmare to get right.

[gabevenberg]

Yeah, but you dont have to set the action

It is enough to just do keys = { "<leader>idk", "<leader>hi" }

It will remove the trigger, load the spec (which will create the plugin's keybinds if it sets any), and then trigger the keysequence again after your spec hooks have ran, thus triggering the expected behavior of the keybind.

Thanks, thats what I was looking for.