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
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Robert Praetorius" <RPraetorius AT AspenRes DOT Com>
Organization: Ministry of Hobo Regalia, Gauntlet Division
To: cygwin AT cygwin DOT com
Date: Wed, 13 Feb 2002 09:36:43 -0500
MIME-Version: 1.0
Subject: RE: /usr/bin/env - Incorrect parsing of #! line?
Reply-to: RPraetorius AT AspenRes DOT Com
CC: "Gerald S. Williams" <gsw AT agere DOT com>
Message-ID: <3C6A33AB.11801.195DC13A@localhost>
In-reply-to: <GBEGLOMMCLDACBPKDIHFCEPKCGAA.gsw@agere.com>
References: <00b901c1b43b$ea06d130$6600a8c0 AT cherry>
X-mailer: Pegasus Mail for Windows (v4.01)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

> I think DG's and PJA's original assessment was correct and
> BASH should be modified. Support for cross-platform scripts
> is important, and the #!/bin/env trick is used frequently.

     bashref.html says:

        "Suggestions and `philosophical' bug reports may be
        mailed to bug-bash AT gnu DOT org or posted to the Usenet
        newsgroup gnu.bash.bug."

As was pointed out, cygwin will use whatever behavior bash implements.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/