Skip to content

'WinIOError' thrown from 'Ctrl+L' was fixed in recent versions #1315

Closed
@daxian-dbw

Description

@daxian-dbw

The IOException thrown from Ctrl+l was fixed in recent versions.
If you run into this one (seeing a stack trace like the below one), please try out the latest version of PSReadLine from PowerShell Gallery.

Exception:
System.IO.IOException: The parameter is incorrect.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.Console.SetWindowPosition(Int32 left, Int32 top)
   at Microsoft.PowerShell.PSConsoleReadLine.ProcessOneKey(ConsoleKeyInfo key, Dictionary`2 dispatchTable, Boolean ignoreIfNoAction, Object arg)
   at Microsoft.PowerShell.PSConsoleReadLine.InputLoop()
   at Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics)

This issue was fixed by #790. The fix was included in 2.0.0-beta4 and newer versions.
For more information, take a look at #922 (comment).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Resolution-DuplicateThere's another issue on the tracker that's pretty much the same thing.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions