From: Craig S. <sut...@ma...> - 2003-04-30 04:33:12
|
Greg, I didn't keep your earlier question, but you need to add /sw/bin:/sw/sbin to your path for Fink files and /usr/local/bin:/usr/X11R6/bin for X11 files. The colon delimits the string in PATH. There are several files that can configure Terminal when it starts. In your Home directory (~/) there could be .tcshrc and/or .cshrc. The period before the file name means that the file is invisible to the GUI environment, but you can see it in the Terminal. From the Terminal type: cd ~/ .... and then enter ls -al ... and enter Look for the 2 files mentioned above. If .tcshrc is there, type pico .tcshrc in the Terminal. Pico is a text editor. If .tcshrc has info in it, use the arrow keys to move to a new line. Type in: setenv PATH /usr/local/bin:/usr/X11R6/bin:/sw/bin:/sw/sbin. The control-o to write the file "out". Y to confirm overwriting, and last control-x to exit pico. If only .cshrc is found, use the info above, substituting .cshrc for .tcshrc. If neither is there, you will create the .cshrc file with pico. Same as above, except you will not be asked to confirm overwriting to existing file. Restart the Terminal and see if this does the trick. I hope all this is right. It took a lot of hunting for info about PATH and Shells to even begin to get my PATH working as I wished. Craig > This is what I get when I run the following command in terminal: > > greghyde% printenv PATH > /bin:/sbin:/usr/bin:/usr/sbin > [blueDog:~] greghyde% > >>> My guess would be that your PATH is incorrect. What do you get from >>> running >>> >>> printenv PATH >>> >>> in a terminal window. |