You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order for escape sequences to work in the Windows Console (conhost.exe, the vintage terminal on Windows), applications need to explicitly call SetConsoleMode with ENABLE_VIRTUAL_TERMINAL_PROCESSING. So perhaps something in the stack here isn't calling that?
For the record, installing wdq in WSL does correctly display the colors. This is because WSL itself is setting the console into the correct mode for all child processes it launches.
I've asked what is WSL and how do I install wdq into it.
Given that cygwin cat shows the colors, it's puzzling why wdq doesn't show them. @nichtich any advice?
@nichtichwdtaxonomy shows the colors ok. What console output library do you use in the two cases, and can you switch wdq to use the same as wdtaxonomy?
Microsoft Terminal now supports VT escape sequences.
wdq -C help
shows escape chars instead of colorswdq -C help | cat
shows the colors okThe text was updated successfully, but these errors were encountered: