X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL,BAYES_05,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org From: "Daniel Colascione" To: "'Nellis, Kenneth'" , References: <2BF01EB27B56CC478AD6E5A0A28931F2013024D9@A1DAL1SWPES19MB.ams.acs-inc.net> In-Reply-To: <2BF01EB27B56CC478AD6E5A0A28931F2013024D9@A1DAL1SWPES19MB.ams.acs-inc.net> Subject: RE: incompatible environment variable names Date: Fri, 6 Aug 2010 11:45:55 -0700 Message-ID: <008001cb3597$a51f5920$ef5e0b60$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Nellis, Kenneth: > I came across an interesting (IMHO) incompatibility between Windows and b= ash environment variable names. You can create odd environment names on Unixish systems too, but nobody rel= ies on them. I've had the same issue; a build environment I use required the presence of= variable names with '(' and ')' in them. For the moment, I've hacked aroun= d the issue by calling cmd.exe to do the work before launching the build sy= stem proper, but eventually, in my Copious Free Time(TM), my plan is to pat= ch bash and add raw-getenv and raw-setenv builtins that do the obvious thin= g. -- 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