Environemt for KDE programs started from the desktop icon
furue at hawaii.edu
Sat Jan 19 00:00:49 GMT 2008
| For example bash reads /etc/profile and its local equivalent when it
| is invoked as a login shell, but reads /etc/bash.bashrc and its
| local equivalent when run as an interactive shell, non-login, shell,
| so any environment customization in ~/.bashrc would be available in
| a Konsole window, but not for the KDE session itself.
And an easy solution is
$ cd ~/.kde/env
$ ln -s ~/.bash_profile bash_profile.sh
if you set your environmental variables in ~/.bash_profile ,
and restart your KDE session. Notice that filenames in
~/.kde/env/ should end with a ".sh" .
This solution is fairly clean, because .bash_profile is
executed only once. (.bashrc is executed each time bash is invoked.)
When you don't use KDE, ~/.bash_profile is still executed because bash
executes it when it's invoked as a login shell. This arrangement is
useful when you log in from a romte computer, for example.
One concern is that the startup script of the KDE system may override
some of the env. vars. I wish the startup script executed the
~/.kde/env/ scripts at the very end of the startup process, but that
doesn't seem to be the case. (Correct me if I'm wrong.)
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
More info: http://www.kde.org/faq.html.
More information about the kde