This is the mail archive of the
mailing list for the Cygwin project.
Re: Environment var PATH broken in 1.3.9 - spaces NG
The path to MSVC is set in the registry (i.e. Control panel > system >
advanced > environment (or however you get there)). To be even more precise
tcsh inherits the environment from bash which inherits it from cmd.exe
which gets it from the registry somehow.
Sorry I didn't mention that.
If I execute 'tcsh -l' at a cmd.exe prompt the behavior is the same. (I
didn't know I could do that! I thought I needed bash to read /etc/profile
to get everything setup.)
I'm busy switching to bash anyway...
At 12:48 PM 1/24/2002 -0800, "Michael A Chase" <email@example.com> wrote:
>When I start either tcsh or bash from the MSDOS prompt with your MSVS
>directory in the path, $PATH is translated correctly. Are you adding the
>directory to your path after tcsh has started?
>If you are adding the MSVS directory in .login or .cshrc, you need to be
>sure to quote properly or tcsh may be taking the spaces as separators.
>I don't actually have MSVS, so I can't confirm or deny the problem you are
>having with varying cases. I have seen other messages that report problems
>with directory specifications that contain spaces.
>** I normally forward private questions to the appropriate mail list. **
>Give a hobbit a fish and he eats fish for a day.
>Give a hobbit a ring and he eats fish for an age.
>----- Original Message -----
>From: "Richard Kandarian" <firstname.lastname@example.org>
>Sent: Thursday, January 24, 2002 12:26
>Subject: Environment var PATH broken in 1.3.9 - spaces NG
> > I'm using MS Visual C++ executables installed in:
> > C:\Program Files\Microsoft Visual Studio\VC98\Bin
> > and for some reason they all have filenames which are all caps.
> > With tcsh in 1.3.8 some of the commands will complete and/or be found
> > either upper or lower case (e.g. cl.exe) and others will only complete
> > and/or be found if typed uppercase (e.g. NMAKE.EXE).
> > Now in 1.3.9 the PATH environment variable in tcsh has all the spaces in
> > the above path replaced with ':' and I have to type in the full path to
> > the Visual C++ stuff. The path (not PATH) in tcsh, which is a translation
> > of the PATH variable, does not have the spaces replaced with ':'.
> > I guess I need to translate my .login and .cshrc to something bash can
> > read... sigh.
Any opinions stated in this message are mine and not expressed on behalf of
any other individual or entity unless explicitly noted otherwise. As for
the links at the very end, my opinion is that they are interesting.
UNIX is software. M$ Windows is hardware implemented in software.
When M$ says 'embrace and extend', what does that bring to mind?
A huge boa constrictor?
Save the world from M$ tyranny - embrace and extend LINUX before M$ does.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html