Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <035101c1a518$e8e08170$a100a8c0@mchasecompaq>
From: "Michael A Chase" <mchase AT ix DOT netcom DOT com>
To: <cygwin AT cygwin DOT com>, "Richard Kandarian" <richard DOT kandarian AT lanl DOT gov>
References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020124130457 DOT 02716e58 AT cic-mail DOT lanl DOT gov>
Subject: Re: Environment var PATH broken in 1.3.9 - spaces NG
Date: Thu, 24 Jan 2002 12:48:23 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

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.

WinXP
Cygwin: 1.3.9-1
bash 2.05a-2
tcsh 6.11.00-3
--
Mac :})
** 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" <richard DOT kandarian AT lanl DOT gov>
To: <cygwin AT cygwin DOT com>
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
all
> 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.




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/