Enable console output target on Windows by default

[Joannis]

Fixes #87

Modern Windows terminals (Windows 10+, Windows Terminal, PowerShell) support ANSI escape codes. This change enables colored output by default on Windows by returning .console as the detected output target.

Changes

• Added #if os(Windows) conditional compilation to return .console directly on Windows
• Keeps existing TTY detection behavior on other platforms

[onevcat]

Hi @Joannis, thanks for the PR! I don’t have any Windows experience, so I’d love your advice here. Would it make sense to add a TTY check on Windows to avoid emitting ANSI escape codes when output is redirected to a file/pipe? I’m thinking something like:

#if os(Windows)
return isatty(fileno(stdout)) != 0 ? .console : .unknown
#else
// existing TERM + isatty logic
#endif

If that’s reasonable, I’d prefer to keep the default behavior consistent across platforms for TTY vs file output. Let me know what you think.

[Joannis]

I can try that, IIRC Windows' terminals don't have all of the APIs you'd expect so I'm not certain isatty is available.

[Joannis]

Hey @onevcat , sorry about the delay. Was not paying attention too much - but I've updated it

[Joannis]

I forgot Windows likes to underscore symbols

[Joannis]

Ping @onevcat