Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<42779E99.5E6192A2@dessent.net>
Date:	Tue, 03 May 2005 08:54:01 -0700
From:	Brian Dessent <brian AT dessent DOT net>
MIME-Version:	1.0
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	Re: echo "$(echo '\r')" oddity
References:	<D1D50F9C5151D2119FF000104BB3F9B708E1B755 AT NL-ROT-MAIL02>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

Jan Just Keijser wrote:

> thx for the quick answer. Lemme guess: I am going to have to build my own
> version of bash that does not have this behaviour... what is going to break
> if I undo this patch from the bash source code?
> 
> It's a shame though, coz this seems to be the only issue that stops that
> nifty socat from working... all tests pass except those tests that use `` or
> $() ...

My guess is that that patch was added so that command substitution on
windows programs works.  Or something to that effect.  You could
certainly recompile without it, and see what happens.

But the question that I think we're left with is what exactly is socat
doing that is broken by this?  If you give examples I'm sure someone
here will be able to show you a way to do what you want without patching
anything.  Note: I have no idea what socat is...

Brian

--
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/

- Raw text -