Handling Emoji Characters in Command Input Prevents History Logging and Causes EncoderFallbackException

[lime2008]

Prerequisites

• Write a descriptive title.

Description of the new feature/enhancement

When entering emoji characters (now i only have tried✨and 🐛, but now only entering🐛 is not normal) in the PowerShell command line via PSReadLine in vsc, attempting to execute the command results in an EncoderFallbackException due to the inability to encode the Unicode character to the current code page. This occurs specifically when PSReadLine in vsc attempts to write the command to the history file. The error disrupts the user’s workflow, as the command is not executed and the history is not updated(but if i have command retried, the error will not occur), and now in my commitment here is a "� 修复stepper响应式的同步".

I often include emojis in commit messages or other commands for better readability or context (e.g., git commit -m "🐛 fix responsive stepper"). Currently, this causes a fatal error that requires restarting the terminal session. The enhancement should allow emojis and other Unicode characters to be handled gracefully, either by encoding them properly or by escaping/sanitizing them when writing to the history file.

Proposed technical implementation details (optional)

No response

[lime2008]

Details is in below:
PS D:\cp-frontend-feat-widgets> git commit -m "� 修复stepper响应式的同步"

哎呀，出现问题。请在报告此 Bug 时添加以下详细信息。
在 GitHub 上报告: https://github.com/PowerShell/PSReadLine/issues/new

环境

PSReadLine: 2.0.0
PowerShell: 5.1.22621.5697
操作系统: Microsoft Windows 10.0.22631
最后的 57 键

 g i t Spacebar a d d Spacebar . Enter
 g i t Spacebar p u s h Backspace Backspace Backspace Backspace c o m m i t Spacebar - m Spacebar " " LeftArrow � Spacebar Backspace Backspace � Spacebar 修 复 s t e p p e r 响 应 式 的 同 步 Enter

例外

System.Text.EncoderFallbackException: 无法将位于索引 15 处的 Unicode 字符 \uD83D 转换为指定的代码页。
   在 System.Text.EncoderExceptionFallbackBuffer.Fallback(Char charUnknown, Int32 index)
   在 System.Text.EncoderFallbackBuffer.InternalFallback(Char ch, Char*& chars)
   在 System.Text.UTF8Encoding.GetBytes(Char* chars, Int32 charCount, Byte* bytes, Int32 byteCount, EncoderNLS baseEncoder)
   在 System.Text.EncoderNLS.GetBytes(Char[] chars, Int32 charIndex, Int32 charCount, Byte[] bytes, Int32 byteIndex, Boolean flush)
   在 System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   在 System.IO.StreamWriter.Dispose(Boolean disposing)
   在 System.IO.TextWriter.Dispose()
   在 Microsoft.PowerShell.PSConsoleReadLine.<>c__DisplayClass83_0.<WriteHistoryRange>b__0()
   在 Microsoft.PowerShell.PSConsoleReadLine.WithHistoryFileMutexDo(Int32 timeout, Action action)
   在 Microsoft.PowerShell.PSConsoleReadLine.MaybeAddToHistory(String result, List`1 edits, Int32 undoEditIndex, Boolean fromDifferentSession, Boolean fromInitialRead)
   在 Microsoft.PowerShell.PSConsoleReadLine.InputLoop()
   在 Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics, CancellationToken cancellationToken)

[daxian-dbw]

Thanks for reporting the issue. This is a known issue related to surrogate pair handling. Will close as a duplicate of #1329