FRESH

Hacker News

My .config Ship of Theseus

31 points by jacobwiseberg

by Leonard_of_Q

4 subcomments

I sort of get the appeal of fine-tuning the terminal environment to perfection but after fiddling with such things for many years - decades - I ended up using mostly stock settings with a very few changes. The advantage of that approach is that I feel at home just about anywhere instead of just on my one or few customised systems. My customisations mostly consist of a local /bin directory with a few hundred scripts (wc -l now shows 263) I made over the years which I dump in a new environment plus a few additions to .bashrc (yes, bash, not one of the fancy replacements (zsh, fish, oil, ...) which are supposed to be better but in reality just end up being different) to set custom paths etc.

by threecheese

5 subcomments

And then you get friends like Claude - dozens of them - which prefer to crap all over $HOME.
The app ‘Conductor’ does this, and I had to uninstall it; I just can’t crack my ‘ls ~/.co<TAB>’ habit, and “nd” is juuuuuust ahead of “nf”.
It *used to* be ‘~/c<TAB>’ before .claude crapped itself into existence..

0 subcomment

by PunchyHamster

1 subcomments

Using actual configuration management (in my case Puppet, tho Ansible is lighter choice) is just all around better way
First: you can template stuff easily. Like having config that have different parameters (say a display name to display stuff on) between devices.
Second: You can do "the everything else" of the machine setup, not just configs but also installed apps and various quirks and tweaks.

by clircle

2 subcomments

I’m moving slowly in the direction of Guix home for dotfile management, but until it covers all my bases, I’m fond of the gnu stow method

by nailer

2 subcomments

Never understood the point of having a dotfile for all of config when config is the point of dotfiles.