Running .bash_login everytime


#1

i used
http://hivelogic.com/articles/2005/12/01/ruby_rails_lighttpd_mysql_tiger
to install ruby on rails on my mac. everything works fine unless i close
the terminal application. after a while of pulling my hair out, i found
out that everytime i restart terminal, i have to run “. ~/.bash_login”
to make the paths work right. is that what i’m supposed to do everytme,
or did i do something wrong?

i’m new to a lot of this stuff, so any help would be greatly
appreciated.


#2

Josh K. wrote:

i used
http://hivelogic.com/articles/2005/12/01/ruby_rails_lighttpd_mysql_tiger
to install ruby on rails on my mac. everything works fine unless i close
the terminal application. after a while of pulling my hair out, i found
out that everytime i restart terminal, i have to run “. ~/.bash_login”
to make the paths work right. is that what i’m supposed to do everytme,
or did i do something wrong?

i’m new to a lot of this stuff, so any help would be greatly
appreciated.

Two possibilities:

Do you have ~/.bash_profile file? The contents of that file are
preferred over the contents of ~/.bash_login, so you need to combine the
two and get rid of the other.

Move the relevant contents of ~/.bash_login to ~/.bashrc The contents of
.bash_login are only sourced when bash is invoked as a login shell,
although my limited testing on mac os x shows that most normal ways of
opening a new terminal does source my .bash_profile.

Ray


#3

Two possibilities:

Do you have ~/.bash_profile file? The contents of that file are
preferred over the contents of ~/.bash_login, so you need to combine the
two and get rid of the other.

Move the relevant contents of ~/.bash_login to ~/.bashrc The contents of
.bash_login are only sourced when bash is invoked as a login shell,
although my limited testing on mac os x shows that most normal ways of
opening a new terminal does source my .bash_profile.

Ray

I just checked that, niether one of those other files exist when I tried
to edit them. I’m guessing another problem could be the actual location
of the file, but I typed it just like it was on the previously mentioned
tutorial.


#4

Josh K. wrote:

Ray

I just checked that, niether one of those other files exist when I tried
to edit them. I’m guessing another problem could be the actual location
of the file, but I typed it just like it was on the previously mentioned
tutorial.

The file ~/.bash_login is in your home directory. That’s what the “~”
means. What’s the result of typing

ls -l ~/.bash_login

in the Terminal?

Ray


#5

that’s what i get:

-rw-r–r-- 1 name name 72 Mar 20 08:44 /Users/name/.bash_login