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
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
Jerome Fong wrote on Tuesday, September 25, 2007 6:23 PM:
I am trying to use cygpath -u to convert my windows path to an unix
path in my shell script. However, it has problems with paths that
has spaces in it. For example, cygpath -u c:\Program Files\Java is
converted to /cygdrive/c/Program
Jerome Fong wrote:
I am trying to use cygpath -u to convert my windows path to an unix path
in my shell script. However, it has problems with paths that has spaces
in it. For example, cygpath -u c:\Program Files\Java is converted to
/cygdrive/c/Program Files/Java, which doesn't work. Is
It seems to be a quoting problem. This is what I was doing:
$ ttt=$(cygpath -u $JAVA_HOME)
$ echo $ttt
/cygdrive/c/Program Files/Java/jdk1.5.0_10
$ cd $ttt
bash: cd: /cygdrive/c/Program: No such file or directory
$ cd $ttt
$pwd
/cygdrive/c/Program Files/Java/jdk1.5.0_10
Is is possible to
Jerome Fong wrote:
$ cd $ttt
bash: cd: /cygdrive/c/Program: No such file or directory
Yes, that's wrong. But more importantly, it's not wrong just in the
POSIX/Win32 path sense, it's wrong in the sense that it can't cope with
any argument that contains whitespace. Your script would also fail
6 matches
Mail list logo
