X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <2BF01EB27B56CC478AD6E5A0A28931F20130250E@A1DAL1SWPES19MB.ams.acs-inc.net>
References: <AANLkTi=W1mfktf7Nri6B=fYPHTxwSqa-6O3tDuQL6KnU AT mail DOT gmail DOT com>	<2BF01EB27B56CC478AD6E5A0A28931F20130250E AT A1DAL1SWPES19MB DOT ams DOT acs-inc DOT net>
Date: Wed, 4 Aug 2010 20:06:07 +0100
Message-ID: <AANLkTinzjP1rJ0Xr4K4J7W3HpENYAQziKEfbPHo+iX+L@mail.gmail.com>
Subject: Re: incompatible environment variable names
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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 give up on this, but felt like sharing my misery.
>>
>> bash does not support the plus character in a variable name and
>> no amount of finagling is going to fix it.
>
> 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?

The Windows environment is translated by the Cygwin DLL, which gets
loaded and initialised when bash.exe is invoked.

Andy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple