Comment by b40d-48b2-979e
1 day ago
As a bonus, you can (should?) version control your `~/.config` dir to enable future revisions and sharing.
1 day ago
As a bonus, you can (should?) version control your `~/.config` dir to enable future revisions and sharing.
check out gnu stow for this! i place my config files in ~/dots, mirroring the structure as if it were my home directory, and gnu stow can symlink everything to my home directory for me. then, only the dots directory is checked into version control.
i find this better than putting all of ~/.config in git, since i don't necessarily want everything there to be version controlled.
video i learned this from: https://youtu.be/y6XCebnB9gs
gnu stow: https://www.gnu.org/software/stow/
You may need to have certain directories be excluded depending on the programs you use. For example, the default Chrome profile location is within ~/.config, which includes cache data that can be multiple gigabytes in size.
Ouch. It doesn't respect `$XDG_CACHE_HOME`?
That's what .gitignore is for ;)
Absolutely. On that subject, I prefer the Atlassian method for storing dotfiles in git but sometimes I feel like it's Mootools vs jQuery all over again.