Predictive text implementation is terrible

Open
#5,169 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp
Domain
cli

Research direction

Reproduce the behavior in PowerShell 7.6.2 with the supplied msys2_shell.cmd command and the step “Type something in powershell.” Locate the predictive-text implementation and its tests; done means suggestions are visually distinct and can be dismissed or partially accepted.

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
D:\msys64\msys2_shell.cmd -ucrt64 -defterm -here -full-path -no-start
Screenshot

Predictive text can be a really useful feature but it's implementation here is terrible.

  1. Suggested text here is the exact same colour as what I've typed. It needs to be more distinguishable.
  2. There's no way (that I can fathom) to simply dismiss the suggestion
  3. There's no way (that I can fathom) to accept a subset of the suggestion, e.g. just the next word

There may be some obtuse way to configure these things, but I shouldn't have to do that, these are reasonable expectations out of the box.

Image
Environment data
7.6.2
Steps to reproduce

Type something in powershell

Expected behavior

useful predictive text that I can distinguish from typed text, and dismiss or partially accept

Actual behavior

confusing indistinguishable predictive text that I cannot dismiss or partially accept

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.