Dotan Cohen wrote: >>> Why would a .bash_profile affect KDE *at all*? .bash_profile is used by >>> *bash* to configure the environment for login runs. If you are starting a >>> KDE session from KDM/XDM/GDM there's no login bash runs involved in the >>> startup. >> I don't think that's universally true, though it probably depends on >> distro and DM. >> >> However... >> >>> If you would like to affect the global environment of your KDE session, and >>> are not using a custom session, you can place files in ~/.kde/env. Files >>> ending in ".sh" are read and executed in the same shell that is reading and >>> executing the startkde script. >> ...you will probably have better luck with this. > > Should I just call it $HOME/.kde/env/profile and include this: > PATH="$HOME/.bin:$PATH" "Files ending in ".sh" are read and executed..." ...so it would be 'profile.sh'. Otherwise I think yes (but I haven't tried it). -- Matthew Please do not quote my e-mail address unobfuscated in message bodies. -- "It's ok, I forgive you. I often confuse cream cheese with happiness myself ;-)" -- Jeremy Whiting (responding to a rather strange yet amusing conversation I'd started; also, I agree with the sentiment) ___________________________________________________ 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.