From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22499 invoked by alias); 13 Feb 2002 03:10: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 22292 invoked from network); 13 Feb 2002 03:09:57 -0000 Received: from unknown (HELO granger.mail.mindspring.net) (207.69.200.148) by sources.redhat.com with SMTP; 13 Feb 2002 03:09:57 -0000 Received: from user-112vubf.biz.mindspring.com ([66.47.249.111] helo=cherry) by granger.mail.mindspring.net with smtp (Exim 3.33 #1) id 16apnw-000096-00 for cygwin@cygwin.com; Tue, 12 Feb 2002 22:09:56 -0500 Message-ID: <00b901c1b43b$ea06d130$6600a8c0@cherry> From: "David Gluss" To: References: <00a201c1b430$5217b5c0$6600a8c0@cherry> <20020213015400.GI28002@redhat.com> Subject: Re: /usr/bin/env - Incorrect parsing of #! line? Date: Tue, 12 Feb 2002 19:10:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-SW-Source: 2002-02/txt/msg00636.txt.bz2 Hmm. You're right about that. In that case I will do nothing. Of course I've always objected to that behavior...but so it is. DG ----- Original Message ----- From: "Christopher Faylor" To: Sent: Tuesday, February 12, 2002 5:54 PM Subject: Re: /usr/bin/env - Incorrect parsing of #! line? > On Tue, Feb 12, 2002 at 05:31:03PM -0800, David Gluss wrote: > >The problem looks to be that bash "helps out" the system by executing > >scripts beginning with #!. In the source for bash, look in > >execute_cmd.c, line 3369. Only one argument is allowed. So e.g. > >#!/usr/bin/env perl -w becomes "/usr/bin/env" "perl -w" If I make a > >patch for this, should it go to the cygwin list? Should it just go to > >gnu.bash.bug and leave it at that? > > I think you're misinterpreting the problem. If it works the same way > on linux and on cygwin, then there is nothing to fix. > > cgf > > -- > 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/ > -- 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/