On 2020/03/23 14:16:23 +0000, Michael Matz wrote:
Hello,
On Mon, 23 Mar 2020, Dr.-Ing. Dieter Jurzitza wrote:
what are you meaning with "child process"? If a terminal (say xterm ..) is started within the gui, all the bash - related aliases within /etc/profile.d/ are processed and active (i. e. ls.bash ...) so how comes you assume the usage of this directory to be "pointless"? I do not get you there ...
ls.bash is _always_ sourced, no matter if interactive login shell or not (see /etc/bash.bashrc). Some other files as well (/etc/profile.d/alias.bash and ~/.alias). But generally, files within /etc/profile.d are not sourced by an interactive shell that isn't also a login shell. You should see that when you try the suggestion: put some random alias into /etc/profile.d/bla.sh and try it out. You will find that the new alias won't exist, except for a 'bash --login' after you have _unset_ $PROFILEREAD.
Right now /etc/bash.bashrc.local is the only place where you can put system-wide aliases that shouldn't be overwritten by packages.
Werner: ideally you would devise some file (or directory) names where people could put it their system-wide aliases, also from packages, that would be sourced from /etc/profile.d/alias.bash .
Good point ... same for tcsh Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr