Closed hisae1421 closed 2 weeks ago
@hisae1421, you were using a pretty old version of PSReadLine (2.0.0-beta2 or prior), and it's likely that the issue was fixed in a newer version. Please upgrade to the 2.3.5 version of PSReadLine from PowerShell Gallery. See the upgrading section for instructions. Please let us know if you run into the same issue with the latest version.
Hi, I use the latest already :
Has to be something else :( this is from the visual studio code that shows me the issue every time by the way, not another PowerShell environment
Hi, I seem to run in to the same issue:
I only get the error in the new powershell extension version. Version 2024.4.0 works fine.
I also have it when i revert back to older version but indeed the issue started last week, probably when 2024.5.0 got deployed
I solved it by installing PowerShell 7 but I don't understand why vsCode extension is not compliant anymore with my default 5.1 powershell environement
Why can't I set this issue to opened ? Some bot said something wrong about it and that's it ? Archived forever ? 😂
@hisae1421 and @Growbutski The exception indicates it's a problem with PS VSCode extension, not PSReadLine. Please report your issue in https://github.com/PowerShell/vscode-powershell instead.
Prerequisites
Exception report
Screenshot
Environment data
Steps to reproduce
Visual Studio launches PowerShell terminal
Expected behavior
I don't understand.... Expected behavior is not to have an error message I guess ?
Actual behavior
Shows the error message above