I added some data to my
.bash_profile to run two aliases ruby version 19 and the proper gems. As soon as I added the data I could not longer run any commands such as the MacPorts command port nor the command mate to run TextMate. As soon as I deactivated
.bash_login and even
.bash_history all was well again.
.bash_history got regenerated and soon thereafter I got
.bash_profile reinstated with my badly needed aliases, but then I lost the option to run these commands again. Here is some of the output of all these files:
jaspersmbp:~ jasper$ cat .bash_profile alias ruby='/opt/local/bin/ruby1.9' alias gem='/opt/local/bin/gem' jaspersmbp:~ jasper$ cat .bash_login jaspersmbp:~ jasper$ cat .bashrc HISTFILESIZE=1000000000 HISTSIZE=1000000 jaspersmbp:~ jasper$ cat .profile #Django path export PATH=/opt/local/bin:opt/local/sbin:/opt/local/lib/python2.4/site-packages/django/bin:$PATH # Apache alias alias apacherestart='sudo /opt/local/apache2/bin/apachectl -k restart' #Subversion OSX for Eclips Joomla Development export PATH=/opt/subversion/bin:$PATH #Test #echo $PATH ## # Your previous /Users/jasper/.profile file was backed up as /Users/jasper/.profile.macports-saved_2012-05-18_at_09:47:58 ## # MacPorts Installer addition on 2012-05-18_at_09:47:58: adding an appropriate PATH variable for use with MacPorts. export PATH=/opt/local/bin:/opt/local/sbin:$PATH # Finished adapting your PATH environment variable for use with MacPorts.
Does anyone know why making
.bash_profile active anihilates the use of commands such as mate and port? I really need
.bash_profile to work so I can use aliases and I need MacPorts port command for all kinds software.