I sure wish I'd managed to keep all the flotsam generated by cpan much
earlier today - unfortunately, it's vanished if swirling puff of electrons.
But this is probably old had to real Perl'ers. Still, I thought someone
might want to know about it...
Much later in the day, I discovered that a head
On Thu, Jul 10, 2003 at 11:40:15PM -0700, Walt Pawley wrote:
Perhaps even better would be not to use the word head as the name of a
command in the first place - especially one that overwrites a command
provided by MacOSX in the first place? I don't really know what the LWP
head command did
The head vs. HEAD problem is a well-known problem with using CPAN on Mac
OS X. There was some discussion on this list last month because some
people believed that the problem had been fixed. Sadly, your experience
proves otherwise.
Indeed, one can blame this problem on the unique
At 06:38 -0400 7/11/03, David R. Morrison wrote:
The head vs. HEAD problem is a well-known problem with using CPAN on Mac
OS X. There was some discussion on this list last month because some
people believed that the problem had been fixed. Sadly, your experience
proves otherwise.
I actually also
On Friday, July 11, 2003, at 02:40 AM, Walt Pawley wrote:
I vaguely recall having been asked a
question about whether something named head should have something or
other done with it but the details escape me (as most things seem to be
prone to do these days).
As a general rule, module Makefiles
At 09:20 -0400 7/11/03, Sherm Pendley wrote:
The lwp-request program will use the name it is invoked with to
determine what HTTP method to use. I can set up alias for the most
common HTTP methods. These alias are also installed in
/usr/local/bin.
Do you want to install the GET alias? [y] n
Do
On Friday, July 11, 2003, at 01:40 AM, Walt Pawley wrote:
Much later in the day, I discovered that a head command typed into
Terminal no longer gave me the first few lines of a file. Instead it
seemed
to provide numerous error messages and webbish looking stuff after some
considerable delay.
Hi
Hi,
There's still a flaw with the conflict-detection in LWP's Makefile.PL
that prevents /usr/bin/head from being overwritten by HEAD on Mac OS X.
The problem is that MakeMaker uses $Config{installscript} as the
installation location for EXE_FILES items, not $Config{sitebin} as was
assumed in
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Chip Howland) wrote:
At 1:10 AM +0900 7/11/03, Robin wrote:
But if I have to have a double clickable perl script I prefer using
the '.command' technique because I really believe Apple should just
go ahead and use Perl as the scripting
At 10:29 AM -0700 7/11/03, Chris Nandor wrote:
and here's a Perl tutorial:
[snip way too many lines of tutorial, apparently intended to make perl look
a lot harder than it is]
Here is what, perhaps, you meant:
Open BBEdit
Type
print Hello, world.
Run the script
Yes, that's one way to run a
On Friday, July 11, 2003 14:14 -0500 Chip Howland [EMAIL PROTECTED]
wrote:
I think you might be a special case. Not everyone has written Mac::Glue
or maintained MacPerl. If you are claiming that you can do everything
with Perl and Mac::Glue that you can with Applescript, then I won't
dispute
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Chip Howland) wrote:
At 10:29 AM -0700 7/11/03, Chris Nandor wrote:
and here's a Perl tutorial:
[snip way too many lines of tutorial, apparently intended to make perl look
a lot harder than it is]
Here is what, perhaps, you meant:
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (David Cantrell) wrote:
It matters not that he wrote Mac::Glue. He's published it, so I can use it
too. And I have just as much difficulty with using Mac::Glue as I do with
using Applescript. That difficulty is solely because Applescript
At 10:29 AM -0700 7/11/03, Chris Nandor wrote:
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Chip Howland) wrote:
At 1:10 AM +0900 7/11/03, Robin wrote:
But if I have to have a double clickable perl script I prefer using
the '.command' technique because I really believe Apple should just
At 9:55 AM -0400 11/7/03, Sherm Pendley wrote:
On Friday, July 11, 2003, at 09:26 AM, Elizabeth Mattijsen wrote:
Surely the install script can be made smart enough to make [n] the
default on Mac OS X?
Even if the test is done in very general terms - i.e. if it were
written to look for a
On Friday, July 11, 2003, at 08:48 PM, Peter N Lewis wrote:
so perhaps the test should be
The test as written is fine - if there is a 'HEAD' file, it looks in it
for the string 'lwp-request'. If it finds such a string, it defaults to
'y', as the file is probably a symlink that was installed by
16 matches
Mail list logo
