bash expansion question

Don Sharp Don.Sharp@dddandr.octacon.co.uk
Thu Apr 13 10:34:00 GMT 2000


I remember "sh" giving this trouble (short selection) when it is "ash".
Are you sure "sh" == "bash" ?

Cheers

Don

Jason Dufair wrote:
> 
> "Larry Hall (RFK Partners Inc)" wrote:
> >
> > At 09:28 PM 4/12/00 -0500, you wrote:
> > >Hello -
> > >
> > >I have cygwin b20 running on WinNT SP6
> > >
> > >at the command line I get the following:
> > >
> > >$ foo=bar/baz
> > >$ echo ${foo%%/*}
> > >foo
> > >
> > >However, if I have the following in a script:
> > >
> > >foo=bar/baz
> > >echo ${foo%%/*}
> > >
> > >and then run it, I get
> > >$ test.sh
> > >ba
> > >
> > >It seems to be dropping one too many characters.  It seems I've either
> > >found an expansion bug or I'm misunderstanding something.  Testing this
> > >on my linux box (bash 1.14.7), it works as expected.  Can someone
> > >clarify this for me?  Thanks a lot.
> > >
> >
> > Sounds like a text/binary thing to me.  Try setting adding "binmode" to
> > your CYGWIN environment variable and restarting bash...
> 
> Thanks for the suggestion, Larry.  I tried it and it seems to have had
> no effect.  Can anyone duplicate this by chance?
> 
> --
> Jason Dufair - jase@deadbeets.com - PGP key on keyservers
> "So many ways to understand
> One for every woman and man
> Been that way since the world began" - Bruce Cockburn
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com



More information about the Cygwin mailing list