Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
From: richardson@evansville.edu
Date: Fri, 02 Mar 2001 17:57:21 GMT
Message-ID: <20010302.17572189@ar63pc.cecs.evansville.edu>
Subject: Re: how2 read value of DOS env var containing a "." ?
To: Earnie Boyd <cygwin@cygwin.com>
CC: rodmant@pounder.sol.net, cygwin@sources.redhat.com
Reply-To: richardson@evansville.edu
In-Reply-To: <3A9FDC79.EF1EE20F@yahoo.com>
References: <20010302.17261236@ar63pc.cecs.evansville.edu> <3A9FDC79.EF1EE20F@yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

It's kind of obvious that it was programmed not too, isn't it?
I was just kind of wondering out loud about why a dot was not
allowed as a legal character in a variable name by the bash
designers.

I don't think it is a good idea to modify bash so that you
can write scripts that aren't compatible with original bash.
A workaround is called for here.  That's what I suggested.

Tony Richardson

>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 3/2/2001, 11:46:33 AM, Earnie Boyd <earnie_boyd@yahoo.com> wrote 
regarding Re: how2 read value of DOS env var containing a "." ?:


> richardson@evansville.edu wrote:
> >
> > Not pretty, but works:
> >
> > bashvar=$(set | grep DOS.VAR | cut -d= -f2)
> >
> > (I didn't know that bash vars couldn't have "."s in their
> > names. I wonder why not?)
> >

> Uhm, just because it was programmed not too?  Use the source, Luke.
> (tm)  It is very easily modifiable.

> Earnie.

> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com


> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple