Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature: restore plugins by default #1817

Open
1 task done
sigasigasiga opened this issue Nov 18, 2024 · 1 comment
Open
1 task done

feature: restore plugins by default #1817

sigasigasiga opened this issue Nov 18, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@sigasigasiga
Copy link

sigasigasiga commented Nov 18, 2024

Did you check the docs?

  • I have read all the lazy.nvim docs

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

As nearly all of us, I store my dotfiles in a git repo. lock-file.json is stored under version control too.
However, if I clone my setup to a new machine, open up neovim, Lazy begins to install the latest version of each plugin automatically and overwrites the lockfile.

To get the locked versions after that I need:

  1. git restore path/to/lockfile
  2. nvim -> :Lazy restore

which is quite inconvenient

Describe the solution you'd like

If lockfile exists then restore all the plugins, otherwise install the newest version.
If a plugin is listed in the spec but is not in the lockfile, then install the latest version and update the lockfile

Describe alternatives you've considered

  1. git restore path/to/lockfile
  2. nvim -> :Lazy restore

Additional context

No response

@sigasigasiga sigasigasiga added the enhancement New feature or request label Nov 18, 2024
@stoicon
Copy link

stoicon commented Nov 28, 2024

#1804
(How to use the Lock file when lazy.nvim loads for the first time?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants