Re^2: Command line arguments not passed in Win7

The first 2 commands give the identical results as your example.

the final one, 'set pathext' shows a lot of file extensions, but NOT .pl! Even though the assoc command appeared to run without error.

My problem is not that the system doesn't execute perl. It finds and executes perl, but doesn't pass the command line parameters to @ARGV.

Comment on Re^2: Command line arguments not passed in Win7

Replies are listed 'Best First'.

Re^3: Command line arguments not passed in Win7
by BrowserUk (Patriarch) on Sep 17, 2013 at 22:09 UTC

The first 2 commands give the identical results as your example.

You sure?

The only thing I am aware of that could be affecting this, is if the ftype were set wrong. For example, if the ftype were set as:

Perl="c:\perl64\bin\perl.exe" "%1"
[download]

That would disable the passing of arguments:

C:\test>type argtest.pl
#! perl -slw
use strict;

print for @ARGV;


C:\test>ftype Perl
Perl="c:\perl64\bin\perl.exe" "%1"

C:\test>argtest 1 2 3 4 5           ### NOTE ### no args printed becau
+se %* is missing above.

C:\test>ftype Perl="c:\perl64\bin\perl.exe" "%1" %*
Perl="c:\perl64\bin\perl.exe" "%1" %*

C:\test>argtest 1 2 3 4 5           ### NOTE ### Now it works.
1
2
3
4
5
[download]

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

[reply]
[d/l]
[select]


good chemistry is complicated, and a little bit messy -LW
	PerlMonks