To: cygwin@cygwin.com
From: Jerome Fong <jfong@successmetricsinc.com>
Subject:  Re: cygpath -u  doesn't seem to convert spaces properly
Date:  Wed, 26 Sep 2007 11:22:13 -0700
Lines: 31
Message-ID: <fde80l$v4k$1@sea.gmane.org>
References:  <46F9AA3C.3227153@dessent.net> <4C89134832705D4D85A6CD2EBF38AE0F0131EF8F@PAUMAILU03.ags.agere.com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
In-Reply-To: <4C89134832705D4D85A6CD2EBF38AE0F0131EF8F@PAUMAILU03.ags.agere.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Thanks,

Jerome

Williams, Gerald S (Jerry) wrote:
> Brian Dessent wrote:
>>> $ cd $ttt
>>> bash: cd: /cygdrive/c/Program: No such file or directory
>> Yes, that's wrong.  [...] It's got nothing to do with
>> cygpath and everything to do with proper portable scripting practice.
> 
> Quite true. When you're using bash or sh, you must *quote
> your arguments* if they could possibly contain spaces or
> other word separators. So learn to do it. Seriously, take
> a few minutes and try it:
> 
> $ mkdir "a b c"
> $ ABC="a b c"
> bash: cd: a: No such file or directory
> $ cd "$ABC"
> ... etc.
> 
> If you don't want to have to quote variable expansions all
> the time, use another shell. I know that zsh, at least,
> doesn't require you to quote them. That being said, you
> still should learn how to quote in a regular POSIX shell.
> Portable shell scripts should really start with #!/bin/sh,
> after all.
> 
> -gsw
> 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/