Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: behaviour of "for (( exp1; exp2; exp3 )); do COMMANDS; done" References: <002901c32427$2e1553e0$78d96f83 AT pomello> <20030527120718 DOT GA22030 AT convex DOT org DOT uk> From: Harald DOT Maier DOT BW AT t-online DOT de (Harald Maier) Reply-To: Harald Maier Date: Wed, 28 May 2003 13:28:43 +0200 In-Reply-To: (Sam Edge's message of "Wed, 28 May 2003 11:17:02 +0100") Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Sender: 320041125923-0001 AT t-dialin DOT net Sam Edge writes: > Stuart Brady wrote in > <20030527120718 DOT GA22030 AT convex DOT org DOT uk> > in gmane.os.cygwin on Tue, 27 May 2003 13:07:18 +0100: > >> On Tue, May 27, 2003 at 12:42:21PM +0100, Sam Edge wrote: >> > Make sure that if your script uses Bash-specific features, it starts >> > with #!/bin/bash and not with #!/bin/sh. That way it'll work anywhere. >> >> You've made the assumption that bash is always in /bin. I've seen it >> in /bin, /usr/bin, /usr/local/bin, /usr/contrib/bin, and /opt/bash/bin. >> ~/bin would be another likely place for it. > > I just _knew_ I shouldn't have said "anywhere." ;-) > > Unfortunately this is a general weakness in the "#!/xxxx" syntax. > > (OT) Does anyone know if any of the common shells, when they see > "#!/bin/xxxx" at the front of a script, try a $PATH search for an > "xxxx" executable if they can't find "/bin/xxxx"? This would seem like > a good idea to me. Some people are using the env program to use the PATH environment: #! /usr/bin/env perl BEGIN { $^W = 1 } Harald -- 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/