ANSI Escape Sequence Handling Issue

[andrewraddatz]

Windows Terminal version

1.12.211020001-release1.12

Windows build number

10.0.19041.0

Other Software

julia version 1.6 and above

Steps to reproduce

Launch julia inside of Windows Terminal

Expected Behavior

Launching julia outside of Windows Terminal with Legacy Console Mode enabled:

Windows Terminal should render the ANSI escapes as above.

Actual Behavior

When julia is launched in Windows Terminal, ANSI escapes are printed directly to the screen.

In Windows Terminal, launched from pwsh:

In Windows Terminal, launched from pwsh (julia --color=no):

In Windows Terminal, launched as a new tab:

In Windows Terminal, launched as a new tab (julia --color=no):

Launched directly, Legacy Console Mode disabled:

[zadjii-msft]

(glad you made it from stackoverflow ☺️)

HUH. I wonder if they're setting the VT reg key.

Can you export the contents of HKCU\Console to a .reg file, rename it to .txt, and share it here?

I'm guessing that there's a VirtualTerminalLevel that's set to something other than 0, and they're using that to manually enable VT support, rather than using SetConsoleMode

[andrewraddatz]

Here's the output with a few non-relevant applications removed from the list.

console.txt

[zadjii-msft]

You know what, I'm smarter than that. When julia is working correctly, are you launching it from a shortcut? Something like julia.lnk, either on the desktop, or the Taskbar, or the Start Menu?

There are two places that a console app can have VirtualTerminalLevel set - one is in the registry, the other is in the lnk. Though, I didn't.... (thought clipped in favor of another theory)

Presumably, using the run dialog (win+r) to launch v:\PortableApps\julia\bin\julia.exe would also not work.

terminal/src/host/srvinit.cpp

Lines 194 to 201 in 284257a

	// microsoft/terminal#1965 - Let's just always enable VT processing by
	// default for conpty clients. This prevents peculiar differences in
	// behavior between conhost and terminal applications when the user has
	// VirtualTerminalLevel=1 in their registry.
	// We want everyone to be using VT by default anyways, so this is a
	// strong nudge in that direction. If an application _doesn't_ want VT
	// processing, it's free to disable this setting, even in conpty mode.
	settings.SetVirtTermLevel(1);

We should be enabling virtual terminal processing for Terminal client apps, always. That implies that julia is actually _manually disabling it?!

https://github.com/JuliaLang/julia/blob/f9bb6f8fa8c66ca00f215cbbc4e4bc5addc43156/stdlib/REPL/src/LineEdit.jl#L1375

That's the only SetConsoleMode reference in julia. Maybe there's something else I'm missing.

x-ref: JuliaLang/julia#43273

PR that added the SetConsoleMode call: JuliaLang/julia#36598

[andrewraddatz]

I don't launch it through a link. In Windows Terminal, the settings are done this way:

Otherwise, I use start v:\PortableApps\julia\bin\julia.exe to launch it.

[andrewraddatz]

After the problem magically resolving itself when i moved my ~/.julia directory, I did some more digging. It looks like the issue is tied to a macro that I created to clear the screen which was called in a different macro in my startup script.

replacing the macro with its content removes the ANSI character issue.

[zadjii-msft]

Well, that's good to know. Thanks for following up!