Mail Archives: cygwin/2000/04/13/11:40:51
: At 10:56 AM 4/13/00, 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...
Don't see what text/binary difference should cause such an effect.
: >Thanks for the suggestion, Larry. I tried it and it seems to have had
: >no effect. Can anyone duplicate this by chance?
:
: No, I can't. Are you sure you're running the same shell in both cases
: (i.e. is sh = bash and is bash what you're running)?
I had the same effect and this was indeed the cause.
Prepending #! /bin/bash to the script was the solution.
Thomas Wolff
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -