This is the mail archive of the cygwin@sources.redhat.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: how2 read value of DOS env var containing a "." ?


The guy (Bob) at work that asked me the original question came up
with this soln:

  set HACK=FOO.BAR ; echo ${!HACK} ; FOO_BAR=${!HACK}

Thanks Tony and Earnie for your help!

-Tom

On Fri 3/2/01 17:57 GMT richardson@evansville.edu wrote:
>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=20
>regarding Re: how2 read value of DOS env var containing a "." ?:
>
>
>> richardson@evansville.edu wrote:
>> >
>> > Not pretty, but works:
>> >
>> > bashvar=3D$(set | grep DOS.VAR | cut -d=3D -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

------- End of Unsent Draft

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]