Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 12 Feb 2002 20:54:00 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: /usr/bin/env - Incorrect parsing of #! line? Message-ID: <20020213015400.GI28002@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <00a201c1b430$5217b5c0$6600a8c0 AT cherry> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00a201c1b430$5217b5c0$6600a8c0@cherry> User-Agent: Mutt/1.3.23.1i 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/