Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <00a201c1b430$5217b5c0$6600a8c0@cherry> From: "David Gluss" To: "Peter J. Acklam" Cc: Subject: Re: /usr/bin/env - Incorrect parsing of #! line? Date: Tue, 12 Feb 2002 17:31:03 -0800 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 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? DG -- 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/