{{ message }}
Error on read command input #4851
Description
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
I am unable to use my profile in the vscode extension terminal because it will cause PSReadLine errors
PowerShell Version
~/Documents/workstation/esh e91e649@master >$PSVersionTable; $Host
Name Value
---- -----
PSVersion 7.4.0
PSEdition Core
GitCommitId 7.4.0
OS Microsoft Windows 10.0.19045
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Name : Visual Studio Code Host
Version : 2023.8.0
InstanceId : 6250413c-638c-4418-810f-b7fd28bd672e
UI : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture : zh-CN
CurrentUICulture : zh-CN
PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled : True
IsRunspacePushed : False
Runspace : System.Management.Automation.Runspaces.LocalRunspaceVisual Studio Code Version
~/Documents/workstation/esh e91e649@master >code --version
1.85.0-insider
2e721b6ec731c22cd3c2853dbc7ad69deb447515
x64Extension Version
~/Documents/workstation/esh e91e649@master >code --list-extensions --show-versions | Select-String powershell
ms-vscode.powershell@2023.8.0Steps to Reproduce
run this in vscode powershell extension host
$a=[System.Collections.ArrayList]@()
Add-Member -InputObject $a -MemberType ScriptMethod -Name Pop -Value {
$value = $this[$this.Count-1]
$this.RemoveAt($this.Count-1)
$value
}
Register-EngineEvent PowerShell.OnIdle -Action {
if($a.Count -gt 0) {
$a.Pop().Invoke()
}
}
then wait.
Visuals
Logs
No response
Activity
SydneyhSmith commentedon Dec 5, 2023
Thanks for the detailed info-- we will need to take a closer look and investigate