diff options
| author | EuAndreh <eu@euandre.org> | 2022-05-13 15:08:14 -0300 |
|---|---|---|
| committer | EuAndreh <eu@euandre.org> | 2022-05-13 15:08:17 -0300 |
| commit | e3c2736b4e0e286d4038a6044d66a58d02ec111d (patch) | |
| tree | 606ba334c269f14ab9c4a6d0c1fcc94f4d7e48fe /bin/email | |
| parent | etc/bash/rc: Include `f ...` and `v ...` in shell history (diff) | |
| download | dotfiles-e3c2736b4e0e286d4038a6044d66a58d02ec111d.tar.gz dotfiles-e3c2736b4e0e286d4038a6044d66a58d02ec111d.tar.xz | |
etc/bash/rc: Link ~/.bashrc to ~/.profile and add set $ENV to ~/.profile
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.
Diffstat (limited to 'bin/email')
0 files changed, 0 insertions, 0 deletions