>phonetic.pl is not in your path. If you try:
>../phonetic.pl
>it should run.
You do need to set the execute bit in the permissions for the file.
chmod 777 phonetic.pl - does more than you want but will do the trick.
>If you are running the default shell, tcsh, you can add the following line to
>~/.cshrc:
>setenv PATH ${PATH}:.
>That way the current directory (.) is always in your path.
But take the time to learn about the rehash command. The shells make up a table of
commands each time the PATH environment variable is changed. Given the performance of
modern processors one wonders why that's still appropriate.
If you do your development in a directory that's in your path and create and store a
new file, with #! line and execute bit set, it won't become executable until you
rehash. Including "." in your path probably causes a rehash but only as you enter a
directory. Adding the ./ in ./phonetic.pl does that but also provides a full path
removing the requirement for being in $PATH at all.
There is an environment variable, something like NOHASH, that will turn hashing off
altogether and I doubt that OS neXt users will ever miss it. Set it in ~.cshrc or
~/.tcshrc. Setting it in ~/.login is not reliable if, for instance, you want to
execute from AppleScript or BBEdit. (~/.MacOSX/environment.plist is another way)
--
--> There are 10 kinds of people: those who understand binary, and those who don't
<--
