Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 To: cygwin@cygwin.com From: Shankar Unni Subject: Re: environment variable name converted to upper case Date: Mon, 23 Aug 2004 14:13:56 -0700 Lines: 9 Message-ID: References: <20040822144651.GA3391@coe.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: adsl-68-120-146-125.dsl.snfc21.pacbell.net User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Thunderbird/0.7.3 Mnenhy/0.6.0.101 In-Reply-To: <20040822144651.GA3391@coe.casa.cgf.cx> X-IsSubscribed: yes Christopher Faylor wrote: > To repeat, translating environment variables to uppercase is something > that *cygwin* does. Check out environ.cc for more information. Could the uppercasing be limited to certain environment variables? Particularly, only PATH, since that's common to both NT and Posix shells, but that NT allows in any case while Posix shells expect in uppercase? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/