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
Date:	Tue, 27 May 2003 12:02:10 +0100
To:	cygwin AT cygwin DOT com
Subject:	Re: behaviour of "for (( exp1; exp2; exp3 )); do COMMANDS; done"
Message-ID:	<20030527110210.GA21745@convex.org.uk>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<002901c32427$2e1553e0$78d96f83 AT pomello> <PHENJGDFMJPEBOBLGEMOKENMCBAA DOT peter DOT oosterlynck AT oracle DOT com>
Mime-Version:	1.0
In-Reply-To:	<PHENJGDFMJPEBOBLGEMOKENMCBAA.peter.oosterlynck@oracle.com>
User-Agent:	Mutt/1.5.3i
From:	Stuart Brady <stuart AT convex DOT org DOT uk>

On Tue, May 27, 2003 at 10:45:50AM +0200, Peter Oosterlynck wrote:

> My workaround: added "#!/usr/bin/bash" in my cygwin script.

I'm not sure that this isn't the correct approach in the first place.
Of course, bash isn't always going to be /usr/bin/bash, so maybe you
really want "#!/usr/bin/env bash" or something. Either way, you
shouldn't be suprised to see bash or tcsh-specific shell scripts
rejected by whatever your /bin/sh happens to be. This will most likely
affect Solaris, HP-UX, FreeBSD and many others. It also affect Linux if
your distribution's /bin/sh isn't what you expected it to be.
-- 
Stuart Brady

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