Dustin L. Howett
Dustin L. Howett
But you aren't inserting a null character. You're inserting a space! Anyway, `WriteConsoleOutputCharacter[AW]` is for legacy consoles that only support UCS-2 (**not surrogate pairs**) anyway, so it is fitting that...
Including the same wide character in both halves is what is required for this to operate as expected on all versions of the Windows Console as well.
This seems like a case where word wrapping (Alt+Z) would help! Is that enough to get you unblocked for now?
Well, to be fair... if it reproduces on Windows Terminal a log from the debug tap might be helpful! Just to see if there's an issue in input generation.
Here's what I'm thinking, @zadjii-msft. We always intended 2-stage handoff to be _actually 2-part_, not just 2-stage. We can provide an updated version of conhost (perhaps even inside terminal!) that...
The original mockups for "default terminal" config actually had two parts: "What console handles these requests?" "What terminal does it send them to?" and that's actually still how it works...
> I can see there is still a cmd.exe there cmd.exe *is the Command Prompt*. You should only see it when you launch a .cmd file or Windows Command Prompt....
You just need another interface entry, ``` {6F23DA90-15C5-4203-9DB0-64E73F1B1B00} ```
Oh! PR #36282 uses the word `use` instead of `using`. For consistency, you should stick with one version of that word! 🙂
/azp run