Date: Thu, 8 Feb 2001 10:08:05 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Probably a bug in bash 2.04
In-Reply-To: <3A81836F.22564.961DF@localhost>
Message-ID: <Pine.SUN.3.91.1010208100744.20284D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 7 Feb 2001, Mark E. wrote:

> I've dug a little deeper into the problem. If you try to run 'foo.sub' when 
> LFN=N, __spawnve will look for 'foo.exe', 'foo.bat', etc. and not run 
> 'foo.sub'. This makes no sense. Why does it do this?

Probably because it doesn't consider files without a recognized
extension to be executable (in the absence of the exec mode bit).

Anyway, this was so from time immemoriam, and it looks like every
application was either living with it or working around it, like Bash
2.03.

We can change this, I think, but the change should make sure the files
which don't have a recognized extension go directly to script_exec.