RE: $PATHEXT not sufficient to run script from BASH without specifying extension on Windows XP?

["Gary R. Van Sickle" <g dot r dot vansickle at worldnet dot att dot net>]

> #
> # I can't seem to execute "testScript.sh" without # 
> specifying its extension:
> #
> $ testScript
> bash: testScript: command not found
> 
> #
> # Although the file is there and executable:
> #
> $ ls -lt testScript.*
> -rwxr-xr-x  1 Owner None 43 Apr 28 11:10 testScript.sh
> 
> #
> # ...and it runs when the extension *is* specified, # thus 
> showing that it's on the $PATH:
> #
> $ testScript.sh
> hello yourself from  ./testScript.sh
> 
> #
> # And ".sh" is in the $PATHEXT variable:
> #
> $ echo $PATHEXT
> .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.SH;.KSH
> 
> #
> # and "#! /bin/bash" is on the first line of the script:
> #
> $ cat testScript.sh
> #! /bin/bash
> echo "hello yourself from " $0
> 
> #
> # What am I missing to be able to run a script from bash # 
> without specifying the extension?
> #
> 
> 

PATHEXT is a Windows NT/etc deal.  Bash doesn't use it, and AFAICT Bash
won't do what you're looking for.  I don't quite get the issue here though;
if you're doing this interactive, just TAB-complete, and if you're doing it
from a script, just specify the full name.

-- 
Gary R. Van Sickle


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/