Win32 curl.exe should enable VT processing

[PhMajerus]

I believe curl.exe is owned by PowerShell team, but since the issue is conhost-related, and you guys are probably the ones who can best understand what the issue is, and know how to fix it quickly, I'll report this here hoping you can get it done.

curl for Windows 10 (%SystemRoot%\System32\curl.exe) works pretty well, but inherits the conhost mode of the parent process.
Because of this, VT markup served over http for console users renders the escape characters instead of processing them as control sequences.

For behavior parity with the original version, can someone please add a SetConsoleMode ENABLE_VIRTUAL_TERMINAL_PROCESSING to curl.exe ?

[zadjii-msft]

Actually, I think that technically the WSL team owns the curl.exe we ship inbox now...

Regardless, we've had discussion before about going and updating curl with changes to enable VT processing for windows. @bitcrazed who should be on top of following up with them. IIRC someone needs to make a PR to the master curl repo (I don't believe we're maintaining a separate fork), and we'll take a binary drop from that, but I don't really remember the details.

Also see #51

[bitcrazed]

I actually have a change-set to enable VT mode in Curl and will be working with the team to incorporate it if they're willing to accept my PR.

Hopefully, this will remedy this problem.

[bitcrazed]

Update: The core of the changes is working nicely. A few more changes required to make curl handle codepages better on Windows, but we're making progress:

[DHowett-MSFT]

This was curl/curl#3011, which is now merged. Thanks!

[bitcrazed]

Reopening since we haven't yet pulled & rebuilt curl from recent sources.

Also started thread with team to consider taking this on.

[DHowett-MSFT]

Looks like it does this now.