docs: document custom lockfile path via 'packlockfile' - #34
Merged
Conversation
Neovim 0.13+ (neovim/neovim#36078) makes the vim.pack lockfile path configurable. zpack delegates all lockfile access to vim.pack, so the option works as-is; note the ordering caveat (must be set before the vim.pack.add() that installs zpack). Refs #6
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #6 (custom lockfile path), which was resolved upstream by neovim/neovim#36078.
Neovim 0.13+ exposes the
'packlockfile'option, and zpack delegates every lockfile read/write tovim.pack, so it works with zpack as-is — it just wasn't documented anywhere.Adds a Lockfile location section to
docs/tips.mdand a mirrored*zpack-lockfile*subsection todoc/zpack.txtcovering:$XDG_CONFIG_HOME/nvim/nvim-pack-lock.json, i.e. inside your config repo)stdpath('data')vim.packcall, i.e. before thevim.pack.add()that installs zpack itselfNo code changes.
Note on #7's plenary follow-up ("maybe add it to the migration tips"): already covered on main by the default lazy plugins bullet in
docs/tips.md/*zpack-migration-default-lazy*, so no change needed there.