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:
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 course causes
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) path, use
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##`
Alternatively,
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
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 causes problems. Would a
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
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
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
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 to this? It
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
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
12 matches
Mail list logo
