On Thu, Jun 22, 2023 at 7:06 AM Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > > Hi Gary, > > On Thu, 22 Jun 2023 at 12:05, Gary Gregory <garydgreg...@gmail.com> wrote: > > > > But is it enabled in cmd.exe? Windows Terminal is a separate download, at > > least on Windows 10. > > You are right: removing the > 'HKEY_CURRENT_USER\Console\VirtualTerminalLevel' on my system disabled > ANSI escapes, so the default value for cmd.exe must be no ANSI > escapes. > > However I think we could drop `jansi` anyway and document the need to > set `HKEY_CURRENT_USER\Console\VirtualTerminalLevel` to 1, because: > 1. Nobody noticed JANSI support has been broken since 2021,
Well, I noticed it ;-) but I've not taken the time to do anything about it. For my apps, this means that I've forced an old version of JAnsi instead of updating to the current version. Gary > 2. I would prefer to change a registry value instead of adding a 200 > KiB library to my application. That's absurd IMO. When I deliver an app with console logging, it just has to work. I can't tell users: Run our setup.exe, then open regedit, back up the registry, edit your registry with this key and value, and make sure you don't trip and shoot yourself in the foot editing your registry. Gary > > Piotr
