How do I track bad plugins with Lazy? #545
-
|
This morning I opened neovim and was greeted with a blank terminal (literal void, nothing displayed at all). I assume one of my plugins is being a little shit but I don't have a great way of checking this with Lazy. Does Lazy have a sort of "debug" mode that can be set to log out its actions so I can see things like
etc etc? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
I actually broke lua loading errors in a recent commit. Just fixed that. So just update the lazy folder and you should again see the plugin that's causing issues |
Beta Was this translation helpful? Give feedback.
-
|
All is working now! That said, I do feel like my question could still be useful. Is what I asked about currently a feature of Lazy? If not, are you open to a PR for it? I have been procrastinating work on netman and logging is always good lol |
Beta Was this translation helpful? Give feedback.
-
|
With lazy, plugins can't break your setup. Lazy will still properly be loaded. But as I mentioned I had accidentally broke the lua loader. It wasn't returning errors anymore. So the feature is general Lazy behavior |
Beta Was this translation helpful? Give feedback.
-
|
Oh gotcha! Never mind then, I appreciate you :) |
Beta Was this translation helpful? Give feedback.
I actually broke lua loading errors in a recent commit. Just fixed that. So just update the lazy folder and you should again see the plugin that's causing issues