PowerShell Extension terminal unusable when using Windows PowerShell with PSReadLine >= 2.2.5

[sba923]

Prerequisites

• I have written a descriptive issue title.
• I have searched all open and closed issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

Using the latest PowerShell Extension v2023.9.5, that comes with PSReadLine 2.3.4, is not possible with Windows PowerShell:

Reverting to PSReadLine 2.0.0, works, anything >= 2.2.5 yields the same behavior.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      5.1.22621.2506
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.2506
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Visual Studio Code Version

1.83.1
f1b07bd25dfad64b0167beb15359ae573aecd2cc
x64

Extension Version

[email protected]
[email protected]

Steps to Reproduce

Launch VScode, open any .ps1 file, and switch the PowerShell session to "Windows PowerShell (x64)"

Visuals

No response

Logs

1698477220-9012415f-77ca-49e4-a3a8-c49c6146ab011698477191238.zip

[andyleejordan]

@daxian-dbw do we know of any issues affecting PSReadLine and Windows PowerShell compatibility?

[SydneyhSmith]

@StevenBucher98 are you aware of any issues with PSReadLine and Windows PowerShell?

[sba923]

Sorry, forgot to share here that we determined with @JanDeDobbeleer that removing the "shell_integration": true" statement from my oh-my-posh profile makes the issue go away.

See https://twitter.com/SBarizien/status/1719646419416490051?t=8tUVSUirC7DB3X2oEan2pA&s=19 and #4731

[github-actions]

This issue has been marked as resolved and has not had any activity for 1 day. It has been closed for housekeeping purposes.