How we can manage local plugins

[A7Lavinraj]

I know vim.pack allows your to package to point to a directory on your local machine but there is a problem(or atleast I am having this problem). vim.pack only checkout to last commit that was made in your local plugin but I want current changes everytime I restart my neovim.

I know this is related to vim.pack issue but since minimax also uses it I though that you can provide me some help.

Currently I am just adding my plugin to runtime path instead of using vim.pack.

[echasnovski]

The way vim.pack installs plugins is by downloading them into a dedicated "plugin package" directory (:h vim.pack-directory). Loading them is then can be done with :packadd plug-name.

The suggestion for "local" plugins is to follow a similar workflow: put a plugin in a dedicated (custom) plugin package and potentially load with :packadd my-local-plug. There are several ways to do this:

• Put such plugins directly into something like '~/.local/share/nvim/site/pack/mine/{start,opt}'. If put into 'start', then they will be loaded during startup. If 'opt' - execute :packadd my-local-plug.
• If you want to have a dedicated directory somewhere else, then create a symlink from that directory to a plugin package directory (like '~/.local/share/nvim/site/pack/mine' or to its 'start' / 'opt' subdirectory).

---

Since so called "local" plugins don't require management (no install since it is already on disk, no update since they assumed to be managed by the user, no delete since they were not installed via vim.pack), I don't think it is a high leverage to have vim.pack handle this sort of use case.

There is neovim/neovim#37727 that adds support for the "unmanaged" (what is called here "local") plugins, but as I said above and in that PR I am not really fond of adding this complexity.

---

Hope this helps.