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 To: "David Gluss" Cc: , "Peter J. Acklam" Subject: Re: /usr/bin/env - Incorrect parsing of #! line? References: <8z9y4kbm.fsf@online.no> <001b01c1b3ff$46981950$6600a8c0@cherry> Organization: Private From: pjacklam@online.no (Peter J. Acklam) Date: Tue, 12 Feb 2002 21:15:06 +0100 In-Reply-To: <001b01c1b3ff$46981950$6600a8c0@cherry> ("David Gluss"'s message of "Tue, 12 Feb 2002 11:55:47 -0800") Message-ID: Lines: 24 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 "David Gluss" wrote: > I don't know if it's constructive to suggest an alternative trick, rather > than trying to fix cygwin, in this forum. However, this might work > for you: >>------------ >>: # -*-Mode: perl;-*- use perl, wherever it is >>eval 'exec perl -wS $0 ${1+"$@"}' >> if 0; >>#!/usr/local/bin/perl -w >>------------ Thanks! But I wonder, does the colon really belong there? If so, what does it do? Will this work under all common shells (sh, ksh, bash, zsh, csh, tcsh)? I hasitate to use a script with no shebang line, because I'm so used to it always being present in a script, but if I don't really need it, then I guess I can do without. 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/