|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make .profile the only configuration file for shells. It concentrates
not only environment variables as login files should, but also aliases,
functions, etc.
Setting $ENV to ~/.profile makes interactive calls to `sh` load this
files, and symlinking ~/.bashrc makes interactive calls to `bash` do
the same.
Ultimately, I find that the separation of environment variables to login
files, usually in ~/.bash_profile, to make sense when thinking about
user sessions and logins, but not something I benefit from. Staying
logged in for multiple days, I modify environment variables that I want
to affect my existing and new terminal sessions, and having to do extra
work for getting those new values (such as an extra command that sources
~/.profile) isn't interesting to me.
|