You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure you are able to repro it on the latest version
Search the existing issues.
Steps to reproduce
Import the CompletionPredictor module with Import-Module -Name CompletionPredictor
Set the PredictionSource option to HistoryAndPlugin with Set-PSReadLineOption -PredictionSource HistoryAndPlugin
Generate and execute a cobra-generated completion script (e.g., kubectl completion powershell | Out-String | Invoke-Expression)
Type a command that uses the completion script (e.g., kubectl get pods) and try to use predictive completion.
Expected behavior
~ ❯ kubectl get
> kubectl get pods [Completion]
> kubectl get csr [Completion]
> kubectl get nodes [Completion]
> ...
Actual behavior
~ ❯ kubectl get
> kubectl get pods [History]
Error details
No response
Environment data
Name Value
---------
PSVersion 7.3.4
PSEdition Core
GitCommitId 7.3.4
OS Microsoft Windows 10.0.19045
Platform Win32NT
PSCompatibleVersions {1.0,2.0,3.0,4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Version
0.1.0
Visuals
No response
The text was updated successfully, but these errors were encountered:
Unfortunately, the completion for native commands doesn't work with completion predictor today because they are too slow.
For a predictor to work with PSReadLine today, it needs to return results within 20ms, which is impossibly for most of native command completers. We have a work item in PSReadLine to allow longer timeout by separating the prediction rendering from the user typing rendering, but we haven't got to it yet.
Prerequisites
Steps to reproduce
Expected behavior
Actual behavior
Error details
No response
Environment data
Version
0.1.0
Visuals
No response
The text was updated successfully, but these errors were encountered: