Some kind of unicode regression

[djdv]

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 4420950337ccdd7bb5bb66d84538d2ea4195c101
Powershell 7-rc3

Steps to reproduce

After 4420950, characters like 🏠 appear to get corrupted.

I'm using this symbol in my Powershell prompt and it has stopped working as expected.
7d6738c:

4420950:

$script:pathDelim = [IO.Path]::DirectorySeparatorChar.ToString()
(@($pwd.Path.Split($pathDelim) | select-object -skip 1) -join  $pathDelim).replace([environment]::UserName, "🏠

[DHowett-MSFT]

Yeah, this is fairly serious. 😄

Thanks!

I bet it's part of the conpty change in 4420950.

function things {
write-host "🏠"
write-host "a🏠"
write-host "🏠b"
write-host "c🏠d"
}

/cc @miniksa

[miniksa]

function things {
write-host "`u{1f3e0}"
write-host "a`u{1f3e0}"
write-host "`u{1f3e0}b"
write-host "c`u{1f3e0}d"
}

[miniksa]

SURROGATE PAIRS!

shakes fist into air

[djdv]

@DHowett-MSFT , @miniksa
Thanks for the render fix!
However, this is still presenting an issue.
If I set glyphs like that to be part of the prompt, I'm not able to actually use the shell (input seems to do nothing).
Rendering them seems fine however.
Example: https://youtu.be/5Dswxk6XdTs

EDIT: spoke too soon
This doesn't happen under #4747 (ddadcc5) but does in current master (4608fd0 ).

[miniksa]

@DHowett-MSFT Dustin Howett FTE , @miniksa Michael Niksa FTE
Thanks for the render fix!
However, this is still presenting an issue.
If I set glyphs like that to be part of the prompt, I'm not able to actually use the shell (input seems to do nothing).
Rendering them seems fine however.
Example: youtu.be/5Dswxk6XdTs

EDIT: spoke too soon
This doesn't happen under #4747 (ddadcc5) but does in current master (4608fd0 ).

OK, great. I'm trying to bring #4747 in ASAP, so hopefully this will be fully resolved for you then.