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: Wed, 20 Feb 2002 22:11:31 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: /usr/bin/env - Incorrect parsing of #! line? Message-ID: <20020221031131.GA1784@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <00a201c1b430$5217b5c0$6600a8c0 AT cherry> <20020213015400 DOT GI28002 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Wed, Feb 20, 2002 at 09:35:16PM +0100, Peter J. Acklam wrote: >Christopher Faylor wrote: >>If it works the same way on linux and on cygwin, then there is >>nothing to fix. > >Ok. But where is this documented? > >I expected "#!/usr/bin/env perl -w" to work because I thought the >line would be interpreted as on the command line (shell) and as is >documented in the manual page for env. Since the behaviour is >different when the line is in the shebang line, it has to be >documented somewhere. AFAIK, it isn't documented anywhere except in the code. I don't know where it would be documented, actually. This obviously isn't an issue with /usr/bin/env. Where did you read about the behavior in "all UNIXes I work on"? We should probably document it in a similar place for cygwin. We'd certainly appreciate a patch to our documentation. Just send it to cygwin AT cygwin DOT com for review. cgf -- Please do not send me personal email with cygwin questions. Use the resources at http://cygwin.com/ . -- 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/