Dev1 Galaxy Forum / Bash does not parse config files like bash_profile correctly.

Re: Bash does not parse config files like bash_profile correctly.

dummy@example.com (devian) — Wed, 04 Nov 2020 17:21:47 +0000

I stand corrected. Thanks for the reply. :-)

Re: Bash does not parse config files like bash_profile correctly.

dummy@example.com (Head_on_a_Stick) — Wed, 04 Nov 2020 17:14:19 +0000

Bash will read ~/.profile as long as ~/.bash_profile is not present but only if it is run as a login shell. However SLiM (the default display manager for Devuan) does not run bash as a login shell and logging in through that will result in ~/.profile (or ~/.bash_profile) not being read.

You can confirm this for yourself by logging in at a console (TTY) screen instead. It is not a bug.

Bash does not parse config files like bash_profile correctly.

dummy@example.com (devian) — Wed, 04 Nov 2020 11:30:50 +0000

According to https://www.gnu.org/savannah-checkouts/ … rtup-Files

"When Bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable."

I have no .bash_profile or .bash_login. I only have ,profile (and also .bashrc which *does* get parsed for different reasons) however I am finding that bash does not source this file when started.

Perhaps I should file this somewhere as a bug?
Cheers