aboutsummaryrefslogtreecommitdiff
path: root/runtime/ftplugin/java.vim
diff options
context:
space:
mode:
authorEvgeni Chasnovski <evgeni.chasnovski@gmail.com>2026-07-28 16:46:13 +0300
committerGitHub <noreply@github.com>2026-07-28 09:46:13 -0400
commit4bba83b4b7363bc6b8da04cb1e13817473b028ec (patch)
tree88294d1220cb3e659adf3809232896d418bd9e1a /runtime/ftplugin/java.vim
parent3fa5904cf246b783db778a457e5544272b847eff (diff)
downloadrneovim-4bba83b4b7363bc6b8da04cb1e13817473b028ec.tar.gz
rneovim-4bba83b4b7363bc6b8da04cb1e13817473b028ec.tar.bz2
rneovim-4bba83b4b7363bc6b8da04cb1e13817473b028ec.zip
fix(pack): do not write the lockfile when installing from it #41031
Problem: Installing plugins during lockfile synchronization always writes the lockfile, even though its content is used during install. This might be a problem if the lockfile (itself or its parent directory) is not writeable (can only be read). Solution: Do not write the lockfile when installing directly from it. This is okay since the `src` and `rev` are used directly from the lockfile and don't change at this step. While potential change in `version` (that must be written to the lockfile) is handled in other code path.
Diffstat (limited to 'runtime/ftplugin/java.vim')
0 files changed, 0 insertions, 0 deletions