Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <4.3.1.2.20000413112823.00d932e0@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Thu, 13 Apr 2000 11:29:29 -0400
To: jase AT deadbeets DOT com
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: bash expansion question
Cc: "cygwin AT sourceware DOT cygnus DOT com" <cygwin AT hotpop DOT com>
In-Reply-To: <38F5E5C8.C2C713C7@deadbeets.com>
References: <3 DOT 0 DOT 5 DOT 32 DOT 20000412235451 DOT 00939d30 AT pop DOT ma DOT ultranet DOT com>
 <4 DOT 3 DOT 1 DOT 2 DOT 20000413110254 DOT 00d93cf0 AT pop DOT ma DOT ultranet DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

sh.exe is ash and ash is quicker for configuring (though less feature rich,
which causes some configures trouble...)

Larry


At 11:20 AM 4/13/00, Jason Dufair wrote:
>Many thanks, Larry.  Indeed sh was != bash.  I renamed sh.exe and linked
>sh to bash and voila!
>
>Now, I suppose there's a good reason that cygwin was set up this way out
>of the box.  If anyone could enlighten me with that reasoning, I'll be
>able to rest easily then.  I am not intending to criticize, just to
>learn a bit more.
>
>Thank you.
>
>"Larry Hall (RFK Partners, Inc)" wrote:
> > 
> > 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...
> > >
> > >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)?
> > 
> > Larry Hall                              lhall AT rfk DOT com
> > RFK Partners, Inc.                      http://www.rfk.com
> > 118 Washington Street                   (508) 893-9779 - RFK Office
> > Holliston, MA 01746                     (508) 893-9889 - FAX
> >                                         (508) 560-1285 - cell phone
>
>-- 
>Jason Dufair - jase AT deadbeets DOT 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 AT sourceware DOT cygnus DOT com