You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I were to unconditionally source.sh/profile in .profile, I would have to un-source it from .bash_profile, and rename all BSF to implicitly "force" Bash to source .profile instead (this is very fragile, as it depends on default behavior). The problem is, users (including myself) would have to nuke all BSF too, as sourcing .profile from any startup-file would cause an infinite source loop.
A potential solution, is to inline .sh/profile into .profile and make .bash_profile source that instead, while un-sourcing .bashrc. This doesn't seem to have any cons, only pros, such as making .profile fully POSIX-compliant and (mostly) shell-agnostic
The text was updated successfully, but these errors were encountered:
If I were to unconditionally
source
.sh/profile
in.profile
, I would have to un-source
it from.bash_profile
, and rename all BSF to implicitly "force" Bash to source.profile
instead (this is very fragile, as it depends on default behavior). The problem is, users (including myself) would have tonuke
all BSF too, as sourcing.profile
from any startup-file would cause an infinitesource
loop.A potential solution, is to inline
.sh/profile
into.profile
and make.bash_profile
source that instead, while un-sourcing.bashrc
. This doesn't seem to have any cons, only pros, such as making.profile
fully POSIX-compliant and (mostly) shell-agnosticThe text was updated successfully, but these errors were encountered: