#Windows CLI Returned Character Formatting

1 messages · Page 1 of 1 (latest)

autumn sand
#

Is there something I need to do to get the status marker characters formatting correctly in Windows. They currently show as the colour coding and a ? in a box at the moment ←[32m[?]←[0m (see attached screenshot). I'm assuming they should be colour coded and a check mark.
I've tried in Powershell, Command Line and even WSL Ubuntu.
Running dagger 12.2

haughty robin
#

Which version of windows are you in and which terminal are you using? I think we’ve seen this on older versions but would be great to confirm if you’re seeing on modern as well.

https://github.com/dagger/dagger/issues/7559

GitHub

What is the issue? The output in the terminal on Windows is very difficult to read because it seems that is is not able to handle the ANSI escape sequences properly. This behavior is the same on po...

autumn sand
#

Hi, it's Windows 10 (10.0.19045.4651). Seen in Powershell 7.4.3, Windows Command Prompt, and the standard Windows Powershell

autumn sand
#

The link to the Github issue was very helpful.
I've installed Windows Terminal and running Powershell 7.4.3 in there I can see the returned output is now readable
From what I see in the Github issue I can see that this isn't planned to be fixed for Windows 10.
So as most of our systems are still running Windows 10, we will have to instruct users to use Windows Terminal for dagger commands.

autumn sand
#

I've also noticed the Terminal in VSCode renders the characters correctly as well, so that is an alternative solution I can suggest

haughty robin
#

@autumn sand thanks! I ran into the same issue on Windows 10!

I think our recommendation is to use Windows Terminal, I think this might be something nice to add to our FAQ because I imagine many companies may still be on Windows 10.