Tell PowerShell ISE to not send stderr to Write-Error

Question

The PowerShell console and the PowerShell ISE behave differently when executables write to the standard error stream (stderr). The console (powershell.exe) displays it like standard output. For example, when I get a status with Mercurial on a non-repository, it writes to standard error:

> hg st -R C:\Windows
abort: repository C:\Windows not found!

However, in the PowerShell ISE (powershell_ise.exe), that error gets passed to PowerShell's Write-Error cmdlet:

> hg st -R C:\Windows
hg.exe : abort: repository C:\Windows not found!
At line:1 char:3
+ hg <<<<  st -R C:\Windows
    + CategoryInfo          : NotSpecified: (abort: repository C:\Windows not found!:String) [], RemoteExcepti 
   on
    + FullyQualifiedErrorId : NativeCommandError

Is there any way to configure the ISE to behave like the console, and not send the stderr stream to Write-Error?

What I'm currently seeing with my Powershell 4 on Win7 is that: The powershell-console and ISE do behave in the described way, *but* when running a powershell-script `.ps1` from the console, or when invoking `powershell script.ps1`from e.g. a normal cmd windows, then the stderr stream will behave like in ISE, that is, use Write-Error. — Martin Ba, Oct 25 '16 at 08:43

Keith Hill · Answer 1 · 2012-09-23T19:43:29.267

Redirecting the stderr output to stdout "should" work but it doesn't in ISE. In this case, your best bet is to silence the error output like so:

& {
    $ErrorActionPreference = 'SilentlyContinue'
    hg st -R C:\Windows 2>&1
}

By executing setting this variable in a nested scope, you avoid setting it globally. When the scope above is exited, the global version of $ErrorActionPreference is still set to whatever it was before.

It is unfortunate that ISE and the console behave differently but it is my understanding that with the "console", another console app just gets the console handle so it is outputting directly to the console (bypassing PowerShell). ISE isn't console based so it is trying to make native stderr play nicely with the PowerShell error stream. IMO the behavior of console isn't ideal in this case. So is it better to have ISE be consistent with console or better to have ISE handle stderr better (except the bit about not honoring stream redirection)? Obviously the PowerShell went with the latter.

This doesn't work. It still writes an error using `Write-Error`. — Aaron Jensen, Sep 21 '12 at 22:39
@splatteredbits Yup, it still does. I updated my answer to offer another option. — Keith Hill, Sep 23 '12 at 19:44
Thanks for this! After half a day of experimentation, this approach turned out to be the clear winner. It has its shortcomings but overall, it works for what I need it. — Sander, Sep 28 '12 at 10:50

score 3 · Accepted Answer · answered Oct 18 '13 at 11:17

3

hg st -R C:\Windows 2>&1 | %{ if ($_ -is [System.Management.Automation.ErrorRecord]) { $_.Exception.Message } else { $_ } }

This preserves the stderr output and sends it as normal output, rather than dropping it.

answered Oct 18 '13 at 11:17

Zenexer

18,788
9
71
77

Tell PowerShell ISE to not send stderr to Write-Error

2 Answers2

Linked