A command to remove cache

[ofseed]

Is your feature request related to a problem? Please describe.

Maybe because I do not delete packages packer downloaded,
lazy always loads plugins from the wrong path.

Describe the solution you'd like

If the cache was wrongly generated, It's hard to debug and find out what's wrong.
Maybe a command with the cache cleaning functionality is necessary.

[folke]

That should not be a problem, since lazy resets tha package path.

You can delete the cache at ~/.local/state/nvim/lazy/cache, but that should not be needed.

Can you give more details on what you're trying to achieve?

[ofseed]

After modifying the packer's configuration file to lazy's,
I deleted ~/.local/share/nvim/site/packer/, where the packer saves plugins.

Then, I found I could not require() any plugin in my configuration file before the UI started.
(manually loading them after entering neovim with require() usually works)

The error message shows that lazy loads plugins from site/packer/, which the packer uses
before. The message corresponds to lazy's source code file lua/lazy/core/cache.
So I realized lazy generated a cache with a wrong path.

After deleting ~/.local/state/nvim/lazy/cache, lazy works well.

What surprised me most was why lazy loaded plugins from the packer directory.

[folke]

That could only happen if the original rtp was still present. Should not happen with lazy's default settings. Did you change those?

[musjj]

Have you deleted ~/.config/plugin/packer_compiled.lua?

[folke]

that also should not cause issues, since I prevent that file from being loaded. But it must indeed be something like that what was happening.

Most likely the RTP path that contained other paths.

Did you have packadd packer still somewhere lingering?

[ofseed]

That could only happen if the original rtp was still present. Should not happen with lazy's default settings. Did you change those?

Neither

[ofseed]

I loaded packer_compile from a custom position, not sure whether it is important,
but I indeed manually deleted it.

This may be a hard-to-reproduce error, if you have no clue, you can close this issue first.

[folke]

ah yes, that would have been the problem. the packer compiled file would have updated the rtp, hence the behavior you noticed.

I prevent loading the default location of packer_compiled, but if you changed that, it would have still been loaded