Re: Basic question

2004-05-23 Thread Randal L. Schwartz
Wren == Wren Argetlahm [EMAIL PROTECTED] writes: Wren And how is this different/better than just using Wren #!perl? Well, #!perl works only when Perl is in your current directory, so unless you're in the habit of running your programs while cd'ed to /usr/bin, it's not gonna do much good. The

Re: Basic question

2004-05-23 Thread Timothy Bailey
On Sat, 22 May 2004 12:50:47 -0600, someone going by the name of Doug McNutt [EMAIL PROTECTED] spake in tongues thusly: You do have the execute bit set don't you? Oh, yeah, I know about the permissions. That's fine. It turned out to be the ./ at the front of the line. . must have been part

Basic question

2004-05-22 Thread Timothy Bailey
I recently got a new(er) computer, and I did a fresh install of Jaguar and Perl, etc. on it. Unfortunately, I'm having a very basic problem, and I'm not finding guidance online for it. Now, I have used MacPerl extensively, and have used Perl on UNIX systems as well, but have not installed it

Re: Basic question

2004-05-22 Thread Kim Helliwell
This might be simply that your search path is not set correctly. Try typing: $ echo $path and see what you get. If . is not in the path, the command it's not finding is the script, not Perl or the Shell. Or, of course, your path might not have the locations of sh or perl. Fix up your path, and I

Re: Basic question

2004-05-22 Thread Chris Devers
On Sat, 22 May 2004, Kim Helliwell wrote: This might be simply that your search path is not set correctly. Correct here may be a matter of opinion -- it's not by accident that . is not part of the path by default, as that's a security hazard. The way around this is to make the path explicit on

Re: Basic question

2004-05-22 Thread Doug McNutt
At 10:10 -0500 5/22/04, Timothy Bailey wrote: Oddly enough, shell scripts (which I am less familiar with) don't seem to pay attention to the shebang line either. I am guessing that the problems are related. You do have the execute bit set don't you? chmod 755 yourScript In any case it's not

Re: Basic question

2004-05-22 Thread Rich Morin
Given that the Perl executable may be located in any of several places, hard-coding a path into the shebang line isn't all that great an idea. The following will always give you the version of perl that comes first on your search path: #!/usr/bin/env perl -r -- email: [EMAIL PROTECTED]; phone:

Re: Basic question

2004-05-22 Thread wren argetlahm
--- Rich Morin [EMAIL PROTECTED] wrote: Given that the Perl executable may be located in any of several places, hard-coding a path into the shebang line isn't all that great an idea. The following will always give you the version of perl that comes first on your search path:

basic question

2004-03-24 Thread kynan
Hi all - a very quick question: I'm a web developer (PHP, javascript etc) with a little Perl and I used to use Applescript about 10 years ago. I want to write a simple script that I can distribute to OS X users along with a folder of images. When clicked (has to be totally simple), the script

Re: basic question

2004-03-24 Thread Bill Stephenson
On Mar 24, 2004, at 4:18 PM, kynan wrote: Hi all - a very quick question: I'm a web developer (PHP, javascript etc) with a little Perl and I used to use Applescript about 10 years ago. I want to write a simple script that I can distribute to OS X users along with a folder of images. When