howto get legendary & which-key to run with lazy

[svenXY]

Hi, in mrjones2014/smart-splits.nvim#135 (reply in thread) you said:

The which-key.nvim extension for legendary.nvim is dependent on load order if you want to auto-load items into both, unfortunately there isn't really any way around that. If you open a discussion on the legendary.nvim repo, we can go from there, but the tl;dr: is the order of operations needed to make the which-key.nvim extension work properly is:

1. which-key.nvim loaded by plugin manager onto Neovim's runtimepath, but do not load the keymaps yet
   

2. legendary.nvim loaded and initialized via require('legendary').setup(opts)
   

3. Register your keymaps with which-key.nvim, now that both plugins are ready, which-key.nvim items will be auto-loaded into legendary.nvim
   

so here it is ;-)

I have no idea on how to load which-key in lazy without the keymaps nor how to then load them in the end, I'm afraid

[mrjones2014]

So, if you're using lazy.nvim, you should be able to achieve that by something like the following:

{
  'mrjones2014/legendary.nvim',
  dependencies = { 'folke/which-key.nvim' },
  config = function()
    -- load which-key and setup config
    local wk = require('which-key')
    wk.setup(opts)
    -- load legendary and register which-key extension
    local legendary = require('legendary')
    legendary.setup({
      -- other opts here
      extensions = {
        which_key = { auto_register = true },
      }
    })
    -- register keymaps with which-key, now they will
    -- be auto-loaded into legendary as well
    wk.register(your_keymap_tables)
  end
}

[svenXY]

nope, still no success, I'm afraid.

I removed the wk.setup(opts) from legendary.lua and added a require('legendary') inbetween the last two lines of which-key.lua.

[mrjones2014]

Can you try restructuring it like I showed in the top comment?

[svenXY]

I can try.

Can I somehow load these opts and your_keymap_tables from the which-keys.lua file? I'd really like to keep them there.

Sorry, I'm not a lua developer...

[mrjones2014]

You could put them in a separate Lua module. Anything under ~/.config/nvim/lua will be available on runtimepath, so if you put them at, for example, ~/.config/nvim/lua/keymaps.lua then you would be able to require('keymaps')

[svenXY]

All right, this is much too complicated just for getting smart-splits to work - which was my initial problem. I have since solved this with normal keybindings.

As much as I like the idea of legendary, it is of not too much use for me without proper which-key integration, but the setup required here to get this to work is a bit too complicated for me, sorry. I was not initially looking for the functionality legendary provides and will most probably not miss not having it (especially since there is telescope support for mappings).

Thanks a lot for your support anyway.