Repository navigation
System.PlatformNotSupportedException when CTRL+L #922
Description
Stack trace
Last 2 Keys:
Ctrl+l Ctrl+l
Exception:
System.PlatformNotSupportedException: Operation is not supported on this platform.
at System.ConsolePal.SetWindowPosition(Int32 left, Int32 top)
at System.Console.SetWindowPosition(Int32 left, Int32 top)
at Microsoft.PowerShell.Internal.VirtualTerminal.SetWindowPosition(Int32 left, Int32 top)
at Microsoft.PowerShell.PSConsoleReadLine.ClearScreen(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, CancellationToken cancellationToken)
Environment data
PS version: 6.2.0
PSReadline version: 2.0.0-beta3
os: Linux shi-tri-lin 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
PS file version:
Steps to reproduce or exception report
- Launch PoweShell
pwsh - Press CTRL+L two times
- Exception happens
Activity
SteveL-MSFT commentedon Jun 18, 2019
This doesn't repro on 2.0.0-beta.4 on Ubuntu 18.04
lzybkr commentedon Jun 18, 2019
Steve Lee (@SteveL-MSFT) - This has been reported multiple times and likely is still an issue as nothing has been done to avoid the exception. But you might tag it as a dupe when you find the similar issues.
daxian-dbw commentedon Sep 15, 2019
close as a duplicate of #991
daxian-dbw commentedon Dec 12, 2019
Keep this issue open, as #991 is originally about a
ArgumentOutOfRangeException.daxian-dbw commentedon Jan 3, 2020
I took a closer look at this issue today and I think the issue had already been fixed by #790, which changed the implementation of
ClearScreenfrom usingConsole.ScrollBuffer,console.SetCursorPositionandconsole.SetWindowPositionto applying the escape sequence"0x1b[2J".That change was included in 2.0.0-beta4 and newer versions, this issue was reported to happen in 2.0.0-beta3.
Francesco Sorge (@sorge13248) Please try out the 2.0.0-rc1 version of PSReadLine from PowerShell Gallery.