Repository navigation
Closed
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues, especially the pinned issues.
Exception report
Oops, something went wrong. Please report this bug with the details below.
Report on GitHub: https://github.com/lzybkr/PSReadLine/issues/new
-----------------------------------------------------------------------
Last 135 Keys:
& Space " C : / U s e r s / l e n o v o Space i 3 / A p p D a t a / L o c a l / P y t h o n / p y t h o n c o r e - 3 . 1 4 - 6 4 / p y t h o n . e x e " Space " c : / U s e r s
/ l e n o v o Space i 3 / D e s k t o p / P r o j e c t - A N U / e x a m Space e l i g i b i l i t y . p y " Enter
Exception:
System.ArgumentOutOfRangeException: The value must be greater than or equal to zero and less than the console's buffer size in that dimension.
Parameter name: left
Actual value was -2.
at Microsoft.PowerShell.Internal.VirtualTerminal.set_CursorLeft(Int32 value)
at Microsoft.PowerShell.PSConsoleReadLine.ReallyRender(RenderData renderData, String defaultColor)
at Microsoft.PowerShell.PSConsoleReadLine.ForceRender()
at Microsoft.PowerShell.PSConsoleReadLine.Insert(Char c)
at Microsoft.PowerShell.PSConsoleReadLine.SelfInsert(Nullable`1 key, Object arg)
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)Screenshot
Environment data
..Steps to reproduce
After Running the program itself, this issue is coming
Expected behavior
After running the program and answering the first 1 question there is another question after answering a number the same number is occurring, but it should come either allowed or not allowed
Actual behavior

Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Jan 11, 2026
Anupriya-hub-1, 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.