Re: stupid spaces in environment vars

David Bear wrote: Brian Dessent wrote: David Bear wrote: Okay, the problem is in quoting in shell scripts, I think. Here's an example: #!/usr/bin/bash curdir=`pwd` echo $curdir prodir=`cygpath $USERPROFILE` Should be: prodir=$(cygpath "$USERPROFILE") echo $prodir cd $prodir Should be:

Re: updated bash to latest 3.1.17(8)-release; startup has errors now

Christopher Faylor wrote: On Mon, Oct 02, 2006 at 03:53:42PM -0700, Brian Dessent wrote: "DePriest, Jason R." wrote: I just want to know if anyone else has experienced this or if not, what I can check out or examine to fix it. I've also got this problem with "make" saying "target pattern conta

Re: Potential bug in sshd

Michael Sowka wrote: Thanks Rob, Ah yes, this explains the "zombie" processes as I cannot make actual client connections. Something is very bizarre with my cygwin setup here. I've noticed other symptoms too: on reinstalling cygwin the info-update and cygwing post-install scripts hang. In fact,

Re: Problem when using variable assignment, backticks in shell script

One may also do: read x < temp in bash Tristen Brian Dessent wrote: "Silva, Russell" wrote: x=`/usr/bin/cat < temp`; I don't know what is causing your problem. I ran your testcase several times and never saw a failure, but from your description it seems like it's the kind of thing that m