Message-Id:	<m10QVZV-0001hvC@sloep103.cs.vu.nl>
Date:	Fri, 26 Mar 99 13:18:45 MET
From:	Michel de Ruiter <mdruiter AT cs DOT vu DOT nl>
To:	djgpp-workers AT delorie DOT com
Subject:	Re: Bash 2.03 update (March 19th)
Reply-To:	djgpp-workers AT delorie DOT com

In your letter dated Wed, 24 Mar 1999 20:10:26 -0500, you wrote:
>    - when `filename' is run, `filename.bat' has preference above
>      `filename'
> Why do you think this is wrong?  I think this is the correct order (it
> has nothing to do with Bash, btw, it's due to  change in libc.a).

Uhm, well, it wasn't like this in Bash-1.14.7 (because it used an
older libc :) so I wasn't used to it.

I have, next to the autoconf script, an autoconf.bat which does a
`bash autoconf', so I don't have to remember typing `bash' before it.
If I type `autoconf' in Bash, this worked ok with Bash-1 of course
(which ran autoconf just like that IIRC). It should also work with
Bash-2 (if Bash/spawnv would use COMMAND.COM to run autoconf.bat which
uses Bash again...) but somehow Bash was used to run autoconf.bat.
That's how I noticed it, and as I did not expect it, I thought it was
a bug.

BTW, I understand why spawnv has preference for the *.bat, but it
quite surprised me in Bash. If I say `autoconf' in Bash, I would like
Bash to run autoconf, not autoconf.bat. Now I would have to say
`autoconf.' to explicitly run autoconf. But, as the batchfile and the
script should to the same, it doesn't really matter.

I think it is because of my alternative setup that I noticed the
change of behaviour in the first place, and I agree spawnv is right.

--
*Groeten, Michel*.      _http://www.cs.vu.nl/~mdruiter_
   ____________ 
   \  /====\  /         "You know, Beavis, you need things that suck,
    \/      \/           to have things that are cool", Butt-Head.

- Raw text -