Re^9: What's wrong with @ARGV

Please see also How do I make Perl scripts recognize parameters in the Win32 cmd console?

Hm. Not sure about the validity of the comments by lucretius. Specifically "To sum up. ftype is old and cmd.exe doesn't care whatever it says.".

That does not fit with my understanding or experience. I can easily flip the active perl installation on my entire machine between the various versions I have installed by changing the ftype setting.

And, as I mentioned, I don't have that registry key set and I don't know what is setting it?

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.

Comment on Re^9: What's wrong with @ARGV - or with me?

Replies are listed 'Best First'.
Re^10: What's wrong with @ARGV - or with me? by karlgoethebier (Abbot) on Jun 12, 2013 at 20:40 UTC
Ť...I don't know what is setting it?ť I observed this issue on a colleague's box who is new to Perl. But he is a experienced Windows user. He has a fresh Windows7 installation and added just some common tools (favorite editor a.s.o) - and a ActiveState Perl installation, just 2-3 days old. So, what else as the ActiveState Perl installation should have caused that entry in the registry? The only idea i have to figure out this is: repeat the Perl setup and use something like RegMon to watch what's going on. And IMHO that means to start from scratch, right? I wonder if it's worth the effort. Thanks and best regards, Karl ŤThe Crux of the Biscuit is the Apostropheť	[reply]
Re^11: What's wrong with @ARGV - or with me? by BrowserUk (Patriarch) on Jun 12, 2013 at 21:05 UTC
The only idea i have to figure out this is: repeat the Perl setup and use something like RegMon to watch what's going on. And IMHO that means to start from scratch, right? I wonder if it's worth the effort. You might get away with just deleting the registry key and then re-installing the AS perl over the top of the existing installation. Or you might try running REGMON whilst you do an un-install of the existing installation -- if it created it, it should remove it when un-installed; but there is no guarantee that the installer/de-installer is so diligent. And it is also possible that the reg key came into being because the user used did something in the Explorer that caused it to form the association. As for whether it is worth your time, only you can decide, but if you do find out, please be sure to report it back here :) 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]