Get-PSRead...).HistorySavePath glitches the console when set to $null

Open
#4,039 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
csharp, powershell
Domain
cli

Research direction

Start by reproducing the issue with (Get-PSReadLineOption).HistorySavePath = $null, then press Up or enter a command in the Windows PowerShell console. Trace the HistorySavePath handling and console rendering behavior; done means disabling history does not display stray keystrokes or require a second Enter, while normal sessions remain unaffected.

Written by the indexing model from the issue text.

Description

Needs-Triage :mag:
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
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

image

Environment data
PS Version: 7.4.2
PS HostName: ConsoleHost
PSReadLine Version: 2.3.5
PSReadLine EditMode: Windows
OS: 10.0.22621.2860 (WinBuild.160101.0800)
BufferWidth: 120
BufferHeight: 9001
Steps to reproduce
  1. open powershell
  2. write this:
 (Get-PSReadLineOption).HistorySavePath = $null
  1. 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

Dominant language
C#
Stars
4.4k
Forks
341
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PowerShell/PSReadLine

All issues in PowerShell/PSReadLine

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.