-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悰 .local/bin folder missing from PATH #764
Comments
I think for that to work, we'd have to start foot as a login-shell, which caused other problems. But some things may have changed and probably we could give it another try (original issue: #721) |
This is not only foot related. I have some sway bindings that call some scripts from my local bin folder (I don't use full path, just script name), and they don't work also. |
Probably we just need to start sway from a login-shell then. Will do a little experiment. |
Would you like to give |
My shortcuts are working, but still no local bin folder in PATH in foot. |
Could you share your |
Sure, here it is: case ":${PATH}:" in And /etc/profile.d/home-local-bin.sh is owned by filesystem 2024.01.19-1 |
is that posix? I did just use |
I have no idea what that is. I have not used posix. It comes from core/filesystem package, and I guess it is installed in all Manjaro installations. |
Well - I guess it is posix compatible. I switched to using the $SHELL-variable anyway. |
Seems that service unit never came to a final conclusion regarding /etc/profile and honestly I am on the fence here, as I personally don't even use it, but I know this caused issues in that past. |
branch
stable
Architecture
x86_64
Description
I have noticed that my $HOME/.local/bin folder is missing from path (since recently, I am not sure about exact time when it disappeared.) When I manually source /etc/profile.d/home-local-bin.sh it works. But I didn't have to do this manually. Also other functionality in /etc/profile.d might be effected, I haven't checked.
Reproduction steps
Screenshots
No response
Logs
No response
The text was updated successfully, but these errors were encountered: