(Premise: let's assume we want the shells to read their config files for the question below)
Question: Don't we actually want to run the shells as **login** non-interactive shells even on linux? The reason I'm asking is that: 1. For sh, it's impossible to specify any config file to be used when run as non-login non-interactive so we can't read .profile. The ENV variable is used to specify sh equivalent of .bashrc for non-login interactive shells so it cannot be used for this purpose. 2. For bash, we can set BASH_ENV to point to .bash_profile (and possibly fall back to .profile when it doesn't exist), but it won't read for us /etc/profile which might contain something important. In the plots, login non-interactive shells are represented by yellow arrows and IMO this is exactly what we want to happen. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/2363#issuecomment-551996307
