Just use `git` to manage your dotfiles
ericgreer.info
Just use `git` to manage your dotfiles
1–10 of 15 posts
Re: Just use `git` to manage your dotfiles
#2Instead of ignoring everything, I've found it better to apply this setting instead:
git config status.showuntrackedfiles noRe: Just use `git` to manage your dotfiles
#3This was discussed a lot on HN.
The problem with this approach is that you can accidentally commit to the $HOME repository.
An approach that avoids that is to use --git-dir= attribute.
E.g. alias dotfiles="git --git-dir=$HOME/.dotfiles"
Re: Just use `git` to manage your dotfiles
#4Sometimes a well-designed, purpose-built tool can replace so many kludgy solutions. This doesn’t solve the problem of reinstating the dotfiles to their original positions in a new machine.
I’ve tried everything from raw git to gnu stow to manual symlinking and everything in between. They all work when the full context of the workflow is fresh in my brain. But after a few weeks I always mess up, even though I’ve documented the process in my dotfiles repo.
I eventually settled on chezmoi, and it just works. I set it up a year ago and haven’t needed anything beyond chezmoi -v diff and chezmoi -v apply.
Re: Just use `git` to manage your dotfiles
#5This was discussed a lot on HN. The problem with this approach is that you can accidentally commit to the $HOME repository. An approach that avoids that is to use --git-dir= attribute. E.g. alias dotfiles="git --git-dir=$HOME/.dotfiles"
This is basically what vcsh (https://github.com/RichiH/vcsh) does. You can install the package via your package manager to get the manpage + completions, or copy in the shell script (https://github.com/RichiH/vcsh/blob/main/doc/INSTALL.md#stan...).
Re: Just use `git` to manage your dotfiles
#6I've been using the same method that was viral on HN years ago. Still works well.
Re: Just use `git` to manage your dotfiles
#7Sometimes a well-designed, purpose-built tool can replace so many kludgy solutions. This doesn’t solve the problem of reinstating the dotfiles to their original positions in a new machine. I’ve tried everything from raw git to gnu stow to manual symlinking and everything in between. They all work when the full context of the workflow is fresh in my brain. But after a few weeks I always mess up, even though I’ve docum…
I’ve been using Chezmoi. It has lots of niceness. Two things are awkward for me. Maybe you have solutions.
I know my way around emacs. vimdiff is a foreign country.
Often my changes are speculative or experimental. So I checkout, edit, apply and only then discover I’ve messed up. Or I can edit in place. Voila vimdiff!
What’s the better way?
Re: Just use `git` to manage your dotfiles
#8Sometimes a well-designed, purpose-built tool can replace so many kludgy solutions. This doesn’t solve the problem of reinstating the dotfiles to their original positions in a new machine. I’ve tried everything from raw git to gnu stow to manual symlinking and everything in between. They all work when the full context of the workflow is fresh in my brain. But after a few weeks I always mess up, even though I’ve docum…
I’ve been using Chezmoi. It has lots of niceness. Two things are awkward for me. Maybe you have solutions. I know my way around emacs. vimdiff is a foreign country. Often my changes are speculative or experimental. So I checkout, edit, apply and only then discover I’ve messed up. Or I can edit in place. Voila vimdiff! What’s the better way?
I would also like to mention Chezmoi.
I switched to it after maintaining a custom written POSIX sh script that kept getting further and further out of hand.
I don't see myself going back to a self-maintained one unless I'm writing it in Rust.
Re: Just use `git` to manage your dotfiles
#9Sometimes a well-designed, purpose-built tool can replace so many kludgy solutions. This doesn’t solve the problem of reinstating the dotfiles to their original positions in a new machine. I’ve tried everything from raw git to gnu stow to manual symlinking and everything in between. They all work when the full context of the workflow is fresh in my brain. But after a few weeks I always mess up, even though I’ve docum…
I’ve been using Chezmoi. It has lots of niceness. Two things are awkward for me. Maybe you have solutions. I know my way around emacs. vimdiff is a foreign country. Often my changes are speculative or experimental. So I checkout, edit, apply and only then discover I’ve messed up. Or I can edit in place. Voila vimdiff! What’s the better way?
Do you run your changes in the original location?
The canonical workflow is this: you run chezmoi cd and make changes there first. Only then do you run chezmoi apply to propagate the changes to the original location.
The source of truth is always what lies in the chezmoi directory, not the other way around.
So if you’re experimenting with the dotfiles in their original location, running chezmoi apply will override them with the snapshot in the chezmoi directory. The vimdiff doesn’t do much here.
If you want to retain your changes there, you’ll have to manually copy them over to the chezmoi directory. This is a bit awkward, but having a consistent source of truth makes the behavior easier to reason about. I rarely look at the diff.
Re: Just use `git` to manage your dotfiles
#10Git is great, but it doesn’t solve the problem of removing unused dotfiles. For that, I use a custom script that accepts a configuration file mapping each file/directory to a package on my system. Then, when I remove those packages, I’m notified to delete its dotfiles.
I’ve found this helpful for evaluating new packages without cluttering my home directory. It’s especially helpful when using many packages that don’t respect the XDG Base Directory specification; they tend to dump dotfiles directly in my home directory, so keeping it clean is important.