I have written a number of scripts, basically to recursively manipulate files and images in directories. I have to copy the scripts into the pwd to run them, which becomes burdensome.
How can I export the path to a bash script so wherever I am in the system I can do
$ sh myscript.sh
without myscript.sh being in the precise pwd of the moment?
Thanks!

I would recommend to copy them in /usr/local/bin

Thnx, but I bumped into this problem.
One script is a csh one.
When I place it at /usr/local/bin and do
$ csh myscript.sh
myscript: No such file or directory
$ sh myscript.sh
returns syntax errors (my default shell is a bash one).

Can you explain better:
- how do you fail to export your path to subshells ?
- why do you need to launch your script with "sh script" instead of "script" ?

that does not make sense.
It should be:also consider putting #!/bin/csh as the first line in the script and give execute permission to the script
and run it as

Giving .sh as an extension for a csh script doesn't make sense either.

Even writing a csh script doesn't make sense nowadays.

THATS SO TRUE..........

well, I had rewritten the script in bash by the time at looked back at the post.

Thnx.

I would go with perfect-circle's advice of putting the she-bang (#!/bin/...) line at the beginning of each script. That way you don't have to figure out what shell goes with which script. It is both self documenting and self running.

To execute a script from anywhere on your system it needs to be in your $PATH environment variable. It is common to place scripts that anyone can execute in /usr/local/bin. If you are a user and want to execute scripts that you wrote, place them in your own bin and make sure this gets into your $PATH. For example if your user name is scooby then put your scripts in /home/scooby/bin.

Bill

All right, I understand.
Thank you!