Re: PATH and SystemRoot oddity

2004-12-01 Thread Luke Kendall
On 1 Dec, Igor Pechtchanski wrote: > The interpolation of the %...% variables into REG_MULTI_SZ values happens > on the Windows level, before Cygwin ever sees them. Windows treats these > variables case-insensitively. > HTH, It does - thanks again, Igor. luke -- Unsubscribe info:

Re: PATH and SystemRoot oddity

2004-12-01 Thread Igor Pechtchanski
On Wed, 1 Dec 2004, Luke Kendall wrote: > On 26 Nov, Igor Pechtchanski wrote: > > On Fri, 26 Nov 2004, 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 >

Re: PATH and SystemRoot oddity

2004-11-30 Thread Luke Kendall
On 26 Nov, Igor Pechtchanski wrote: > On Fri, 26 Nov 2004, 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 co

Re: PATH and SystemRoot oddity

2004-11-27 Thread Igor Pechtchanski
On Sat, 27 Nov 2004, Jason Curl wrote: > Igor Pechtchanski wrote: > > > > First off, you could have actually removed the offending entries > > > > from the PATH using something like > > > > > > > > OFFENDING_ENTRY="/cygdrive/c/ClearCase/bin" > > > > PATH="`echo "$PATH" | sed "s#:$OFFENDING_ENTRY##

Re: PATH and SystemRoot oddity

2004-11-27 Thread Jason Curl
Igor Pechtchanski wrote: First off, you could have actually removed the offending entries from the PATH using something like OFFENDING_ENTRY="/cygdrive/c/ClearCase/bin" PATH="`echo "$PATH" | sed "s#:$OFFENDING_ENTRY##"`" Alternatively, if you want to translate any Win32 path to a Cygwin (POSIX) pat

Re: PATH and SystemRoot oddity

2004-11-26 Thread Igor Pechtchanski
On Fri, 26 Nov 2004, Jason Curl wrote: > Igor Pechtchanski wrote: > > On Fri, 26 Nov 2004, Jason Curl wrote: > > > > > I have a similar question: I had to modify 'profile' to change > > > $PATH=:$PATH > > > to > > > $PATH= > > > > > > How can I simply add $SYSTEMROOT:$SYSTEMROOT/system32

Re: PATH and SystemRoot oddity

2004-11-26 Thread Jason Curl
Igor Pechtchanski wrote: On Fri, 26 Nov 2004, Jason Curl wrote: I have a similar question: I had to modify 'profile' to change $PATH=:$PATH to $PATH= How can I simply add $SYSTEMROOT:$SYSTEMROOT/system32 to this? It doesn't work as-is because $SYSTEMROOT = C:\Windows (and this is therefo

Re: PATH and SystemRoot oddity

2004-11-26 Thread Igor Pechtchanski
On Fri, 26 Nov 2004, 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 >

Re: PATH and SystemRoot oddity

2004-11-26 Thread Igor Pechtchanski
On Fri, 26 Nov 2004, Jason Curl wrote: > I have a similar question: I had to modify 'profile' to change > $PATH=:$PATH > to > $PATH= > > How can I simply add $SYSTEMROOT:$SYSTEMROOT/system32 to this? It > doesn't work as-is because $SYSTEMROOT = C:\Windows (and this is > therefore not

Re: PATH and SystemRoot oddity

2004-11-26 Thread Larry Hall
At 03:14 PM 11/26/2004, you wrote: >Brian Dessent wrote: >>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 caus

Re: PATH and SystemRoot oddity

2004-11-26 Thread Jason Curl
Brian Dessent wrote: 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

Re: PATH and SystemRoot oddity

2004-11-25 Thread Brian Dessent
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 we