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 Message-ID: <41A6D980.41FE183F@dessent.net> Date: Thu, 25 Nov 2004 23:21:36 -0800 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: PATH and SystemRoot oddity References: <20041126064717 DOT 0A1A4837CA AT pessard DOT research DOT canon DOT com DOT au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Luke Kendall wrote: > I see that by default PATH includes some entries like > %SystemRoot%/System32 > > I also note that $SystemRoot is undefined, yet $SYSTEMROOT contains the > expected C:\WINDOWS value. > > This of course causes problems. Would a backslash-style path work > correctly if it were properly interpolated into the PATH? Is the % > notation special magic for Cygwin to handle DOS-isms? > > The case variance may be of interest, in that case. I think you're falsely attributing your errors to this. The cygwin DLL takes care of all the win32 -> posix translation of the path, and it knows about %SystemRoot%. If this were really the case don't you think tons of things would break? Try "echo $PATH" at your shell prompt and you'll see that the systemroot is correctly substituted. FWIW, I think environment variables are case-insensitive at the win32 API level. They preserve case but are not sensitive to it, just like ntfs. Brian -- 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/