On Tuesday, 2011-02-01, Dotan Cohen wrote: > It is rather frustrating that the Plasma Krunner (Alt-F2) does not > follow the path configured in $HOME/.profile. If the user has a > wrapper function for /usr/bin/firefox in $HOME/.bin/firefox and > $HOME/.bin starts the path, Konsole will open the firefox wrapper but > Krunner will open /usr/bin/firefox. > > The lead Plasma developer mentions that the user can configure the KDE > path by placing an executable in ~/.xinitrc > https://bugs.kde.org/show_bug.cgi?id=263883 > > However, it "doesn't work". Googling the issue I see lots of people > asking and the answer is usually to configure the path in > .bash_profile or .profile. That does not work in KDE 4.x, I assume > that it worked in 3.x by the age of those posts. That never worked because e.g. .bash_profile is only read by interactive shells (see man bash) and the shell running /usr/bin/startkde is not interactive. Some people might have had /bin/bash symlinked to /bin/sh and .bashrc sourcing .bash_profile but of course this is just working around the way that shell works. Usually distributions have some way of setting environment variables that should always be present regardless of the type of login (local vs. from remote, X vs. virtual console). Xinit is a way to do that only for X11 based sessions, but again regardless of workspace environment being used. For KDE one can additional use KDE's environment extender mechanims, i.e. putting a file (with .sh extension) into $HOME/.kde/env Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
Attachment:
signature.asc
Description: This is a digitally signed message part.
___________________________________________________ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
