From: Nancy McGough <nm@NoAdsPlease.ii.com>
To: Cygwin Mailing List <cygwin@sourceware.cygnus.com>
Subject: Re: precompiled perl?
Date: Sun, 18 Apr 1999 18:35:00 -0000 [thread overview]
Message-ID: <Pine.WNT.4.10.9904182117550.-495273@aleph> (raw)
In-Reply-To: <001b01be8a00$b8676710$0568d1d0@hunda>
Thank you everyone for the pointer. When I looked at that page before
I posted, it looked to me like all the files out there needed to be
compiled. For people who are new to this world (like me), you might
want to change the README to say "precompiled binary" rather than just
"binary."
I've now downloaded, bunzipped, and untarred it and successfully run a
perl script! Here are a couple questions: The first line of my script
is:
#!perl
and it works fine because perl is on my path. But, if perl weren't on
my path, what is the best thing to put as the first line of the
script. On my system perl is in C:\Cygnus\cygwin-b20\usr\local\bin but
when I'm in the Cygwin bash window I'm not sure what's considered the
root directory.
Another Q: Is it possible to send a file to a Cygwin perl script from
within Windows Explorer. E.g., by right clicking and choosing Send To
and having the script be one of the Send To choices. Any pointers to
launching Cygwin stuff from within Windows would be great.
Thanks again,
Nancy
--
©Nancy McGough http://www.ii.com Infinite Ink
--= Sent via PINE: Power Internet News & Email for Win/Unix =--
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Nancy McGough <nm@NoAdsPlease.ii.com>
To: Cygwin Mailing List <cygwin@sourceware.cygnus.com>
Subject: Re: precompiled perl?
Date: Fri, 30 Apr 1999 18:32:00 -0000 [thread overview]
Message-ID: <Pine.WNT.4.10.9904182117550.-495273@aleph> (raw)
Message-ID: <19990430183200.9QB_W_zEqy-GKNn2K_SittlwDx27adSV0_zVN9SxexE@z> (raw)
In-Reply-To: <001b01be8a00$b8676710$0568d1d0@hunda>
Thank you everyone for the pointer. When I looked at that page before
I posted, it looked to me like all the files out there needed to be
compiled. For people who are new to this world (like me), you might
want to change the README to say "precompiled binary" rather than just
"binary."
I've now downloaded, bunzipped, and untarred it and successfully run a
perl script! Here are a couple questions: The first line of my script
is:
#!perl
and it works fine because perl is on my path. But, if perl weren't on
my path, what is the best thing to put as the first line of the
script. On my system perl is in C:\Cygnus\cygwin-b20\usr\local\bin but
when I'm in the Cygwin bash window I'm not sure what's considered the
root directory.
Another Q: Is it possible to send a file to a Cygwin perl script from
within Windows Explorer. E.g., by right clicking and choosing Send To
and having the script be one of the Send To choices. Any pointers to
launching Cygwin stuff from within Windows would be great.
Thanks again,
Nancy
--
©Nancy McGough http://www.ii.com Infinite Ink
--= Sent via PINE: Power Internet News & Email for Win/Unix =--
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-04-18 18:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-18 9:14 Nancy McGough
1999-04-18 12:00 ` Charles Wilson
1999-04-30 18:32 ` Charles Wilson
1999-04-18 18:05 ` Suhaib M. Siddiqi
1999-04-18 18:35 ` Nancy McGough [this message]
1999-04-19 8:31 ` John Mullee
1999-04-20 12:11 ` Nancy this-address-is-valid McGough
1999-04-30 18:32 ` Nancy this-address-is-valid McGough
1999-04-30 18:32 ` John Mullee
1999-04-30 18:32 ` Nancy McGough
1999-04-30 18:32 ` Suhaib M. Siddiqi
1999-04-30 18:32 ` Nancy McGough
1999-04-19 6:32 Earnie Boyd
1999-04-30 18:32 ` Earnie Boyd
1999-04-20 15:41 John Huddleston
1999-04-30 18:32 ` John Huddleston
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=Pine.WNT.4.10.9904182117550.-495273@aleph \
--to=nm@noadsplease.ii.com \
--cc=cygwin@sourceware.cygnus.com \
/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).