Commit log formatting issues on windows

[CaptainStabs]

>dolt log -n 1
←[33mcommit 3il13afu8mba8ktjp0tdevlafn6n9hg7 ←[0m←[33m(←[0m←[36;1mHEAD -> ←[0m←[32;1mmain←[0m←[33m, ←[0m←[31;1morigin/main←[0m←[33m) ←[0m
Author: spacelove <removed>
Date:  Wed Jun 15 09:40:29 -0400 2022

        updated readme

version: 0.40.12

[fulghum]

Thanks for reporting this one @CaptainStabs. Can you tell us a little more about your windows environment? For example, are you using WSL or windows term or cygwin?

[CaptainStabs]

Just using default windows command prompt. Happens on my laptop that uses Clink, and on my desktop that just uses the vanilla command prompt. Also occurs in PowerShell

OS versions: Windows 10 Pro 21H2 Windows 10 Home 21H2

[timsehn]

Here's a simple repro in Powershell:

PS C:\Users\timse\dolthub\dolt\test_enum_history> dolt init
Successfully initialized dolt data repository.
PS C:\Users\timse\dolthub\dolt\test_enum_history> dolt version
dolt version 0.40.32
database storage format: OLD ( __LD_1__ )
PS C:\Users\timse\dolthub\dolt\test_enum_history> dolt sql -q "create table t (pk int primary key, c1 enum('foo', 'bar'), c2 int)";
PS C:\Users\timse\dolthub\dolt\test_enum_history> dolt schema show
t @ working
CREATE TABLE `t` (
  `pk` int NOT NULL,
  `c1` enum('foo','bar'),
  `c2` int,
  PRIMARY KEY (`pk`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_bin;

PS C:\Users\timse\dolthub\dolt\test_enum_history> dolt add t
PS C:\Users\timse\dolthub\dolt\test_enum_history> dolt commit -m "added table)
>> "
←[33mcommit mc7usod8ctc04p7k786c8tkfkokg97ma ←[0m←[33m(←[0m←[36;1mHEAD -> ←[0m←[32;1mmain←[0m←[33m) ←[0m
Author: Tim Sehn <[email protected]>
Date:  Tue Sep 06 21:47:24 -0700 2022

        added table)


PS C:\Users\timse\dolthub\dolt\test_enum_history>