How to use lazydev with NVIM_APPNAME sandbox?

[c-c-k]

I apologize If this question is stupid but I can't figure out how to configure Lazydev and LuaLS in a scenario such as:

I'm working IN:

• NVIM_APPNAME=nvim/main
• NVIM executable: /opt/nvim/main/bin/nvim
• NVIM config: ~/.config/nvim/main/
• NVIM Lazy plugins dir: ~/.local/share/nvim/main/lazy/

I'm working ON:

• NVIM_APPNAME=nvim/test
• NVIM executable: /opt/nvim/test/bin/nvim
• NVIM config: ~/.config/nvim/test/
  • Which is a symlink to: ~/Projects/nvim-test-config/
• NVIM Lazy plugins dir: ~/.local/share/nvim/test/lazy/

The problem I'm encountering is that Lazydev and LuaLS provide completion and diagnostics for the plugins and runtime library of the main NVIM instead of the plugins and runtime library of the test NVIM.

[Kayzels]

It should find the plugins relative to the Neovim that is actually being run. So, if you run NVIM_APPNAME=nvim/test, it will find the plugins for that. It uses the runtime for the current Neovim instance to find the files. So, it doesn't know that you are expecting a different version. You can run your test nvim config, while modifying it, and then it will find the plugins properly.

It also works the other way: if you opened your main config using your test config, it would use the test config for the runtime.

[c-c-k]

Thank you, after thinking about it some more I realized what I wanted was somewhat contradictory.

A big part of the reason for the nvim/test config is that while playing around with my configuration I often break it to the point that Lazy.nvim fails to load. In which case even if LazyDev were to somehow use the Lazy.nvim config from nvim/test (while running inside nvim/main) it would simply fail to load it.

I think I'm still missing something fundamental about the effective workflow for tweaking around one's Neovim configuration.
But for the moment the solution that I see is to use the exrc mechanism to add to LazyDev paths to plugins in the nvim/test data dir when I'm installing, checking out or upgrading them to a version that significantly differs from the one in the nvim/main data dir.