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
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<62835D8790DBD111981100805FA7E4C405605A53@EXPRESS1>
From:	"Kirschner, Paul E. UTRC" <KirschPE AT UTRCCT DOT res DOT utc DOT com>
To:	"'cygwin'" <cygwin AT cygwin DOT com>
Subject:	tcsh changes with spaces in path
Date:	Thu, 13 Feb 2003 09:32:12 -0500

The latest tcsh change...

I've updated the version of tcsh to 6.12.00-4.
- /etc/csh.login now preserves spaces in pathnames when evaluating $path.

breaks my .cshrc. Several paths in my win2000 system path (from the
environment variables section) are of the form "c:\program files\...". That
space now breaks  my cshrc lines like...

setenv PATH $PATH":/d/jdk1.3.1/bin"

The space seemingly adds a third argument - which is illegal.

Wasn't the space "\" prefixed before? Can we go back in functionality on
this? What advantage do we get with the raw space? Any recommendations for
getting around this problem?

thanks...

----------------------------------------------------------------------------
-------------
Paul Kirschner
Systems Department
United Technologies Research Center
kirschpe AT utrc DOT utc DOT com
(860)610-7119


--
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/

- Raw text -