X Tutup
Skip to content

PSReadLine 2.4.5 shows no inline history prediction on PowerShell 7.6.0, while 2.3.6 works #5116

@CN-Scars

Description

@CN-Scars

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

N/A

Screenshot

No exception is involved. If needed, I can provide a screenshot/GIF showing that PSReadLine 2.4.5 does not show inline history prediction

Environment data

PS Version: 7.6.0
PS HostName: ConsoleHost (Windows Terminal)
PSReadLine Version: 2.4.5
PSReadLine EditMode: Windows
OS: 10.0.26100.7705 (WinBuild.160101.0800)
BufferWidth: 120
BufferHeight: 30

Steps to reproduce

  1. Start a clean PowerShell session:
pwsh -NoProfile
  1. Configure PSReadLine:
Import-Module PSReadLine
Set-PSReadLineOption -PredictionSource History
Set-PSReadLineOption -PredictionViewStyle InlineView
  1. Run a command so it is saved into PSReadLine history:
echo __psrl_probe_987654
  1. On the next prompt, type this prefix without pressing Enter:
echo __psrl_
  1. Observe that no inline history prediction is shown, and pressing RightArrow does nothing.

Expected behavior

An inline history prediction should appear after typing a prefix of a recently executed command.

For example, after running:

echo __psrl_probe_987654

typing:

echo __psrl_

should show the rest of the command as an inline suggestion, and pressing RightArrow should accept it.

Actual behavior

No inline history prediction is shown.

PredictionSource is set to History, PredictionViewStyle is set to InlineView, and PSReadLine history is being saved correctly, but no inline suggestion appears and pressing RightArrow does nothing.

The issue reproduces in pwsh -NoProfile.

On the same machine and in the same environment, PSReadLine 2.3.6 works, while PSReadLine 2.4.5 does not.

Additional notes:

  • Failing version: PSReadLine 2.4.5
  • Working version: PSReadLine 2.3.6
  • History file is updated correctly
  • This is not caused by my profile, because it reproduces in pwsh -NoProfile

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs-Triage 🔍It's a new issue that core contributor team needs to triage.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      X Tutup