Ansi codes are not properly handled by cmd.exe

[jsmif]

In cmd.exe on Windows, the output of bumble looks kind of horrible. There's all sorts of stray things like ←[0m making the text pretty hard to read.

←[33mL2CAP_DISCONNECTION_RESPONSE←[0m [ID=3]:
  ←[36mdestination_cid:←[0m 64
  ←[36msource_cid:     ←[0m 64

or

    ←[36mprimary_phy:                  ←[0m LE_1M
    ←[36msecondary_phy:                ←[0m Phy[0]
    ←[36madvertising_sid:              ←[0m 255
    ←[36mtx_power:                     ←[0m 127
    ←[36mrssi:                         ←[0m -72
    ←[36mperiodic_advertising_interval:←[0m 0
    ←[36mdirect_address_type:          ←[0m PUBLIC_DEVICE
    ←[36mdirect_address:               ←[0m 00:00:00:00:00:00/P

This sort of issue was described here and seems to have something to do with colorama initialization requirements.

Is there any workaround / should I be using some other environment other than cmd.exe?

[zxzxwu]

You can use Windows Terminal.

[jsmif]

That seems to just be the same as PowerShell? In which case, I can't activate the venv as I get this error:

.\venv\Scripts\Activate.ps1 : File C:\Users\user\Desktop\bumble\venv\Scripts\Activate.ps1 cannot be loaded because running scripts is
disabled on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ .\venv\Scripts\Activate.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

Is the Bumble powershell script signed so that I can set the policy to AllSigned? Do I have to turn off PowerShell security to run Bumble? (Currently I don't need to disable any security, or even launch as an admin in order to use cmd.exe)

[barbibulle]

Which version of Windows are you using? Starting with Windows 10, ANSI escape codes should be supported by the default command terminal

[jsmif]

Edition	Windows 10 Pro
Version	22H2
Installed on	‎4/‎2/‎2021
OS Build	19045.6216

(Which seems surprisingly out of date given that I'm pretty sure I tell this box to do a windows update every few months when I use it. Or I suppose perhaps they haven't been updating the YYHX numbering since Win 11 shipped... In any case I updated last night (inadvertently) and the problem persists)

[zxzxwu]

https://dev.to/aka_anoop/enabling-virtualenv-in-windows-powershell-ka3

I personally don't encourage people to use CMD anymore...

[jsmif]

Wow...

I guess you've never heard of powershell malware huh? It's only been going on for a decade...

Please don't ever make that recommendation again. The security default is set that way for a reason.

[zxzxwu]

Sounds good.

[barbibulle]

I have just tried on a fresh install of Windows 11 (I don't have a Windows 10 machine to try). The color logs work just fine in a CMD window (Command Prompt shell in a Windows Terminal window).

[jsmif]

So readable! 😍 Unfortunately I only have one throwaway underpowered mini-pc that's eligible to run Windows 11 (everything else is Linux or Mac (but I don't install software on my host OS on Mac if I can avoid it, which I can here (by using Windows. As a reminder, Linux doesn't actually work per Issue #747)), but I've started software updates on the win11 box and can give it a shot, since I shouldn't need a powerful box just for playing with Bumble. So anyway, fair enough, Win 10 is going out of support, so feel free to close this if it's not going to be fixed there.