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 09:52:27 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: tcsh changes with spaces in path Message-ID: <20030213145227.GE27226@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <62835D8790DBD111981100805FA7E4C405605A53 AT EXPRESS1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <62835D8790DBD111981100805FA7E4C405605A53@EXPRESS1> User-Agent: Mutt/1.5.1i 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" cgf -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam AT sourceware DOT org and be permanently blocked from mailing lists at sources.redhat.com -- 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/