The currently supported $ErrorView values are:
NormalView - the default, "noisy", multi-line display:
> Get-Item /NoSuch
Get-Item : Cannot find path '/NoSuch' because it does not exist.
At line:1 char:1
+ Get-Item /NoSuch
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (/NoSuch:String) [Get-Item], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetItemCommand
CategoryView - a terse, single-line display that doesn't always contain enough information:
> $ErrorView = 'CategoryView'; 1 / 0
NotSpecified: (:) [], RuntimeException
It would be nice to have another option - e.g., ConciseView - that limits output to a single line that contains the immediately relevant information (digging deeper - if needed - is always possible via $Error[0]):
> $ErrorView = 'ConciseView'; Get-Item /NoSuch # wishful thinking
Get-Item : Cannot find path '/NoSuch' because it does not exist.
Arguably, this kind of display is the most useful to end users when viewed in the console, so perhaps it should be the default.
As an aside: requiring the $ErrorView values to end in *View seems redundant; related: #3644 and #3645.
Environment data
PowerShell Core v6.0.0-alpha (v6.0.0-alpha.18) on Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64
The currently supported
$ErrorViewvalues are:NormalView- the default, "noisy", multi-line display:CategoryView- a terse, single-line display that doesn't always contain enough information:It would be nice to have another option - e.g.,
ConciseView- that limits output to a single line that contains the immediately relevant information (digging deeper - if needed - is always possible via$Error[0]):Arguably, this kind of display is the most useful to end users when viewed in the console, so perhaps it should be the default.
As an aside: requiring the
$ErrorViewvalues to end in*Viewseems redundant; related: #3644 and #3645.Environment data