Bash

Rails
1

I have installed Ruby and Rails on my Intel iMac according to the
instructions provided by Hivelogic. Everything works perfectly.
I have noticed that if I close Terminal and later come back and open it,
It seems like the paths set in bash_login are lost. If I open bash_login
the paths are still there however if i do ruby -v it says I am running
1.8.2 (mac default) when I have installed 1.8.4. If I run .
~/.bash_login, everything is fine and ruby -v now shows I am running
1.8.4.

Why do I have to keep running this command everytime I want work on my
rails app?

2

Ron G. wrote:

I have installed Ruby and Rails on my Intel iMac according to the
instructions provided by Hivelogic. Everything works perfectly.
I have noticed that if I close Terminal and later come back and open it,
It seems like the paths set in bash_login are lost. If I open bash_login
the paths are still there however if i do ruby -v it says I am running
1.8.2 (mac default) when I have installed 1.8.4. If I run .
~/.bash_login, everything is fine and ruby -v now shows I am running
1.8.4.

Why do I have to keep running this command everytime I want work on my
rails app?

Nevermind.
After some searching it looks like the two lines added to bash_login
needed to be added to .profile instead.

Sorry if you wasted any time reading this.

3

On Mar 28, 2006, at 8:21 PM, Ron G. wrote:

Why do I have to keep running this command everytime I want work on my
rails app?

This has come up before on the list - can you check for the existence
of ~/.bash_profile and let us know if it exists? From what I’m
reading at:

http://www.sfu.ca/~jpsember/osx.html

bash will source ~/.bash_profile, ~/.bash_login or ~/.profile,
whichever is found first. If you have a ~/.bash_profile and that
source is correct, then bash may simply not be getting around to
reading your ~/.bash_login. If you do have a ~/.bash_profile then
please add the line:

source ~/.bash_login

to the end of your file and then start a new terminal session and
type echo $PATH and see if it includes the directories added to your
path in your ~/.bash_login.

–
Jason P.
[email protected]

“The key to performance is elegance, not
battalions of special cases.”

  • Jon Bentley and Doug McIlroy
4

Jason P. wrote:

bash will source ~/.bash_profile, ~/.bash_login or ~/.profile,
whichever is found first. If you have a ~/.bash_profile and that
source is correct, then bash may simply not be getting around to
reading your ~/.bash_login. If you do have a ~/.bash_profile then
please add the line:

source ~/.bash_login

to the end of your file and then start a new terminal session and
type echo $PATH and see if it includes the directories added to your
path in your ~/.bash_login.

–
Jason P.
[email protected]

“The key to performance is elegance, not
battalions of special cases.”

  • Jon Bentley and Doug McIlroy

Since bash_profile was empty I just removed it.
Now everything is working again.
thank yo very much for the information and your help.