Re: bash 3.2.49-22 problem (subscripts fail to run sometimes)

Hello Eric, Your suggestion helped. It turned out to that McAffe's virus scanner was screwing up Cygwin. Killing it made the script work. Thanks. Sincerely, Vitas Povilaitis On Wed, Jul 22, 2009 at 8:19 AM, Eric Blake wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > According to V

Re: bash 3.2.49-22 problem (subscripts fail to run sometimes)

Vitas Povilaitis wrote: > Occasionally, a subscript fails to run, as in this example: > $ ./t.sh Hello-1.0.0 > PACKAGE Hello VERSION 1.0.0 > PACKAGE Hello VERSION > PACKAGE Hello VERSION 1.0.0 > > $ ./t.sh Hello-1.0.0 > PACKAGE Hello VERSION 1.0.0 > PACKAGE Hello VERSION 1.0.0 > PACKAGE VERSION

Re: bash 3.2.49-22 problem (subscripts fail to run sometimes)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Vitas Povilaitis on 7/22/2009 6:15 AM: > $ ./t.sh Hello-1.0.0 > PACKAGE Hello VERSION 1.0.0 > PACKAGE Hello VERSION > PACKAGE Hello VERSION 1.0.0 > This is under Cygwin 1.5.25-15 under Windows XP Ver. 5.1 Build 2600 > Service Pack 2. It c

bash 3.2.49-22 problem (subscripts fail to run sometimes)

Occasionally, a subscript fails to run, as in this example: $ cat t.sh #!/bin/bash PACKAGEVERSION=$1 PACKAGE=`echo $PACKAGEVERSION | sed 's/^\(.*\)-.*$/\1/'` VERSION=`echo $PACKAGEVERSION | sed 's/^.*-\(.*\)$/\1/'` echo "PACKAGE $PACKAGE VERSION $VERSION" PACKAGE=`echo $PACKAGEVERSION | sed 's/