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

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

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

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

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

> Victor Atkinson syrres.com> writes: > >> >> Greetings, >> >> I recently updated my Cygwin installation from version 1.5.11-1 to 1.5.17-1. >> As I did so, I also updated all of my packages, including updating Bash from >> version 2.05b-16 to version 2.05b-17. > > As long as you are upgrading,

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

Victor Atkinson syrres.com> writes: > > Greetings, > > I recently updated my Cygwin installation from version 1.5.11-1 to 1.5.17-1. > As I did so, I also updated all of my packages, including updating Bash from > version 2.05b-16 to version 2.05b-17. As long as you are upgrading, why not go al