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 Date: Mon, 23 Aug 2004 22:18:03 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: environment variable name converted to upper case Message-ID: <20040824021803.GA6917@coe.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20040822144651.GA3391@coe.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Mon, Aug 23, 2004 at 02:13:56PM -0700, Shankar Unni wrote: >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? I don't see any reason to do so. This is trivial to work around and cygwin's current behavior has not changed for many years. -- 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/