Re: Bash behavior change 2.05b-17 vs 2.05b-16

[Eric Blake <ebb9 at byu dot net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Victor Atkinson on 7/25/2005 1:23 PM:
> I believe that it is Bash itself that is causing this behavior, and not some
> underlying Cygwin mechanism, for two reasons:  First, the backslash format
> of the command works fine under zsh, tcsh, and csh.  Second, backslashed
> paths work fine under Bash, if used as parameters to built-in commands like
> cd, or external commands like wzzip.exe.

Indeed, bash was following the letter of the law of POSIX - it invokes a
PATH search unless the first non-assignment word of the command includes a
'/'.  So in bash-3.0-10, I will patch that to also skip path searches if
the command starts with <letter>: or includes '\\'.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
volunteer cygwin bash maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC5ih884KuGfSFAYARAjeHAJ9izHilVNOdGmbhw9QTU/sacPeD+QCgqbE7
3uPCAPW7QFIngBBJGnOhC3U=
=6JNS
-----END PGP SIGNATURE-----

--
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/