Folke Lemaitre

I meant what is the error you get in lazy when it was building peek? Inside lazy, you can press `` to build a plugin. Report back with the error...

If it doesn't report an error, then build was succesful, so not a lazy issue. You'll need to debug this yourself....

I dont think this is a good idea. fyi, `dev` plugins are also **not** managed by lazy. Only remote plugins.

Allright, I'll think about it. But I'm very hesitant to add this since lazy's update code doesn't just do a `git pull`. It does a `git fetch` followed by `git...

Because of the reasons I listed above, I don't thing this is a good idea. Updating local plugins would also need another way to update them compared to remote plugins,...

I'm actually working on something like this, but I'm still not sure I should add it. More details soon. But it involves a new property `deactivate` which can be a...

It's not as simple as that, since you need to properly update the lazy loading handlers as well. Anyhow, the code to reload plugins is actually live already. It's just...

@idr4n you should not use `reload` for this purpose, that makes no sense. For lualine, you can just change the theme I believe. Other plugins typically have an autocmd that...

@lervag the reloading is a two step process. First lazy completely deactivates a plugin by removing any lazy handlers, unloading its lua modules and clearing `vim.g.loaded_....` for vim plugins. It...

clearing keymaps and autocmds should be handled by the plugin indeed, but in most cases that's not needed for a reload. After deactivation, the plugin is loaded again, meaning for...