Some emoji, eg '😃' don't work, whereas others like '⏰' do

[mikemaccana]

Moved from microsoft/terminal#1606

Using app store preview build of Windows Terminal, with win+. to send 😃 and then ⏰:

@DHowett-MSFT mentioned it's likely not a Windows Terminal issue:

Powershell has trouble with high unicode input ... and there's not much we can do to help that.

Name                           Value
----                           -----
PSVersion                      6.2.1
PSEdition                      Core
GitCommitId                    6.2.1
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

[vexx32]

I wonder if this is due to PS itself or PSReadLine...

Can you Remove-Module PSReadline and try it again?

[mikemaccana]

After Remove-Module PSReadline

[vexx32]

Interesting. Input doesn't like it much, but output is OK.

I'd venture to say this is probably an issue both for PS itself in places and the PSReadLine module as well,

@daxian-dbw any thoughts on this?

[iSazonov]

/cc @daxian-dbw @SteveL-MSFT Should we track the issue here or in PSREadline repo?

[SteveL-MSFT]

Seems like there is an issue in both PS and PSRL. We can keep this issue here for now. Removing PSRL and on macOS, simply pasting "😃 results in �"😃�. Quite strange.

[SteveL-MSFT]

@chuanjiao10 that may be true on Windows, but on macOS there is still an issue although perhaps different from the original issue

[daxian-dbw]

In Windows Terminal, garbage characters may appear when deleting the emoji character.

[iSazonov]

@daxian-dbw Is any updates in PSRL with the issue?

[daxian-dbw]

@iSazonov Unfortunately, no news from the PSReadLine side. also, as mentioned in this issue, the same repros without PSReadLine.

[DHowett-MSFT]

PSReadline uses raw input and non-PSReadline uses COOKED_READ in the console host. One of these things can never be fixed 😄

[iSazonov]

I'd prefer to get updated COOKED_READ in Core.

[DHowett-MSFT]

Cooked read is provided by conhost.exe, not Core, and we cannot change it without significantly impacting application compatibility all across Windows. Raw input with a readline-like library is the correct thing to do.

[iSazonov]

Raw input with a readline-like library is the correct thing to do.

I mean that this must be in Core so that we do not re-implement this in every application. Is there a tracking issue?