Lazy loading conflicts about vapournvim HOT 6 CLOSED

The issue here is when a package is lazy-loaded, vim.cmd [[packadd ...]] needs to be used prior to require(). So what I may need to do is add vim.cmd [[ <pkg> ]] to Vapour.utils.plugins.require_if_installed() or something, because otherwise it'll just keep causing issues.

from vapournvim.

I think e67d293 fixes this for now. Maybe we can add a lazy load parameter to require_if_installed and if it is true then do vim.cmd('packadd ' .. pkg) or something like that?

from vapournvim.

I have implemented the checking for lazy loading in the require_if_installed function and tested it with treesitter and the markdown-preview.nvim plugin and it seems to be working fine.

from vapournvim.

I've tweaked the require_if_installed function slightly since I started realizing not all repos are the module names, which is a little annoying. But I'll port your changes as well over.

I didn't say this yesterday as I was exhausted by the time, but I think just part of the issue is some need to not be lazy-loaded, while others do.

Locally how I have it now is which-key is not lazy loaded, but for example NvimTree is. In the plugins conf it's loaded on :NvimTreeToggle command, so when I do <leader>e then it gets loaded without issue.

This might be a good safe way to go about this. Because doing packadd imo defeats the purpose of lazy-loading. I just couldn't get it to work any other way prior, but I think the above is a sane approach.

Another reason why I think this issue is such a thing is because even though these various packages are lazy-loaded, they're still trying to be loaded outside of their trigger scope if you will (event/cmd), which is causing the issues. So I'll work with that, as we should just need to edit the plugins file to config = function () require'...' end, which I've done in some situations already.

from vapournvim.

Now I get "which-key" not existing every time I start neovim. I am not sure if it is good or bad. Does this mean that it is getting lazy loaded?

from vapournvim.

Now I get "which-key" not existing every time I start neovim. I am not sure if it is good or bad. Does this mean that it is getting lazy loaded?

Yeah. I got that fixed in my modularize-vapour branch, the main thing I'm running into right now is auto-complete not working for some reason. So been trying to figure that out.

from vapournvim.