This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: how2 read value of DOS env var containing a "." ?
- To: Earnie Boyd <cygwin at cygwin dot com>
- Subject: Re: how2 read value of DOS env var containing a "." ?
- From: richardson at evansville dot edu
- Date: Fri, 02 Mar 2001 17:57:21 GMT
- CC: rodmant at pounder dot sol dot net,cygwin at sources dot redhat dot com
- References: <20010302.17261236@ar63pc.cecs.evansville.edu> <3A9FDC79.EF1EE20F@yahoo.com>
- Reply-To: richardson at evansville dot edu
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