-
Notifications
You must be signed in to change notification settings - Fork 20
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/etc/profile sourced twice when run from shell #13
Comments
I thought Anyway, running sway from your console should be as simple as |
Ah that makes more sense though the usage statement in the readme is confusing. Interestingly the reason I looked it up was because starting with |
I may have some bugs letting the (systemd's) environment polluted. If you reproduce the failure of
|
Here is the output after
Looks like sway is failing for some reason, I'll post the sway debugging output shortly. |
Here is the sway debug output when starting with
|
Running |
Sorry, I did'nt took the time to look into it lately. But yeah it's environment related. I'm trying to figure out witch variable is needed and why. I now think it's I'm also thinking about how to best handle the environment variables (and yeah I will need to provide a script at least to do the cleanup). |
In If the script is being run by a display manager, source Another solution is to not source More modern alternatives for setting global environment variables include /etc/environment and |
IMO considering Sway is running as a systemd service, sourcing Here's my soluion:
And add any other environment variable that you need via |
Oh! And also
|
When executing
sway-user-service
from a shell, /etc/profile has already been sourced and does not need to be sourced again. Although this has limited impact on functionality, it does cause annoyances such as duplicate entries in$PATH
.The text was updated successfully, but these errors were encountered: