in reply to Re^6: What's wrong with @ARGV - or with me?
in thread What's wrong with @ARGV - or with me?

But this fixed it: HKEY_CLASSES_ROOT\Applications\perl.exe\shell\open\command

Weird!

I currently have 5 versions of AS perl installed on this machine -- and I've had many others installed previously -- and that key doesn't exist in my registry.

What creates it and what uses 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^7: What's wrong with @ARGV - or with me?

Replies are listed 'Best First'.
Re^8: What's wrong with @ARGV - or with me?
by karlgoethebier (Abbot) on Jun 12, 2013 at 14:22 UTC
[reply]
      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.
[reply]
        «...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]

In Section Seekers of Perl Wisdom