You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Search the existing issues, especially the pinned issues.
Exception report
the bug happens both in the pre-installed powershell and 7.4.2 powershell, im using windows 11, the bug happend when i used "(Get-PSReadLineOption).HistorySavePath = $null" and then either pressed up arrow or typed in a command, some text "last 90 keystrokes" appeared: ![image](https://github.com/PowerShell/PSReadLine/assets/69431561/bb412007-bf3e-46fa-b6d9-801b97483027)
either write a command and press enter, or press up arrow
Expected behavior
all keystrokes you press appear on the "last X keystrokes:" part, and a big text that re-appears for each command that is run, and sometimes you need to press enter twice for the command to get run
Actual behavior
it happend each time i tried it, powershell goes back to normal if you restart the session, but if you start a separate session while the glitched one is running the separate session is normal, and the glitched one stays glitched, and the double enter keypress behavior is needed for commands to run
The text was updated successfully, but these errors were encountered:
Prerequisites
Exception report
the bug happens both in the pre-installed powershell and 7.4.2 powershell, im using windows 11, the bug happend when i used "(Get-PSReadLineOption).HistorySavePath = $null" and then either pressed up arrow or typed in a command, some text "last 90 keystrokes" appeared: ![image](https://github.com/PowerShell/PSReadLine/assets/69431561/bb412007-bf3e-46fa-b6d9-801b97483027)
Screenshot
Environment data
Steps to reproduce
Expected behavior
all keystrokes you press appear on the "last X keystrokes:" part, and a big text that re-appears for each command that is run, and sometimes you need to press enter twice for the command to get run
Actual behavior
it happend each time i tried it, powershell goes back to normal if you restart the session, but if you start a separate session while the glitched one is running the separate session is normal, and the glitched one stays glitched, and the double enter keypress behavior is needed for commands to run
The text was updated successfully, but these errors were encountered: