Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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: <002601c3612f$8846e2d0$200aa8c0@thorin>
From: "Carlo Florendo" <carlo AT astra DOT ph>
To: <cygwin AT cygwin DOT com>
Cc: "Menon, Girish \(MED, WIPRO-GE MED\)" <Girish DOT Menon AT med DOT ge DOT com>
References: <EF3C4DA34DEFD411AE6200A0C9F2A3581ADE4B66 AT uswaumsx06medge DOT med DOT ge DOT com>
Subject: Re: Backtick does not work
Date: Wed, 13 Aug 2003 08:12:06 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700

----- Original Message -----
From: "Menon, Girish (MED, WIPRO-GE MED)"


> From the bash shell the ` (backtick or command execution) work. But when
> I spawn a process and execute a shell script which contains the back
> ticks, the process just chokes.
>
> For example, a simple shell script like
> #!/bin/sh
> ..
> ..
> myenv=`/bin/env | grep CYGWIN`

Check the permissions of your script.  It should at least be +x for the one who executes it.  Please be more specific on what
doesn't work?  Does echoing not work, say, if you add `echo $myenv' in your script?

By the way, this does not seem to be a cygwin problem.  Kindly check  for more info in http://www.cygwin.com/problems.html

Thanks!

Best Regards,

Carlo
------
Carlo Florendo
Astra Philippines Inc.
URL: http://www.hq.astra.ph/resources







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