Thanks for the detailed response!

I, too, always use perl script.pl on all systems, Linux included. In all honesty, I never even use Windows, except to develop berrybrew ironically ;)

This feature was solely developed because one of my users had asked for it, and since I don't use Windows, didn't notice the problem until another user stumbled across it.

In your ftype, you're missing a couple of entries. Compare yours:

tempPerl="C:\EX_D\ulisseDUE\perl5.32.64bit\perl\bin\perl.exe"
[download]

...to mine:

C:\repos\berrybrew>ftype berrybrewPerl
berrybrewPerl=C:\berrybrew\5.10.1_32\perl\bin\perl.exe %1 %*
[download]

The %1 is the script name, and %* are any arguments passed to it.

Output (only hitting ENTER once to execute the command):

C:\repos\berrybrew>t\data\assoc.pl
Hello, world!
C:\berrybrew\5.10.1_32\perl\bin\perl.exe

C:\repos\berrybrew>
[download]

Script:

use warnings;
use strict;

print "Hello, world!\n";
print "$^X\n";
[download]

I can't repro the original problem that was reported (having to hit enter twice) on three new systems I've spun up and tried it on, so I'm as content as I can be until it gets wider testing after release and I get actual feedback on it.

I'll make a note on this thread when I finish the full release with point form notes on how to test it while actually using berrybrew if you or anyone else is interested in testing it in the larger scheme of things.

As far as registry, I set only HKCR\.pl for the association, and HKCR\berrybrewPerl\shell\open\command for the ftype definition from within the berrybrew library.