# .bash\_login help!

**URL:** <https://www.ruby-forum.com/t/bash-login-help/103938>\
**Category:** Rails\
**Created:** [May 11, 2007, 7:51pm UTC](https://www.ruby-forum.com/t/bash-login-help/103938 "2007-05-11T19:51:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [May 11, 2007, 7:51pm UTC](https://www.ruby-forum.com/t/bash-login-help/103938/1 "2007-05-11T19:51:09Z")

</div>

My setup worked perfectly! I had installed all sorts of things I  
needed for RoR with MacPorts and a lot of gems and then I wanted to be  
smart and add mySQL to the path in .bash\_login so I could access it in  
the terminal…

I typed mate .bash\_login (opening the document .bash\_login in textmate  
if it exists or creating a new one in the current folder) while in the  
home directory in the terminal and got a blank document in TextMate. I  
pasted in the path to mySQL and saved it.  
I must have overwritten some previous version without being told  
because after that I couldn’t do any of my normal terminal stuff  
anymore!

I then manually added all the paths I could think of and look up in  
the file system to the .bash\_login but a lot of things still don’t  
work. I tried to reinstall all the ports apps and all the gems in hope  
that one of the package managers would do some .bash\_login magic for  
me, but none of them did.

When trying to run the ruby script/server command I now get:

./script/…/config/boot.rb:18:in `require': No such file to load -- rubygems (LoadError) from ./script/../config/boot.rb:18 from script/server:2:in`require’  
from script/server:2

Could one of you rails developers out there who are on a mac do me a  
favor and copy and paste their .bash\_login? Feel free to remove all  
parts that don’t have anything to do with ruby and ruby on rails.

Thanks.

Best regards  
Sebastian

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [May 11, 2007, 8:12pm UTC](https://www.ruby-forum.com/t/bash-login-help/103938/2 "2007-05-11T20:12:11Z")

</div>

Never mind…  
Sorry.

One of the first things I tried to do to solve the problem was to get  
my old .bash\_login from a backup. I couldn’t find one in my backup  
though. I then tried to remove the .bash\_login I just had created  
thinking that maybe there hadn’t been one originally, but things still  
didn’t work so I created it once more. What I might have forgotten was  
to restart the terminal though, because when trying to delete it now,  
it sort of works. I still got a few error, but after reinstalling  
rails and mongrel things seem to work.

That leads to another question though. How could a single .bash\_login  
file ruin my whole terminal workflow? I am positive that the new PATH  
that was exported in the .bash\_login file did reference $PATH so any  
values already present or added by other files should be preserved…  
do you have any idea?

Best regards  
Sebastian

On May 11, 7:50 pm, Sebastian Probst E.

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [April 9, 2009, 5:31am UTC](https://www.ruby-forum.com/t/bash-login-help/103938/3 "2009-04-09T05:31:58Z")

</div>

Sebastian probst Eide wrote:

> Never mind…  
> Sorry.
> 
> One of the first things I tried to do to solve the problem was to get  
> my old .bash\_login from a backup. I couldn’t find one in my backup  
> though. I then tried to remove the .bash\_login I just had created  
> thinking that maybe there hadn’t been one originally, but things still  
> didn’t work so I created it once more. What I might have forgotten was  
> to restart the terminal though, because when trying to delete it now,  
> it sort of works. I still got a few error, but after reinstalling  
> rails and mongrel things seem to work.
> 
> That leads to another question though. How could a single .bash\_login  
> file ruin my whole terminal workflow? I am positive that the new PATH  
> that was exported in the .bash\_login file did reference $PATH so any  
> values already present or added by other files should be preserved…  
> do you have any idea?
> 
> Best regards  
> Sebastian
> 
> On May 11, 7:50 pm, Sebastian Probst E.

Sebastian -

I ran into the same exact problem with my Terminal. I wanted to  
downgrade my rails installation. Got a warning and so added a path to  
the .bash\_login file which might be wrong I think. So after restarting  
the Terminal now it looks like my Terminal got messed up. It can’t even  
recognize the RAILS command.

If you can please help me out on this to get my Terminal back that would  
be great. I’m new to OSX (\*nix) and if you can be a bit more specific on  
how to get my Terminal working again that would greatly help.

Thanks in advance.
