Windows Terminal Preview v1.20.10822.0 #16935
Replies: 4 comments 3 replies
-
Does this PowerShell support ANSI colors again? If so, how to enable them? They're currently broken in my Windows 11 Windows PowerShell Windows Terminal PS C:\Users\C> $PSStyle.OutputRendering = 'ANSI'
The property 'OutputRendering' cannot be found on this object. Verify that the property exists and can be set.
At line:1 char:1
+ $PSStyle.OutputRendering = 'ANSI'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyNotFound |
Beta Was this translation helpful? Give feedback.
-
The naming is extremely confusing. Thanks for looking into it. I found the solution is using "\x1b[" instead of "\x9b", but then it stops working in Git Bash in VS Code while it starts working outside VS Code. See https://gist.github.com/CTimmerman/ddb19887b7f5e36eea122deb5eaf7431 |
Beta Was this translation helpful? Give feedback.
-
thanks microsoft |
Beta Was this translation helpful? Give feedback.
-
Windows Terminal Preview 1.20 needed some servicing too, so I figured... why not?
Bug Fixes and Changes
ReadConsoleOutputCharacterW
no longer fails on lines containing narrow surrogate pairs (Fix a ReadConsoleOutputCharacter regression #16898)Binary files inside the unpackaged distribution archive bear the version number
1.20.240322002-preview
.Asset Hashes
2DE1BF8E66469C3C2F26F6398ED56EDBA33E6635AB227C9EF26D0ED8E39A90AA
7FAF725A1ADDB05B2B23692EF9970A2336589E6B68B6789B6E77A53A1688BA9F
0CC49F67C51228F9677EC96D01F1E8C39720E0EA3A686E06FC8592A3F927C46D
60EE40125419F0813B3C055555B388E3C9CE953EDF800B43EC85F331D2FA91B2
This discussion was created from the release Windows Terminal Preview v1.20.10822.0.
Beta Was this translation helpful? Give feedback.
All reactions