From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22625 invoked by alias); 21 Feb 2002 20:46:03 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Received: (qmail 22421 invoked from network); 21 Feb 2002 20:45:50 -0000 Received: from unknown (HELO mail45.fg.online.no) (148.122.161.45) by sources.redhat.com with SMTP; 21 Feb 2002 20:45:50 -0000 Received: from FENRIS (ti100710a002-0058.dialup.online.no [130.67.2.58]) by mail45.fg.online.no (8.9.3/8.9.3) with ESMTP id VAA09030; Thu, 21 Feb 2002 21:45:46 +0100 (MET) To: cygwin@cygwin.com Subject: Re: /usr/bin/env - Incorrect parsing of #! line? References: <20020213015400.GI28002@redhat.com> <00a201c1b430$5217b5c0$6600a8c0@cherry> <20020213015400.GI28002@redhat.com> <4.3.1.2.20020220155727.02161d00@pop.ma.ultranet.com> Organization: Private From: pjacklam@online.no (Peter J. Acklam) Date: Thu, 21 Feb 2002 13:04:00 -0000 In-Reply-To: <4.3.1.2.20020220155727.02161d00@pop.ma.ultranet.com> ("Larry Hall's message of "Wed, 20 Feb 2002 15:59:37 -0500") Message-ID: <4rka371x.fsf@online.no> User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.1 (i386-msvc-nt5.0.2195) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-02/txt/msg01067.txt.bz2 Message-ID: <20020221130400.2McwiGUBr6ngoTObFy2mYxux_StPTVry8N1e5Cw3ZT4@z> "Larry Hall (RFK Partners, Inc)" wrote: > Well if env documentation states a particular behavior and that > behavior is not what you see, then there is a bug in env or it's > documentation. What made me believe that "#!/usr/bin/env perl -w" should work was the following part of the documentation for env: NAME env - run a program in a modified environment SYNOPSIS env [OPTION]... [-] [NAME=VALUE]... [COMMAND [ARG]...] It clearly says that the command (COMMAND) takes arguments (ARG). Indeed it does on the command line, but not on the shebang line. > You should contact it's maintainer and since it appears to be a > general issue, you should contact the GNU maintainer, not the > Cygwin. I'm not sure what to do, if anything, since this behaviour seems to be so common. For all I know, someone might count on it. Peter -- People say I'm indifferent, but I don't care. -- 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/