Dongbo Wang

The suggestion to use `Frecency` algorithm for history prediction (#1808) and also possibly a local ML model to provide predictions from the history patterns would also require a more powerful...

I have been wanting to do this, but it just couldn't get in the priority cut due to the limited team resources. @StevenBucher98 has put this in the 2.3.0 release...

@darthwalsh and @iSazonov Thank you both for the investigation so far. I will need to get a macOS to try reproducing the issue. A couple clarification: 1. the mutex is...

I cannot reproduce the issue with the repro steps described in the issue. The GIF below is from WSL Ubuntu 18.04 with PowerShell 7.4-preview.3 + PSReadLine 2.3.1-beta1. I tried on...

I can reproduce the issue after moving the prompt function to `$PROFILE`. We will investigate it.

Unfortunately, we don't own that doc.

The only way I can think of is changing `scriptBlock.Invoke(k, arg);` to the following: ``` PowerShell.Create(RunspaceMode.CurrentRunspace) .AddScript(scriptBlock.ToString()) .AddArgument(k) .AddArgument(arg) .AddCommand("Out-Default") .Invoke(); ``` By explicitly set the downstream cmdlet to be...

Yup, that would work for the closure: ``` PowerShell.Create(RunspaceMode.CurrentRunspace) .AddCommand("Invoke-Command") .AddParameter("ScriptBlock", scriptBlock) .AddParameter("ArgumentList", new[] { k, arg }) .AddCommand("Out-Default") .Invoke(); ``` It will still be a behavior change though, as...

Alright, reopen this issue as it looks like something we are interested in improving.

Note that `PSReadLine` doesn't know there is text rendered on the console, so when typing anything after the handler execution, the new characters will be rendered at the original cursor...