-
Notifications
You must be signed in to change notification settings - Fork 317
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 1 Keys:
UpArrow
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: top
Actual value was -1.
at System.Console.SetCursorPosition(Int32 left, Int32 top)
at Microsoft.PowerShell.PSConsoleReadLine.ReallyRender(RenderData renderData, String defaultColor)
at Microsoft.PowerShell.PSConsoleReadLine.ForceRender()
at Microsoft.PowerShell.PSConsoleReadLine.HistoryRecall(Int32 direction)
at Microsoft.PowerShell.PSConsoleReadLine.PreviousHistory(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
I am afraid that I closed the relevant terminal window and that thus far I have been unable to reproduce the bug.
Environment data
PS Version: 5.1.19041.5737
PS HostName: ConsoleHost (Windows Terminal)
PSReadLine Version: 2.0.0-beta2
PSReadLine EditMode: Windows
OS: 10.0.19041.1 (WinBuild.160101.0800)
BufferWidth: 120
BufferHeight: 30Steps to reproduce
Unknown. Seemingly though the problem occurs upon some (which?) instances of either: pressing the up arrow, on its own, so as to paste the last command from the buffer; pressing ctrl-alt-upArrow, which is a keyboard shortcut that I have assigned, using the program Autohotkey, to maximise the current window. The problem occurred - it has occurred only once - a second or two after I first opened a terminal window (but I have tried and failed to reproduce the exact, error-giving, scenario.)
Expected behavior
No exception.
Actual behavior
Exception.
This form seems to need an 'other information' field. For, I want to add the following.
Cf. #4588
Cf. #4599.
Cf. #4585?
Cf. #4682?
But, ah: the problem seems to be the one documented here. Might that account of the problem be made more visible somehow? Perhaps you should even make the installer for the Windows Terminal ensure that a recent version of 'PSReadLine' is installed.
I have installed the latest stable version of PSReadLine by following these instructions. I shall see whether the problem reoccurs.