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
From:	ericblake AT comcast DOT net (Eric Blake)
To:	cygwin AT cygwin DOT com
Subject:	Re: base-files patch
Date:	Fri, 25 Mar 2005 18:34:26 +0000
Message-Id:	<032520051834.18021.424459B2000099DD0000466522058891160A050E040D0C079D0A@comcast.net>
X-Authenticated-Sender:	ZXJpY2JsYWtlQGNvbWNhc3QubmV0

> On Fri, 25 Mar 2005, Eric Blake wrote (snipped):
> 
> 
> Most shells understand "`""`" (particularly, all official shells on
> Cygwin, which is what's important).

True enough, and I concede that POSIX requires it to work.

>  In fact, in this particular case,
> it's probably better to use "``" instead of `""`, IMO.

No, "`echo $0|tr ...`" does the wrong thing if $0 is "two  spaces/sh" (it passes just one space to tr, instead of two), while `echo "$0"|tr ...` works correctly.



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