Yet another path question

path

I created a Ruby file called Player.rb in the following path:
Jwan/studio_game

Jwan is my name so I think Jwan is my user file.

How do I permanently add the path to the terminal so I don't have to type in pwd and cd commands everytime I open the terminal?

Also, what does the code below do. I tried finding the answer myself but I do not understand what the code below does. What parts of the code below do I replace?

export PATH=/users/ophir/android-sdks/tools:$PATH

Best Answer

First of all I'd confirm that path. I believe the full path might be "/User/Jwan/studio_game". Type ls -al /User/Jwan/studio_game into a Terminal window and see if it lists your file.

Assuming that works, then within the Terminal you could use the following command to add that location to your PATH variable. Then open a new Terminal window (or a new tab within the existing one) and the change should have taken effect.

echo export PATH='/User/Jwan/studio_game:$PATH' >> ~/.bash_profile

And just to explain that command...

echo says to write whatever follows to standard output.
export says you want to export a variable.
PATH is the name of the variable you want to export.
$PATH refers to the existing variable.
>> redirects standard output to a file. >> appends to the file if it exists, or creates it if it doesn't. > on its own would replace the file if it already existed.
~ represents your home folder which I assume is /Users/Jwan.
.bash_profile is a file that is loaded whenever you open a new Bash session that can be used to run various commands to set up variables the most common being the PATH variable.

Related Solutions

Delete things from $PATH

If you just typed in the exports into the terminal as noted above then the variables in the environment will only last until you exit that terminal session. So simply typing exit and then reopening another terminal will remove any setting that you applied with the noted exports performed in your question.

export MAGICK_HOME="/Library/ImageMagick-6.7.5/"
export PATH="$MAGICK_HOME/bin:$PATH"
export DYLD_LIBRARY_PATH="$MAGICK_HOME/lib/"

Additionally you can un set variables from the environment by using the unset command.

For example:

unset MAGICK_HOME # will remove MAGICK_HOME from the environment.

You can do it for the others as well but if you do it for PATH you will lose your path setting until you close this terminal session and reopen a new window,etc.

As an experiment try typing:

env | grep MAGICK_HOME

You should see MAGICK_HOME=/Library/ImageMagick-6.7.5/ echoed back if its still in the environment. If its not then the settings have already been lost by a windows close. etc re-enter your export of MAGICK_HOME and try the above command again.

then

exit

and then finally re open a new terminal window and enter:

env | grep MAGICK_HOME

Your settings should be gone for MAGICK_HOME. The same is true for the modification done to all the other environment variables set with the export command right in a terminal session. They will just return to their default values if you have not set them in a start-up invocation file as required for your shell environment variables to have a more permanent place in your shell enviorment.

Strange path environment

The issue is how you have uninstalled python. Deleting the app does remove the code but does not affect anything you have changed elsewhere will not have been undone. In this case the changes to the path have not been undone and as the installer is a simple one it keeps adding the new bit of the path to the existing path.

To fix the path you need to find the file where the PATH environment variable is altered. If you are using the bash shell (the default in recent OSX) then. . ideally it should be ~/.bashrc but probably ~/.profile or ~/.bash_profile. See other questions or manuals on what startup file bash uses) Then edit this file so that you have only one Python in it, the lines changing PATH will begin export PATH=

In general things are uninstallable if only you know exactly what they changed in install and what they write to at run time. There is no generic way to do this. The best apps have uninstallers which will do the best. You can stop the app running by deleting the .app bundle and most configuration takes up little disk space so the cost of leaving it is not high. Also most .apps do not need edits in bash files so are more self contained.

Best Answer

Related Solutions

Delete things from $PATH

Strange path environment

Related Question