I have noticed recently that .xinitrc seems to run with different envvars than those I set in /etc/profile and ~/.profile . I first noticed this when I started using ROX Appdirs in my home dir for some things - I have the following in my ~/.profile to let me use these apps from an xterm: for dir in ~/Apps/*; do alias `basename $dir`=$dir/AppRun ; done When I try to then run "ROX-Filer -pdefault & exec OroboROX" in my .xinitrc, they fail. I need to point directly to the AppRun script in each. This is a minor annoyance, but the story gets less trivial: I also set my CHOICESPATH (used by various ROX apps for locating their config files) in /etc/profile . This is unavailable to .xinitrc, and so is unavailable to ROX-Filer (since I start it's pinboard in .xinitrc), and is thus unavailable to, say, an OroboROX theme (these come in appdirs which run a shellscript to adjust the appropriate files and have OroboROX reparse it's config). The thing is that for some reason this var *IS* available to OroboROX - meaning that where it reads it's config, and where the theme adjusts the config, end up being two different places. This works well if I run the script from an xterm (since I have xterm set to be a login shell). I should be able to work around this with 'export CHOICESPATH=...' in my .xinitrc, but this isn't ideal since I would like to be able to change the location by editing one file. I could also have .xinitrc source the appropriate file in /etc/profile.d - however, I realy think this is an ugly solution.
Can anyone enlighten me on what could be causing this problem? -- Lennon Victor Cook -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
