Re: The same environment variables everywhere
- Date: Mon, 27 Feb 2017 08:11:21 -0500
- From: Greg Wooledge <wooledg@xxxxxxxxxxx>
- Subject: Re: The same environment variables everywhere
On Sun, Feb 26, 2017 at 02:26:08PM +0200, Teemu Likonen wrote:
> I would like to hear some ideas on how to set various environment
> variables (PATH, MANPATH, EDITOR etc.) in one place that would make them
> effective everywhere. My "everywhere" means:
> - X session started through lightdm and ~/.xsession script
> - Linux console login (bash)
> - user's systemd services
The last one is simply not going to happen the way you seem to expect.
You should change the jobs launched by systemd to dot in the appropriate
file, instead of expecting systemd to load some interactive shell config
As for the first two... well. You know WHY there is a separation, right?
People put crap in .profile that would not work properly in an X config
file, because there is no terminal. For example, /usr/games/fortune,
or something that probes the terminal settings. The complete absence of
an underlying terminal, not to mention a TERM variable, would make many
.profile files fail, which is why .profile is not read by X startups.
However, if *you* have personally vetted your .profile and believe that
it will run safely in an X startup environment with no terminal, then
you can simply dot it in from ~/.xsessionrc and voila.
(Do not confuse ~/.xsessionrc and ~/.xsession; they are very different.)