Different dotfiles on different machines, updated on the target side about chezmoi HOT 5 CLOSED

Another options is to use a modify_ script.

In general, yes. lazy-lock.json is a bit of a special case akin to go.sum. I don't think I’d want to have a modify_ script for go.sum or Gemfile.lock.

from chezmoi.

lazy-lock.json should not be templated, full stop. It's a state file that, if you use different plug-ins on different machines, will always differ, and using chezmoi's approach for substituting state here is the wrong choice.

Your main options are:

1. Use the same plug-ins on all machines. This keeps a stable lazy-lock.json that just needs to be merged when you update it.

2. Configure lazy.nvim to use a different lockfile for personal and work machines. When you call lazy.setup({}), do something like this in your (now templated) setup file:

   lazy.setup({
     lockfile = vim.fn.stdpath("config") .. {{ if isPersonal }}"/lazy-lock.json" {{ else }}"/work-lazy-lock.json"{{ end }}
   })
   

See https://github.com/folke/lazy.nvim?tab=readme-ov-file#%EF%B8%8F-configuration.

from chezmoi.

Another options is to use a modify_ script.

from chezmoi.

lazy-lock.json should not be templated, full stop. It's a state file that, if you use different plug-ins on different machines, will always differ, and using chezmoi's approach for substituting state here is the wrong choice.

Your main options are:

1. Use the same plug-ins on all machines. This keeps a stable `lazy-lock.json` that just needs to be merged when you update it.

2. Configure `lazy.nvim` to use a different lockfile for personal and work machines. When you call `lazy.setup({})`, do something like this in your (now templated) setup file:
   ```
   lazy.setup({
     lockfile = vim.fn.stdpath("config") .. {{ if isPersonal }}"/lazy-lock.json" {{ else }}"/work-lazy-lock.json"{{ end }}
   })
   ```

See https://github.com/folke/lazy.nvim?tab=readme-ov-file#%EF%B8%8F-configuration.

Here, the file differing on different machines is a feature, not a bug. I care much less about breaking my editor at home than at work. I still want the lockfile to be version-controlled so I can easily roll it back if I need to, as suggested here.

from chezmoi.

Another options is to use a modify_ script.

In general, yes. lazy-lock.json is a bit of a special case akin to go.sum. I don't think I’d want to have a modify_ script for go.sum or Gemfile.lock.

I will look into modify scripts and your option number 2. I mostly wanted more options to consider, thank you both for the suggestions!

from chezmoi.