Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: Sam Edge To: cygwin@cygwin.com Subject: Re: behaviour of "for (( exp1; exp2; exp3 )); do COMMANDS; done" Date: Wed, 28 May 2003 15:22:36 +0100 Organization: . Reply-To: cygwin@cygwin.com Message-ID: <77h9dvo3rjbopg45hi1ec65igvfv6i2lkg@4ax.com> References: <002901c32427$2e1553e0$78d96f83@pomello> <20030527120718.GA22030@convex.org.uk> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Posting-Agent: Hamster/2.0.0.1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h4SEN6M14143 Harald Maier wrote in in gmane.os.cygwin on Wed, 28 May 2003 13:28:43 +0200: > > (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 } Erm ... doesn't this just duplicate the problem? How can you guarantee that "env" is always in /usr/bin? It's also pretty inefficient, isn't it? Ho hum ... off topic thread alert! Mea culpa. ;-) Regards, -- Sam Edge -- 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/