Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 13 Feb 2003 16:06:45 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: tcsh changes with spaces in path Message-ID: <20030213150645.GR5822@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <62835D8790DBD111981100805FA7E4C405605A53 AT EXPRESS1> <20030213145227 DOT GE27226 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030213145227.GE27226@redhat.com> User-Agent: Mutt/1.4i On Thu, Feb 13, 2003 at 09:52:27AM -0500, Christopher Faylor wrote: > On Thu, Feb 13, 2003 at 09:32:12AM -0500, Kirschner, Paul E. UTRC wrote: > >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? > > setenv PATH "$PATH"":/d/jdk1.3.1/bin" or set path = ( $path:q "/d/jdk1.3.1/bin" ) I'm surprised you don't see the advantage in having the ability to add also these incredible Win paths with spaces in them to $path. If you don't want to have them in $path, just remove them in your local .login or .cshrc file. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/