ListView does not render the first selection after reuse in Vi insert mode
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Anfängerfreundlichkeit
- 65/100
Rechercherichtung
Reproduce with pwsh -noprofile, Vi edit mode, and ListView prediction settings, then compare the first DownArrow after reopening ListView with the initial use. Trace the ListView navigation path and Vi insert-mode handling. Done means the first press visibly highlights the internally selected item on every reuse, with Enter and subsequent navigation remaining consistent.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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
Long-time Vi mode user. For a couple of years, I've been dealing w/ an obscure behavior and finally taking time to report it.
Issue: In Vi insert mode with PredictionViewStyle set to ListView, the first DownArrow press after reusing the list selects a history item internally but fails to render its highlight until another navigation key is pressed.
More Detail:
When using these PSReadLine options:
Set-PSReadLineOption -PredictionViewStyle ListView
Set-PSReadLineOption -EditMode Vi
the first DownArrow press in the prediction selects a history entry internally without visually rendering the selection highlight.
Pressing Enter at that point executes/accepts the first history item, which indicates that the item was selected despite no visible highlight. Pressing DownArrow a second time causes the selection highlight to appear. After that, UpArrow and DownArrow behave and render normally.
Note: The issue does not occur the first time ListView is used in a new PowerShell session; it only begins after ListView has already been used once.
Entering Vi normal mode and then returning to insert mode resets the behavior, e.g. Esc + i. After that, the first DownArrow press renders correctly again, until the issue recurs.
Environment data
PS Version: 7.6.3
PS HostName: ConsoleHost
PSReadLine Version: 2.4.5
PSReadLine EditMode: Vi
OS: 10.0.26100.1 (WinBuild.160101.0800)
BufferWidth: 180
BufferHeight: 50
Steps to reproduce
- Run
pwsh -noprofile - Run
Set-PSReadLineOption -EditMode Vi - Run
Set-PSReadlineOption -PredictionViewStyle ListView - In Vi insert mode, type text that produces history predictions
- Use the ListView and navigate it with DownArrow (on the first use in a new session, the highlight appears as expected)
- Complete or dismiss the ListView (e.g. ESC to dismiss and
ccto clear the line/command) - Trigger ListView again and press DownArrow once
On the second and later uses of ListView:
- The first DownArrow press appears to do nothing visually.
- No entry is highlighted.
- Pressing Enter accepts or runs the first list item, indicating that the selection changed internally.
- Pressing DownArrow a second time causes the visual highlight to appear.
- Subsequent UpArrow and DownArrow presses render correctly.
Expected behavior
- Each
DownArrowpress in ListView should visibly move the selection to the next prediction. - On the first press, the first matching history entry should be highlighted immediately.
- The visible highlight and the internally selected item should always remain in sync.
- This should behave consistently every time ListView is opened while in Vi insert mode.
Actual behavior
- After ListView has been used once, reopening it in Vi insert mode produces no visible highlight on the first
DownArrowpress. - The first item appears unselected, but it is selected internally.
- Pressing
Enteraccepts/runs that first item despite the missing highlight. - A second
DownArrowpress makes the highlight appear, after which navigation renders normally. - Pressing
Escand thenitemporarily resets the behavior.
- Vorherrschende Sprache
- C#
- Sterne
- 4.4k
- Forks
- 341
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus PowerShell/PSReadLine
-
Needs-Triage :mag:
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
PowerShell/PSReadLine#5205 ·
-
Needs-Triage :mag:
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
PowerShell/PSReadLine#5195 ·
-
Needs-Triage :mag:
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
PowerShell/PSReadLine#5121 ·
-
Needs-Triage :mag:
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 64/100
PowerShell/PSReadLine#5045 ·
-
Area-CommandHelp Issue-Enhancement
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 68/100
PowerShell/PSReadLine#3470 · 3 Reaktionen ·
Alle Issues in PowerShell/PSReadLine
Ähnliche Issues
-
effort:S P3 refactor
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
nightscout/nocturne#1532 ·
-
core dependencies
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 80/100
-
documentation
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
-
C#/.NET Roslyn LSP Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
DotNetNext/SqlSugar#1458 ·