PSReadLine 2.4.5 shows no inline history prediction on PowerShell 7.6.0, while 2.3.6 works
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Reproduce the issue in a clean pwsh -NoProfile session using the listed PSReadLine settings and compare version 2.4.5 with 2.3.6. Trace the history prediction and InlineView behavior, then verify that a typed prefix shows the saved command and that RightArrow accepts it.
Written by the indexing model from the issue text.
Description
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
- Start a clean PowerShell session:
pwsh -NoProfile
- Configure PSReadLine:
Import-Module PSReadLine
Set-PSReadLineOption -PredictionSource History
Set-PSReadLineOption -PredictionViewStyle InlineView
- Run a command so it is saved into PSReadLine history:
echo __psrl_probe_987654
- On the next prompt, type this prefix without pressing Enter:
echo __psrl_
- Observe that no inline history prediction is shown, and pressing
RightArrowdoes 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
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 341
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PowerShell/PSReadLine
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSReadLine#5205 ·
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PowerShell/PSReadLine#5195 ·
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PowerShell/PSReadLine#5121 ·
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
PowerShell/PSReadLine#5045 ·
-
Area-CommandHelp Issue-Enhancement
Difficulty 1/5 Under an hour Newbie friendliness 68/100
PowerShell/PSReadLine#3470 · 3 reactions ·
All issues in PowerShell/PSReadLine
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 75/100
sillsdev/languageforge-lexbox#2665 ·
-
bug documentation frontend
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
azurenoops/spin_agent#975 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·