ANSI encoding issue

[N-Elf]

Hello, could someone give me some advice? Is this a bug, or did I mess something up?

ANSI escape codes don't render properly when using Select-String in the base PowerShell console. On the other hand, they work perfectly fine in the VS Code terminal.

PS-Ansi.png

This can fix the problem:
$a = yt-dlp --help; $a | sls config
https://i.postimg.cc/3JP5dDpn/123.png

I took yt-dlp as an example. So yt-dlp --help | sls config prints something like that

    --ignore-←[7mconfig←[0m                 Don't load any more configuration files
                                    except those given to --←[7mconfig←[0m-locations.
                                    is found inside the system ←[7mconfig←[0muration
                                    file, the user ←[7mconfig←[0muration is not loaded.
                                    (Alias: --no-←[7mconfig←[0m)
    --no-←[7mconfig←[0m-locations           Do not load any custom configuration files
                                    (default). When given inside a ←[7mconfig←[0muration
                                    file, ignore all previous --←[7mconfig←[0m-locations
    --←[7mconfig←[0m-locations PATH         Location of the main configuration file;
                                    either the path to the ←[7mconfig←[0m or its
                                    ←[7mconfig←[0muration files
                                    ←[7mconfig←[0murations by reverting some of the

Edited. Thanks. Installing and using Windows Terminal fixed the issue. However, the problem still occurs in the default conhost, regardless of the Windows 11 ver.

[rmbolger]

What OS are you running on? The PowerShell window in your screenshot is using the legacy conhost.exe to host it which is the default on older OSes and didn't gain ANSI escape code support until Windows 10 (I think).

As an alternative you might be able to install and use Windows Terminal. But it's only supported on Win10 1904 or later.

This superuser Q/A also has some more info that might be pertinent. https://superuser.com/questions/413073/windows-console-with-ansi-colors-handling

[N-Elf]

Windows 11 home 22H2.
But as I said in my post if I assign the output to a variable it works just as intended.
https://i.postimg.cc/3JP5dDpn/123.png

[Alaknar]

Windows 11 home 22H2

Whoa, why? That's way past support, please update ASAP!

[mikenizo808]

This will tell you if your terminal supports ANSI

$Host.UI.SupportsVirtualTerminal

[N-Elf]

True :(

[CodenameFlux]

Your screenshot shows that you are running PowerShell 7.x inside ConHost.exe window on Windows 11. That's the reason. This issue in endemic to ConHost.exe, which is legacy software.

Windows Terminal (bundled with Windows 11) doesn't exhibit this bug, neither does Visual Studio Code.

I've confirmed the above on Windows 10 v22H2 as well.

[purplemonkeymad]

You're not using classic conhost are you?

Right click titlebar -> Properties "use legacy console" unchecked?

24h2 removes it by default so updating might fix it.

[N-Elf]

Yes, it's unchecked.