2 ms·
One thing I started doing differently is using a .ksajrc file. I then simply add that to the last line of .bashrc. The reason is that all too often the .bashrc
by ksaj 7y ago
One thing I started doing differently is using a .ksajrc file. I then simply add that to the last line of .bashrc. The reason is that all too often the .bashrc that comes "stock" with a major OS update/upgrade requires changes that get clobbered if you overwrite the default .bashrc all the time. This means I don't miss out on the OS changes, but I also have all my creature comforts.
For example, instead of specifying my full path in .ksajrc, I simply prepend my ~/bin if it is not already included in the pre-.ksajrc $PATH variable. Doing that means I don't suddenly lose new dist-added /opt directories in the path, as one example of many possible.
I also keep a list of what packages I need installed so I can just run that script after installation of the new OS. I do this mainly because I install a lot of stuff that doesn't normally get included in a stock setup. (examples include sbcl, gaze, htop, etc)
I haven't reflected that in my github dotfiles repository yet, but I should get on top of that.