🚀 go-pugleaf

kf <ken@cleveland.lug.net> doodled in uk.comp.os.linux:

> Alternatively, put your script in a subdirectory which is in the already
> existing path (do "env | grep -i path" to find out) or include the directory
> in which your script resides in the path; for example, if you have the
> script in your home directory, put the following in your ".profile" file:
> "$PATH=$PATH:$HOME".

That's a bourne shell + derivatives thing. As I said earlier, in csh it's
path, not PATH, you don't export it but you setenv it, and you rehash to get
the shell to look again the next time, although this depends on whether he
really is running (t)csh instead of bash in order to execute the script.

OTOH under no circumstances will '$PATH=$PATH:$HOME' in .profile do what he
wanted it to do! (You've not said to export PATH afterwards, $HOME isn't
necessarily where his script it, and $PATH is not an lvalue...)

-- 
~Tim
 ___ http://www.glutinous.custard.org/ _______ tim@glutinous.custard.org ____
| Geek Code: GCS dpu s-:+ a-- C++++ UBLUAVHSC++++ P+++ L++ E--- W+++(--) N++ |
| w--- O- M-- V-- PS PGP++ t--- X+(-) b D+ G e++(*) h++(*) r--- y-	     |
|  .|` Clouds cross the black moonlight /				     |
|      Rushing on down to the circle of the turning world .|`	(Runrig)     |
`----------------------------------------------------------------------------'