docs(pack): document $XDG_DATA_HOME/nvim/site presence in 'packpath'

Problem: Some use cases might lead to `vim.pack.add()` failing to
`:packadd` a plugin because of missing entry in 'packpath'. Like with
`nvim --clean` or manually setting `$XDG_DATA_HOME` during startup.

Solution: Document it. A more proactive approach can be ensuring correct
'packpath' entry, but it is currently somewhat verbose to do (due to
having to adjust for Windows using `\` in 'packpath' entries).
This commit is contained in:
Evgeni Chasnovski
2025-08-22 13:41:36 +03:00
parent 7acfad226d
commit 1ffaaa06c5
2 changed files with 6 additions and 2 deletions

View File

@@ -211,7 +211,9 @@ WORK IN PROGRESS built-in plugin manager! Early testing of existing features
is appreciated, but expect breaking changes without notice. is appreciated, but expect breaking changes without notice.
Manages plugins only in a dedicated *vim.pack-directory* (see |packages|): Manages plugins only in a dedicated *vim.pack-directory* (see |packages|):
`$XDG_DATA_HOME/nvim/site/pack/core/opt`. Plugin's subdirectory name matches `$XDG_DATA_HOME/nvim/site/pack/core/opt`. `$XDG_DATA_HOME/nvim/site` needs to
be part of 'packpath'. It usually is, but might not be in cases like |--clean|
or setting |$XDG_DATA_HOME| during startup. Plugin's subdirectory name matches
plugin's name in specification. It is assumed that all plugins in the plugin's name in specification. It is assumed that all plugins in the
directory are managed exclusively by `vim.pack`. directory are managed exclusively by `vim.pack`.

View File

@@ -4,7 +4,9 @@
---is appreciated, but expect breaking changes without notice. ---is appreciated, but expect breaking changes without notice.
--- ---
---Manages plugins only in a dedicated [vim.pack-directory]() (see |packages|): ---Manages plugins only in a dedicated [vim.pack-directory]() (see |packages|):
---`$XDG_DATA_HOME/nvim/site/pack/core/opt`. ---`$XDG_DATA_HOME/nvim/site/pack/core/opt`. `$XDG_DATA_HOME/nvim/site` needs to
---be part of 'packpath'. It usually is, but might not be in cases like |--clean| or
---setting |$XDG_DATA_HOME| during startup.
---Plugin's subdirectory name matches plugin's name in specification. ---Plugin's subdirectory name matches plugin's name in specification.
---It is assumed that all plugins in the directory are managed exclusively by `vim.pack`. ---It is assumed that all plugins in the directory are managed exclusively by `vim.pack`.
--- ---