From: "David Gluss" <dgluss@marple-tech.com>
To: "Charles Wilson" <cwilson@ece.gatech.edu>,
"Peter J. Acklam" <pjacklam@online.no>
Cc: <cygwin@cygwin.com>
Subject: Re: /usr/bin/env - Incorrect parsing of #! line?
Date: Tue, 12 Feb 2002 14:59:00 -0000 [thread overview]
Message-ID: <007101c1b418$dbbb8940$6600a8c0@cherry> (raw)
In-Reply-To: <3C6995F0.50400@ece.gatech.edu>
I think it takes a while to get used to the style of this
list. Thank you for explaining what was meant by
"because... we're mean".
Perhaps a little forgiveness and tolerance all around
would (slap)...oops, never mind...
DG
PS:
% env foobar
env: foobar: No such file or directory
% env foobar -w
env: foobar: No such file or directory
-->put #!/usr/bin/env perl in script "blah"
% blah
% (works fine)
-->put #!/usr/bin/env perl -w in script
% blah
/usr/bin/env: perl -w: No such file or directory
$ echo $SHELL
d:/cygwin/bin/sh.exe
So I believe the original poster (PJA) was correct in his assessment.
It's not "env", because #!/bin/ls gives similar behavior.
----- Original Message -----
From: "Charles Wilson" <cwilson@ece.gatech.edu>
To: "Peter J. Acklam" <pjacklam@online.no>
Cc: <cygwin@cygwin.com>
Sent: Tuesday, February 12, 2002 2:23 PM
Subject: Re: /usr/bin/env - Incorrect parsing of #! line?
> Peter J. Acklam wrote:
>
> > Christopher Faylor <cygwin@cygwin.com> wrote:
> >
> >
> >>Peter J. Acklam wrote:
> >>
> >>
> >>>[...]
> >>>why does Cygwin look for the file "perl -w". No UNIX I
> >>>have worked on would parse the shebang line that way.
> >>>
> >>Because... we're mean.
> >>
> >
> > I'm new here so I don't know who you are, but I hope one can
> > expect more informative responses than this gibberish.
>
>
> When Chris says "because we're mean" it *usually* means that the
> original post was either
> a) rude
> b) accusatory
> c) demanding
> AND that the original poster made an incorrect analysis of their
> problem, then complained about the non-existant problem, and blamed the
> cygwin developers for being such idiots to make that (non-existant)
mistake.
>
> For instance:
> -----------BEGIN EXAMPLE-------------
> "When I start cygwin, it complains that there is no /tmp directory.
> But TEMP=C:\WINNT\TEMP, so of course /tmp exists. Why doesn't cygwin
> understand TEMP?"
>
> Answer: "because we're mean". cygwin understanding the TEMP environment
> variable has nothing to do with whether a directory named '/tmp' exists.
> Cygwin DOES in fact understand TEMP -- but not all applications on
> cygwin use TEMP; some, like bash, directly hardcode '/tmp' and complain
> if it doesn't exist. Furthermore, setup.exe automatically creates /tmp,
> so if it doesn't exist on your machine, then either (a) setup is broken
> -- but the other 2000 people who successfully used it never ran in to
> that problem, or (b) [much more likely] you didn't use setup.exe to
> install cygwin. Bad bad bad bad.
>
> e.g. You didn't follow the directions on how cygwin should be installed,
> then discovered that stuff doesn't work right, then misanalyzed the
> problem, and blamed us for it.
>
> Because we're mean.
> -----------END EXAMPLE-------------
>
> Your question was borderline: "No UNIX I have worked on would parse the
> sheband line that way" This statement as worded implies
> 1) you are much more experienced with unix than any of the monkeys
> working on cygwin
> 2) cygwin sucks -- the monkeys must have been lobotomized before they
> started coding it
> 3) fix it now, you damn lobotomized code monkeys!
>
> Furthermore, it isn't *cygwin* that's parsing the command line. It's
> env.exe. AND, it is not NECESSARILY looking for 'perl -w' -- maybe it's
> just reporting all of its arguments, like a good little app. Perhaps,
> env can't find perl in the current PATH at all -- so it's really just
> saying "can't find "perl" -- and btw, you had a '-w' argument". There's
> no way to know from what you reported.
>
> But you blamed us, and cygwin, anyway.
>
> Because we're mean.
>
> --Chuck
>
>
> --
> 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/
>
--
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-12 22:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2002-02-12 15:22 Chris January
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
2002-02-20 21:33 ` Christopher Faylor
2002-02-21 13:23 ` Peter J. Acklam
2002-02-13 6:50 Chet Ramey
2002-02-13 7:16 ` Gerald S. Williams
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 14:13 Heribert Dahms
2002-02-22 1:27 pjacklam
2002-02-22 4:34 ` Michael Schaap
2002-02-22 5:26 pjacklam
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='007101c1b418$dbbb8940$6600a8c0@cherry' \
--to=dgluss@marple-tech.com \
--cc=cwilson@ece.gatech.edu \
--cc=cygwin@cygwin.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).