Re^3: Handling MSWin Script Output

in reply to Re^2: Handling MSWin Script Output
in thread Handling MSWin Script Output

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).

Comment on Re^3: Handling MSWin Script Output

Replies are listed 'Best First'.
Re^4: Handling MSWin Script Output by kcott (Archbishop) 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]

Replies are listed 'Best First'.

Re^4: Handling MSWin Script Output
by kcott (Archbishop) 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]

In Section Seekers of Perl Wisdom