Since I just realized that, given the way I’m trying to arrange my dotfiles with a bare git repo, I can’t exactly include a README in the repo, I’m going to post the README I wrote here, because I thought it actually turned out pretty well. You can find the dotfiles referenced here.
These are my (fourth?) attempt at arranging my dotfiles. I’m bad at dealing with git so I keep starting over. If you want a history, check out my other repositories, ordered by date of last commit:
- A NixOS config with XMonad, etc.
- Some dotfiles I apparently forked from Forkk??
- The move to Gitlab
- Managed by GNU Stow
Okay, so it’s my fifth attempt. Like I said, I’m bad at Git. At any rate, this time I’m using the method outlined in Nicola Paolucci’s blog, which uses a bare git repo and shell alias to track files directly in
$HOME. I’m trying to use it instead of GNU Stow now because I don’t like how stow requires perl, which adds a dependency I don’t need, and because I use git a ton anyway, meaning that a move to Paolucci’s system is sort of a double-win, in a way.
You can see the files, in all their edited glory, at their repository.
Uhhh, all this shit’s in the public domain.By this, of course I mean the repo. Sure. I don’t care. Let’s say,
Unless otherwise specified, just in case I change my mind later.
I’ll try to keep this current.
add nvim and nvim-pager.
I’ve also decided (and this may be more important) that I’m going to keep each program’s configuration in its own branch, and merge them into the machine branches as needed. I’m sure this is going to come bite me in the ass someday, but today is not that day.