New command line variables are put in .bash_profile, which isn't executed in all cases.

[GoogleCodeExporter]

To reproduce

- Install git cleanly (on my account :-D)
- try to start git from a new terminal
- it isn't found.

On my user account, .bash_profile isn't executed, but .bashrc is.

I created a new account, and .bash_profile is executed there!  So this
can't be repro'ed on a new account.

I'm not sure what's different about my account - the only relevant bash
file I have there is .bashrc and of course .bash_history.  I never noticed
this difference before because I just put things in .bashrc.

But if my account is different, there must be other people whose accounts
are different;  the installer needs to take this into account.

Original issue reported on code.google.com by tom.ritc...@gmail.com on 16 May 2008 at 7:27

[GoogleCodeExporter]

Did you have ~/.profile ?

My understanding is that .profile is executed if it exists.  Then, 
.bash_profile is
executed if .profile doesn't exist.

Original comment by timchar...@gmail.com on 16 May 2008 at 7:31

[GoogleCodeExporter]

There's no .profile.

Oh, dear, this is so embarrassing.  I restarted my whole user session after 
that last
one and now .bash_profile runs every time in a new shell, I see my annoying 
debugging
messages that weren't there.

I can't see what I might have done to prevent it from running before.  This 
machine's
been up for quite a while now, perhaps that was it.

:-(  Sorry.

Original comment by tom.ritc...@gmail.com on 16 May 2008 at 9:29

[GoogleCodeExporter]

Original comment by timchar...@gmail.com on 16 May 2008 at 9:56

• Changed state: Invalid

[GoogleCodeExporter]

p.s. - I've posted more than plenty of issues like this :)  Thanks for taking 
the time to report how your experience 
is and helping to make the installer better.

Original comment by timchar...@gmail.com on 16 May 2008 at 9:58