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
Date: Wed, 13 Feb 2002 09:47:37 -0500
From: Chet Ramey <chet AT nike DOT ins DOT cwru DOT edu>
To: gsw AT agere DOT com
Subject: RE: /usr/bin/env - Incorrect parsing of #! line?
Cc: cygwin AT cygwin DOT com, dgluss AT marple-tech DOT com, pjacklam AT online DOT no,
   chet AT po DOT cwru DOT edu
Reply-To: chet AT po DOT cwru DOT edu
Message-ID: <020213144737.AA61530.SM@nike.ins.cwru.edu>
Read-Receipt-To: chet AT po DOT CWRU DOT Edu
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-In-Reply-To:  Message from gsw AT agere DOT com of Wed, 13 Feb 2002 09:25:41 -0500 (id <GBEGLOMMCLDACBPKDIHFCEPKCGAA DOT gsw AT agere DOT com>)

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

How is changing bash going to do anything?  The kernel takes
care of executing files with a `#!' magic number.  I presume
that the cygwin dll handles this.

There is an incompatibility between the linux kernel and other
Unices in the way they parse arguments after the interpreter
name, but that's not really bash's business.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet)

Chet Ramey, CWRU    chet AT po DOT CWRU DOT Edu    http://cnswww.cns.cwru.edu/~chet/

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