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: keep the cond=false plugins in-sync in the lazy-lock.json #1535

Closed
1 task done
Stark-X opened this issue Jun 23, 2024 · 4 comments · Fixed by #1612
Closed
1 task done

feature: keep the cond=false plugins in-sync in the lazy-lock.json #1535

Stark-X opened this issue Jun 23, 2024 · 4 comments · Fixed by #1612
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@Stark-X
Copy link

Stark-X commented Jun 23, 2024

Did you check the docs?

  • I have read all the lazy.nvim docs

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

It's been a bit tricky managing my terminal setup between work and home. I've used different plugins - Plugin A for work and Plugin B for home. I thought I could switch between them using a cond in the config, but turns out the lock file I put in the git doesn't keep both plugins intact. It's causing the lock file to always update whenever I "sync" in a different environment.

Describe the solution you'd like

The lock file should contains the disabled plugins.

Describe alternatives you've considered

N/A

Additional context

No response

@Stark-X Stark-X added the enhancement New feature or request label Jun 23, 2024
@rochakgupta
Copy link

+1 as this is probably my biggest and only pain point with lazy.nvim.

@folke
Copy link
Owner

folke commented Jun 29, 2024

This can't really be poperly fixed, since there's no state for plugins that have not been installed due to cond

@folke folke closed this as not planned Won't fix, can't repro, duplicate, stale Jun 29, 2024
@folke folke added the wontfix This will not be worked on label Jun 29, 2024
@PeterCardenas
Copy link

PeterCardenas commented Jun 30, 2024

@folke do you recommend a specific workaround? currently trying setting lazy = true and setting up the autocommand to load the plugin manually

@folke folke reopened this Jul 5, 2024
@folke folke closed this as completed in baac551 Jul 5, 2024
@folke
Copy link
Owner

folke commented Jul 5, 2024

Plugins with cond=false or disabled=true now remain in the lockfile

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

Successfully merging a pull request may close this issue.

4 participants