From: hammond@csc.albany.edu (William F. Hammond)
To: pjacklam@online.no (Peter J. Acklam)
Cc: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>, cygwin@cygwin.com
Subject: Re: /usr/bin/env - Incorrect parsing of #! line?
Date: Thu, 21 Feb 2002 19:10:00 -0000 [thread overview]
Message-ID: <i7d6yyb6a2.fsf@pluto.math.albany.edu> (raw)
In-Reply-To: <4rka371x.fsf@online.no>
pjacklam@online.no (Peter J. Acklam) writes:
> "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> wrote:
>
> > Well if env documentation states a particular behavior and that
> > behavior is not what you see, then there is a bug in env or it's
> > documentation.
>
> What made me believe that "#!/usr/bin/env perl -w" should work was
> the following part of the documentation for env:
I don't understand why you want to use /usr/bin/env under Cygwin.
Not everything that makes sense under *ix makes sense for Cygwin.
Presumably one runs Cygwin because one does not want to run Linux
so that one can have simultaneous single platform access to Win*
things and Gnu things familiar in *ix contexts.
That said, doesn't it then make sense to use a straight Win* build for
perl so that perl can be used in Win* mode? Granted that -- and
granted the desire to build environment outside of the Perl script
itself -- one may use either a bat file or an sh script, as
appropriate for the calling context, to create the needed environment.
Either way after building the environment use the syntax:
perl {script-name} {script-arg} ... .
-- Bill
--
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/
next prev parent reply other threads:[~2002-02-22 2:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 17:47 David Gluss
2002-02-12 17:54 ` Christopher Faylor
2002-02-12 19:10 ` David Gluss
2002-02-13 6:26 ` Gerald S. Williams
2002-02-13 6:38 ` Michael Schaap
2002-02-13 6:39 ` Robert Praetorius
2002-02-13 6:52 ` Benoit Rochefort
2002-02-14 11:55 ` Gerald S. Williams
2002-02-20 12:57 ` Peter J. Acklam
2002-02-20 13:37 ` Larry Hall (RFK Partners, Inc)
2002-02-21 12:47 ` Peter J. Acklam
2002-02-21 13:04 ` Peter J. Acklam
2002-02-21 19:10 ` William F. Hammond [this message]
2002-02-20 21:33 ` Christopher Faylor
2002-02-21 13:23 ` Peter J. Acklam
-- strict thread matches above, loose matches on Subject: below --
2002-02-22 5:26 pjacklam
2002-02-22 1:27 pjacklam
2002-02-22 4:34 ` Michael Schaap
2002-02-13 14:13 Heribert Dahms
2002-02-13 6:53 Chet Ramey
2002-02-13 10:37 ` Christopher Faylor
2002-02-13 11:14 ` Lassi A. Tuura
2002-02-13 6:50 Chet Ramey
2002-02-13 7:16 ` Gerald S. Williams
2002-02-12 15:22 Chris January
2002-02-12 10:38 Peter J. Acklam
2002-02-12 10:53 ` Christopher Faylor
2002-02-12 12:16 ` Peter J. Acklam
2002-02-12 14:25 ` Charles Wilson
2002-02-12 14:59 ` David Gluss
2002-02-20 13:03 ` Peter J. Acklam
2002-02-12 11:56 ` David Gluss
2002-02-12 12:17 ` Peter J. Acklam
2002-02-12 13:56 ` David Gluss
2002-02-12 14:57 ` Chris January
2002-02-20 12:57 ` Peter J. Acklam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=i7d6yyb6a2.fsf@pluto.math.albany.edu \
--to=hammond@csc.albany.edu \
--cc=cygwin@cygwin.com \
--cc=lhall@rfk.com \
--cc=pjacklam@online.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).