From:	"Mark E." <snowball3 AT bigfoot DOT com>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date:	Wed, 31 May 2000 13:34:26 -0400
MIME-Version:	1.0
Subject:	Re: __dosexec_find_on_path question
Message-ID:	<393514E2.16889.426125@localhost>
X-mailer:	Pegasus Mail for Win32 (v3.12c)
Reply-To:	djgpp-workers AT delorie DOT com

> > Does the same thing need to be done to __dosexec_find_on_path?
> > 
> > Sorry, I didn't understand this question.  We *are* talking about
> __dosexec_find_on_path, aren't we?
> 

Let's reset so we're all on the same page.
We have two files in a directory. Let's name them 'script' and 'script.sh'. 
At the Bash command line, I do this:
bash-2.04$ ./script

script.sh would execute in Bash 2.04 up until a few days ago. I was using 
__dosexec_find_on_path, but even when I stopped using it, script.sh would 
still get executed. This is because __spawnve searches for extensions just 
like  __dosexec_find_on_path. So __spawnve would find and execute script.sh 
instead of 'script' not matter what we do to __dosexec*. Therefore it is 
__spawnve that needs to be fixed up and not __dosexec*.

- Raw text -