-
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
feature: ability to continue loading other plugins when one fails #349
Comments
This is already the case? If you still encounter issues with this, please provide an example where config if plugin prevents loading of other plugins. |
It's related to issue #348, where an error with |
Thats just standard Neovim behavior with |
Ahh I see. Sorry for the confusion and thanks for the help! |
Update: it seems when the error isn't from the config function itself, but from a lazy-issued spec check, other plugins don't get loaded. For example, the following error disables my dressing.nvim loading (VeryLazy).
|
p.s. also on that note, not sure why barbar.nvim's lua module of "bufferline" doesn't get detected. |
Can you provide a minimal Bufferline doesn't get detected because there's both a What do you mean eactly with a lazy-issued spec check? What you are seeing is just a |
That stacktrace is also super weird. It doen't really make sense. Seems related to LazyVim/starter#5 somehow. I see a similar stacktrace there |
I can reproduce that stacktrace. Checking what's wrong here. Super weird |
I was able to fix the weird error. It was triggered becuase I did The fix was to use Lazy now also correctly de-duplicates plugin mods, so the |
Perfect thank you so much for the painful debugging and the fix! Appreciate it a lot 🎉🎉 |
Did you check the docs?
Is your feature request related to a problem? Please describe.
When a plugin's config errors out, other plugins may not be loaded. As such, users are unable to use the benefits of other plugins to resolve config issues with that plugin(s).
Describe the solution you'd like
Warn or display the error and which plugin it's from, and continue loading the other plugins. I've done something similar before for packer.nvim using protected calls and it resolves this issue completely: https://github.com/axieax/dotconfig/blob/28f46b2353e5496e666c4a5a9d26ee4c30fe1cbf/nvim/lua/axie/plugins/packer.lua#L46-L52
Describe alternatives you've considered
Using an alternative text editor to resolve minor config issues in the case of an infinite loop
Additional context
No response
The text was updated successfully, but these errors were encountered: