On 5/19/2010 8:50 AM, Rockefeller, Harry wrote:
Given that 'foo' is a bash script, why is it that:
$ foo
returns the error:
bash: ./bin/foo: No such file or directory
What happens when you directly run ./bin/foo?
I get exactly the same error. The error is correct.
./bin/foo doesn't exist. (I'm not in home directory when
I issue the command.)
What is the shebang (first line) of foo?
#!/bin/bash
I thought it might have something to do with this and tried commenting
It out but nothing changed.
BUT since foo is *really in* PATH, e.g.,
$ `which foo`
runs correctly?
What is the output of "which foo" in this case?
/cygdrive/c/DOCUME~1/harryr/bin/foo