Project based config using .nvim.lua

[Jezda1337]

Hi, I’ve searched for this topic before writing this, but none of the examples I found were helpful.

I have a plugin that reads a project-based config using vim.g. It checks for a config file in the cwd, and if it exists, it tries to read values from vim.g. The issue is that lazy.nvim loads plugins too early, before the project config is sourced. This forces me to manually load the config file using dofile(), which isn't ideal.

I’ve also tried using .lazy.nvim but ran into the same problem.

Is there a better way to handle this?

[iton0]

the init plugin spec may be what you need https://lazy.folke.io/spec#spec-setup

[Jezda1337]

I tried and it didn't help, I think this is for vim.g which is used inside init function not from .nvim.lua project file.

[dpetka2001]

Can you give an example with more concrete details as to what you're trying to achieve? Show the plugin spec of the plugin you're using along with the vim.g that it's using and the .nvim.lua file, so that I can try to test what happens.

From a quick test if you have a file .lazy.lua with contents

print("lazy")

return {}

and a file .nvim.lua with contents

print("exrc")

Then it will first print lazy and then exrc, which shows that the .nvim.lua file is loaded after .lazy.lua file, which makes sense because the .lazy.lua file is parsed during the parsing phase and loaded as the last plugin spec when the plugins load.

However, if you change .lazy.lua to

vim.schedule(function()
  print("lazy")
end)

return {}

then it will print exrc first and then lazy.

[Jezda1337]

So, I have build a plugin which can be configured from .nvim.lua in the project using vim.g variable.
So I'm looking for a way to avoid sourcing file manually here. Lazy actually init the plugin too early so I must source .nvim.lua and plugin/. The actual issue cumming from here and its not related to my plugin only who every want to use .nvim.lua for configuring smth will end up the same issue.

[dpetka2001]

I believe that if you don't load those files manually and you define vim.g.html_css in the init function of the plugin spec instead of .nvim.lua, it should work, no?

Unfortunately, .nvim.lua seems to load after the plugins setup it seems, so it seems to not be reliable to gather plugin spec related stuff from there.
Instead you could use the .lazy.lua provided by lazy.nvim to change the default values of your plugin on a per project basis, but that means it would be dependent on lazy.nvim and probably not compatible with other plugin managers.

Of course there might be a better solution I fail to think of. Sorry I couldn't be of more help.

Hopefully @folke might have a better solution and give feedback when he's back from his vacation.