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:inrequire’
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
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 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.