Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 21 Aug 2004 12:21:10 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: environment variable name converted to upper case Message-ID: <20040821162110.GA3596@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <5C97FD5F888F6C41B267BBBCE94DC4E71B4E75 AT inhyms21 DOT ca DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5C97FD5F888F6C41B267BBBCE94DC4E71B4E75@inhyms21.ca.com> User-Agent: Mutt/1.4.1i On Sat, Aug 21, 2004 at 09:30:53PM +0530, Koduru, Seshasai wrote: >An environment variable name defined in windows environment with >lowercase is converted to uppercase by cygwin environment. > >Because of this behavior the shell scripts are not recognizing >$lowercase variable. Is this the regular expected behavior? Yes. >Is there any way to get the case preserved? Don't set the environment variable at the windows level. Set it in the shell prior to running the program. If that isn't adequate, then there probably isn't any way to do what you want. -- 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/