Daniel Kasak wrote:
> Timothy Johnson wrote:
>> It sounds like there is a problem with your file association.
>>
>> Open HKEY_CLASSES_ROOT and go to Perl-->Shell-->Open-->Command.
>>
>> The (Default) entry should probably read:
>>
>> "C:\Perl\bin\perl.exe" "%1" %*
>>
> I'll check it out tomorro
Timothy Johnson wrote:
It sounds like there is a problem with your file association.
Open HKEY_CLASSES_ROOT and go to Perl-->Shell-->Open-->Command.
The (Default) entry should probably read:
"C:\Perl\bin\perl.exe" "%1" %*
I'll check it out tomorrow when I can get back to the PC.
Thanks :)
L PROTECTED]
Sent: Wednesday, February 01, 2006 8:20 PM
To: Timothy Johnson; Perl Beginners
Subject: Re: Script's command-line options under Windows
Timothy Johnson wrote:
> One more question. Does it work if you do it like this?
>
> perl script_name.pl argument
>
Ye
Timothy Johnson wrote:
One more question. Does it work if you do it like this?
perl script_name.pl argument
Yes, actually!
Strange ... very strange.
Thanks :)
--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-76
>
>
>-Original Message-
>From: Daniel Kasak [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, February 01, 2006 6:09 PM
>To: Timothy Johnson; Perl Beginners
>Subject: Re: Script's command-line options under Windows
>
>Timothy Johnson wrote:
>
>>Just to
Timothy Johnson wrote:
Just to clarify, you're able to invoke the script by typing
script_name.pl, right?
Yep.
Because one possible reason would be that your file association somehow
didn't take when you installed activeperl.
Also, does it work if you do:
my $userid = $ARGV[0];
al Message-
From: Daniel Kasak [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 01, 2006 5:40 PM
To: Perl Beginners
Subject: Script's command-line options under Windows
Hi all.
I've got an app than runs on Linux and Windows. I invoke it:
script_name.pl USERID
where USERID is a number
on a new installation ( latest ActiveState
Perl, Windows 2000 sp4 ), this isn't working. What's even more
frustrating is that if I fire the script up under Komodo, the
command-line options *are* accepted ( ie I get a $userid ).
What's up?
Dan
--
To unsubscribe, e-mail: [
call:
Can't open -p: No such file or directory
Can't open -t: No such file or directory
which is just saying that it cannot open the command line options that
I'm trying to pass to outline2html.pl. So what is the right way to get
those options through?
Is there a way t
-Original Message-
From: Wiggins d'Anconia [mailto:[EMAIL PROTECTED]
Sent: Friday, April 16, 2004 4:59 PM
To: ewalker
Cc: [EMAIL PROTECTED]
Subject: Re: command line options
[EMAIL PROTECTED] wrote:
> Hey guys anyone have any examples of how to check options with the Get::Lon
[EMAIL PROTECTED] wrote:
Hey guys anyone have any examples of how to check options with the Get::Long module.
Here is what I used to get the options. I need examples of how to check to see if they
entered the correct things or not.
&GetOptions('h|usage|help|info', 'p=s', 's=s', 't=s');
I posted a
Hey guys anyone have any examples of how to check options with the Get::Long module.
Here is what I used to get the options. I need examples of how to check to see if they
entered the correct things or not.
&GetOptions('h|usage|help|info', 'p=s', 's=s', 't=s');
Eric Walker
--
To unsubscribe
Hi,
Jeff Westman [mailto:[EMAIL PROTECTED] asked:
> Why does the order of these options matter?
[...]
> $ nslookup someServer | perl -en 'print qq($_);'
>
> $ nslookup someServer | perl -ne 'print qq($_);'
-e must be followed by the code:
$ perl --help
Usage: perl [switches] [--] [programfile]
Hi,
Why does the order of these options matter? In the first case, no output is
produced, but it works correctly in the second case. I would have thought
perl would have been smart enough to parse the command line options in any
order.
$ nslookup someServer | perl -en 'pri
14 matches
Mail list logo
