Consider moving the `$ErrorView` configuration to `$PSStyle`
See original GitHub issueSummary of the new feature / enhancement
The $ErrorView variable was introduced earlier than $PSStyle. But with $PSStyle containing configuration like $PSStyle.Formatting and $PSStyle.Progress, it feels to me the error view configuration should be moved to $PSStyle as well, for consistency and easier discoverability.
Proposed technical implementation details (optional)
Discard the $ErrorView variable (breaking change), add the public property ErrorView to System.Management.Automation.PSStyle.
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Using PowerShell with $PSStyle
In this post, I show you how you can use ANSI rendering to control text decorations, such as color and font styling, in...
Read more >about Preference Variables - PowerShell
$ErrorView. Determines the display format of error messages in PowerShell. The $ErrorView variable takes one of the ErrorView enumeration values ...
Read more >7.2.md - PowerShell/PowerShell
General Cmdlet Updates and Fixes. Use $PSStyle.Formatting.FormatAccent for Format-List and $PSStyle.Formatting.TableHeader for Format ...
Read more >"Fossies" - the Fresh Open Source Software Archive
As a special service "Fossies" has tried to format the requested source page into HTML format using (guessed) C# source code syntax highlighting...
Read more >about ANSI terminals - PowerShell
Describes the features of PowerShell that use ANSI escape sequences and the terminal hosts that support them.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

We could simplify codes if we moved $host.UI.SupportsVirtualTerminal detection in PSStyle too.
I would like to work on this, but I have another PR https://github.com/PowerShell/PowerShell/pull/18003 that is modifying
$PSStylethat has been reviewed but not merged for almost a year, @daxian-dbw can you please resolve it first so I don’t merge-conflict myself?