-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: plugin spec cannot be read until renaming it #298
Comments
Thank you for reporting this! I defintely want to figure out what was causing all of this. If you now rename the file back to how it was, does everything still work? |
If I rename the file back to |
Can you try with the lastest version? I may have fixed this |
yep, now it works again. Thanks! |
Great, glad I found that one. thanks again for reporting! |
Did you check docs and existing issues?
Neovim version (nvim -v)
0.8.2
Operating system/version
macOS 13.0.1 (M1)
Describe the bug
Okay, so I am not really sure what the issue is here, so my apologies if this came up in a previous issue, I simply do not know under what terms I should search this problem.
From what I can tell, after one
:Lazy sync
, lazy seems to have stopped being able to read the file containing my plugin spec.I have ~30 plugins in the main module (
/lua/config/load-plugins.lua
) and another ~50 in submodules (/lua/config/load-plugins/*.lua
).After the:Lazy sync
run, lazy refused to recognize the ~30 plugins in the main module, and displayed only the number 50 as the number of total plugins. Not sure what caused that – rolling back tolazy.lock
did not fix it, deleting all plugins and bootstrapping the config again also did not solve this.Running a bare bones config with only
init.lua
,/lua/config/lazy.lua
, and/lua/config/load-plugins.lua
also did not work, in that state Lazy recognized only itself as the sole plugin listed and reported that the main module was not available.On a whim I tried renaming the file to
load-plugins2.lua
and also changed the respective line in lazy'ssetup()
call, and suddenly everything started working again.Maybe some sort of caching issue? While technically it works for me again now, I still wanted to report this since I am not really sure what caused this. (Also, this issue was a really scary one, since the problem even persisted when I checked out earlier versions of my dotfile directory, feeling as if nvim was unrecoverably broken until I figured it out)
Steps To Reproduce
not reproducible with the
repro.lua
The text was updated successfully, but these errors were encountered: