Pushing twice F8 leads to crash in console

[Schwanowski]

Hi there

i am using Visual Studio Code 1.41 Insider edition with Powerhell V7 latest preview and have a very strange issue.

Everything looks stable but when I try to press twice F8 to debug my scripts my console crashs entirely.

Its not related to code because when i reverse to ps ise and v5 all runs perfectly fine.

Can you please advice?

Environment data

Steps to reproduce or exception report

[Crash.txt]

Crash.txt

[msftrncs]

I am pretty sure this is the same as #1083, and there is no perfect solution for it yet. It happens because the history item that you are reaching with F8 is too long for the buffer in VS Code, and PSReadLine, when it tries to display it to you, it expects to put the cursor on the first line at the end of the matching text, the same as CTRL+r (or + s), but that position is not accessible from VS Code's console.

[Schwanowski]

Is there a chance to clear the history? I think I should be able to reproduce the error at least (and i will be able to work again). Carl Morris <[email protected]> schrieb am Sa., 23. Nov. 2019, 07:35:

…

I am pretty sure this is the same as #1083 <#1083>, and there is no perfect solution for it yet. It happens because the history item that you are reaching with F8 is too long for the buffer in VS Code, and PSReadLine, when it tries to display it to you, it expects to put the cursor on the first line at the end of the matching text, the same as CTRL +r (or + s), but that position is not accessible from VS Code's console. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1202?email_source=notifications&email_token=AIEXBZS2NWT73P7ZK72AFRDQVDFLZA5CNFSM4JQPOBAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE7O3WY#issuecomment-557772251>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIEXBZRKTZH2YSJ27BTCUZTQVDFLZANCNFSM4JQPOBAA> .

[Schwanowski]

I could fix it on my machine be uninstalling the powershell plugins and re-install them again.

Unforunately, I was not able to reproduce the issue. It seems be to related to

• a long code in the history ran by f8
• maybe a braket } error in the code

[msftrncs]

Any history item longer than your VS Code buffer (in lines), should cause the problem, when you use history search commands. This is different than UpArrow or DownArrow, as those always put the cursor on the last line. The search functions will try to place the cursor after the match, and if that match is off the buffer in VS Code, the exception occurs.

You can also erase your history, note its location is given in `Get-PSReadLineOption'. You could delete the file or edit the file to remove entries.

[Schwanowski]

ok thank you I will figure it out

[daxian-dbw]

Close as a duplicate of #1083

[msftrncs]

@Schwanowski, you might want to look at the Set-PSReadLineOption parameter -HistorySearchCursorMovesToEnd. It may be a workaround for this issue, but not sure it will apply to #1083.