Re: How To Permanently Add-to a Users PATH Statement in the Bash Shell
On Tue, Jul 07, 2020 at 09:57:34AM -0400, Stephen P. Molnar wrote:
> The Subject line is the problem
Yeah. The Subject: line reveals the problem: you believe that PATH is
set primarily by your shell.
It's not. It's set primarily by your method of login, and then by your
session tools, whether those be a shell or a desktop environment. A
shell may have the final word in some setups, but in many cases,
most of your environment is set before a shell is even executed.
> with my Debian Buster platform. Now from
> Google I see that there has been a change in the way Debian handles this
> problem.
Huh? What did you type into Google? What random page on the entire
freaking Internet did you read? What did you pick up from it? Is it
true or a lie?
> [[blah blah blah nothing about how you log in]]
> This works unless I open a new Terminal, in which case it is no longer in
> the PATH.
The only detail you've given us is that you have something you call
a "Terminal", with a capital T. Is that the actual name of the
terminal emulator you run? Maybe someone else who reads this message
can figure out "Oh, he said Terminal with a capital T, that must mean
he's running ____ Desktop."
If you actually want to understand how your environment is set during
login, you have to reveal the necessary details, and that starts with
*HOW* you log in (console login + startx, gdm3, sddm, lightdm, ssh,
or something else).
We also need to know if you run a Desktop Environment, and if so, which
one.
On top of that, it would be useful to know what terminal emulator you're
using to *TRY* to verify the PATH variable, and what options were given
to it. Believe it or not, the PATH variable you see in a terminal emulator
may not be the same as the one used by your window manager, etc.
Gods, I am so tired of this question and having to repeat my demands
for BASIC information over and over.
Here are some resources for those of you who refuse to reveal any of
the necessary background information to get answers, and would rather
hoard all of your details under the guise of "privacy" or whatever.
https://wiki.debian.org/Xsession
https://wiki.debian.org/EnvironmentVariables
https://mywiki.wooledge.org/DotFiles
That is nowhere NEAR a comprehensive overveiw of every possible piece
of every possible configuration, but it's a starting point.
Reply to: