RE: incompatible environment variable names

2010-08-06 Thread Daniel Colascione
Nellis, Kenneth: > I came across an interesting (IMHO) incompatibility between Windows and bash > environment variable names. You can create odd environment names on Unixish systems too, but nobody relies on them. I've had the same issue; a build environment I use required the presence of vari

Re: incompatible environment variable names

2010-08-04 Thread Andrey Repin
Greetings, Nellis, Kenneth! > Well, *somehow* it got into the Cygwin environment, and cygwin.bat directly > invokes bash, so I interpret this as bash creating the Cygwin environment. > Where is the hole in this logic? Even windows itself creates environment variables inaccessible through CMD. Sti

Re: incompatible environment variable names

2010-08-04 Thread Corinna Vinschen
On Aug 4 13:59, Nellis, Kenneth wrote: > > From: Steven Collins > > On Wed, Aug 4, 2010 at 10:23, Nellis, Kenneth wrote: > > > [...] > > > So, Windows has no problem with + symbols in variable names, but > > > bash does, kinda sorta: > > > [...] > > > > From the bash man page: > > > > > Hench b

Re: incompatible environment variable names

2010-08-04 Thread Eric Blake
On 08/04/2010 12:59 PM, Nellis, Kenneth wrote: >> From: Steven Collins >> On Wed, Aug 4, 2010 at 10:23, Nellis, Kenneth wrote: >>> I came across an interesting (IMHO) incompatibility between >>> Windows and bash environment variable names. Not just windows, but any system with environment variable

Re: incompatible environment variable names

2010-08-04 Thread Andy Koppe
On 4 August 2010 19:59, Nellis, Kenneth wrote: >> > Cygwin> export QNX_VISUAL_C++_PATH="$(cygpath "$(printenv >> QNX_VISUAL_C++_PATH)")" >> > -bash: export: `QNX_VISUAL_C++_PATH=/cygdrive/c/Program Files/Orbital >> Qnx VisualC++ IDE': not a valid identifier >> > Cygwin> >> > >> > I probably need to

RE: incompatible environment variable names

2010-08-04 Thread Nellis, Kenneth
> From: Steven Collins > On Wed, Aug 4, 2010 at 10:23, Nellis, Kenneth wrote: > > I came across an interesting (IMHO) incompatibility between > > Windows and bash environment variable names. > > > > I have a Windows environment variable as such: > > > > C:\>set QNX_VISUAL_C++_PATH > > QNX_VISUAL_C+

Re: incompatible environment variable names

2010-08-04 Thread Steven Collins
On Wed, Aug 4, 2010 at 10:23, Nellis, Kenneth wrote: > I came across an interesting (IMHO) incompatibility between > Windows and bash environment variable names. > > I have a Windows environment variable as such: > > C:\>set QNX_VISUAL_C++_PATH > QNX_VISUAL_C++_PATH=C:\Program Files\Orbital Qnx Vis