I've installed the latest KDE version of MX Linux.
I note that the .profile file in my home directory has two checks already set for adding ~/.local/bin and ~/bin to the PATH.
After reboot, echo $PATH does not show the updated PATH. I created ~/.local/bin and ~/bin so the exist checks should work.
If I souce .profile, the new entries show up.
Why isn't the PATH updated on reboot?
Adding to my PATH on system startup
- dolphin_oracle
- Developer
- Posts: 22445
- Joined: Sun Dec 16, 2007 12:17 pm
Re: Adding to my PATH on system startup
I think it gets overwritten by .bashrc. modify your path there.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Live system help document: https://mxlinux.org/wiki/help-antix-live-usb-system/
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Live system help document: https://mxlinux.org/wiki/help-antix-live-usb-system/
Re: Adding to my PATH on system startup
In short, quoting Debian's wiki:
They describe some ways of adjustments. Make sure when using .bashrc, it's made such that the PATH is not added, when it's already included.wiki.debian.org/EnvironmentVariables wrote:Graphical logins do not read a shell's startup files (/etc/profile and ~/.profile and so on) by default
Re: Adding to my PATH on system startup
I see. Didn't know that as most of my past experience was on Arch based distros. Although I wonder why the MX install puts those additions in .profile on a clean install.
Thank you!
Thank you!
Re: Adding to my PATH on system startup
To allow setup environment for users who prefer to boot into the console instead of X-gui - see wiki link.slayd wrote: Wed Apr 26, 2023 7:30 pm I see. Didn't know that as most of my past experience was on Arch based distros. Although I wonder why the MX install puts those additions in .profile on a clean install.
Re: Adding to my PATH on system startup
Ah. That makes sense.
I solved the problem by sourcing .profile from .zshrc
I solved the problem by sourcing .profile from .zshrc