1·
1 year agoSince .bashrc is executed for all non-login shells, it shouldn’t really source .profile, which is only meant for login shells, and might trigger expensive activity. (.profile might source .bashrc, but that`s fine.)
aebletrae [she/her]
- 0 Posts
- 3 Comments
Joined 1 year ago
Cake day: July 23rd, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Are other lines in
.profilebeing executed, or is the whole file ignored? Have you logged out and in again since adding these lines?
But those kinds of initialisations belong in
.profile(or, if you’re using a weird desktop environment, its own configuration file), particularly if you want.desktopfiles to work. (In.bashrc,PATHwill grow longer in each subshell, which shouldn’t cause problems but is wasteful.)So, what desktop environment (GNOME, KDE, Cinnamon, etc.) are you using?
.profileis executed by login shells for the benefit of it and its subshells, and by DEs like Cinnamon for the benefit of.desktoplaunchers at login.So, have you logged out and back in again since adding these lines to
.profile?And of course, the
.profilehas to be executed properly for its configuration to take effect, so it`s useful to know if the problem is with those specific lines, or the file as a whole.Add:—
to the top of
.profile, and:—to the bottom of
.profile(use alternative paths as you see fit) to monitor that activity. You can test this by sourcing.profilebut the real test is logging out and in again. Look at the time when you do this so you can correlate each action with each timestamp in the log files. If.profileis executed to completion, you should have two files with matching timestamps but differentPATHs. If you don’t have a matching timestamp in the “end” log file, there’s a problem mid-execution. If neither file is being updated,.profileisn’t being executed at all.