Re: My .profile is not read?

On Fri, Sep 16, 2011 at 05:28:15PM -0700, John W wrote:
 
> But for some reason fluxbox overwrote it with some 'default' value - I
> don't know why that happened, or if it is configurable. I didn't find
> cause for this in any obvious places, or in the documentation.
> Everything *else* from my .profile was inherited correctly, which is
> why I feel fairly confident in saying that something in fluxbox
> overwrote it.

I don't think fluxbox changes $PS1...

> So ultimately, when I launched new xterm processes inside fluxbox,
> they had the wrong PS1.

...but rather the .bashrc which is loaded by xterm.
(look deeply for what happens in your .bashrc)

Try the following in .fluxbox/keys
Control		BackSpace :Exec export -p > /tmp/env_dump.log
(then when fluxbox is up, you can dump its environment)

Or:
export -p > /tmp/env-before-bashrc.log at the beginning of .bashrc.

> As a workaround, I put my PS1 definition in my .bashrc rather than my .profile.
> Since .bashrc does get read every time a (non-login) shell is
> launched, it gave me my special prompt.

.bashrc is where is located my $PS1 too.
.bash_profile is where I try to put daemons like jackd, irexec, mpd,
some aliases and $PATH modifications (it uses [[ bash-syntax ]] )


> If anyone knows why fluxbox seems to be messing with PS1 on startup,

$ grep -r PS1 ~/comp/sources/fluxbox # brought nothing

is your $PS1 really exported ?


Raph

------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerry® mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry® DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1