Re^2: Handling MSWin Script Output

I got the same as you for 'assoc' and 'ftype' in cmd.exe:

C:\Users\ken\tmp>assoc | find /i "perl"
.pl=Perl_program_file

C:\Users\ken\tmp>ftype | find /i "Perl_program_file"

C:\Users\ken\tmp>
[download]

In the registry, I have exactly the same as you (except I have C:\Users\ken\local\opt\strawberry_perl\5_030_000\install instead of your C:\Strawberry).

In your PowerShell output, you show everything output to the PowerShell, instead of the commands starting with perl being output in a separate window. Did you do something else to achieve that?

In cmd.exe, I get much the same as you:

C:\Users\ken\tmp>perl .\test_platform.pl
Platform: MSWin32
Executable: C:\Users\ken\local\opt\strawberry_perl\5_030_000\install\p
+erl\bin\perl.exe
Enter to close window:

C:\Users\ken\tmp>.\test_platform.pl
Platform: MSWin32
Executable: C:\Users\ken\local\opt\strawberry_perl\5_030_000\install\p
+erl\bin\perl.exe
Enter to close window:

C:\Users\ken\tmp>perl test_platform.pl
Platform: MSWin32
Executable: C:\Users\ken\local\opt\strawberry_perl\5_030_000\install\p
+erl\bin\perl.exe
Enter to close window:

C:\Users\ken\tmp>test_platform.pl
Platform: MSWin32
Executable: C:\Users\ken\local\opt\strawberry_perl\5_030_000\install\p
+erl\bin\perl.exe
Enter to close window:

C:\Users\ken\tmp>
[download]

So, the answer to Question 1 seems to be to remove the

if ($^O eq 'MSWin32') {
    print 'Enter to close window: ';
    <>;
}
[download]

and run all scripts from "cmd.exe".

— Ken

Comment on Re^2: Handling MSWin Script Output Select or Download Code

Replies are listed 'Best First'.
Re^3: Handling MSWin Script Output by VinsWorldcom (Prior) on Sep 11, 2019 at 10:32 UTC
I didn't do anything different - all output showed in the PowerShell window I ran the command from - no new window was launched. And just a note, I use PowerShell now exclusively - I never use CMD.exe anymore. PowerShell, I've learned, is sooooo much more capable and I've grown to love it over the past year (yes, I was a late adopter - much like how I'm now picking up Python much to my chagrin since everyone at $work uses it).	[reply]
Re^4: Handling MSWin Script Output by kcott (Bishop) on Sep 16, 2019 at 04:20 UTC
"I didn't do anything different - all output showed in the PowerShell window I ran the command from - no new window was launched." Orangutan mentioned PowerShell configuration: it may be that we're using different options. I haven't changed anything so, presumably, I have the default configuration. Given I'm only likely to be using PowerShell infrequently, I won't spend any time investigating that further right now; that may change if my usage does. — Ken	[reply]


Keep It Simple, Stupid
	PerlMonks