Radon Rosborough

I can reproduce your problem though, to be clear. See https://github.com/raxod502/prescient.el/issues/65.

Hmmm... it _should_ be fine to have multiple concurrent sessions. When updating the history file, whichever session has the most updates to install will "win" and overwrite the updates of...

I wonder if somehow a list is being reversed internally, and the most recently used candidates are being put at the bottom of the list...?

No, that seems like a bug. I suspect it is due to another internal change in Ivy. The best solution is to switch to [Selectrum](https://github.com/raxod502/selectrum), which does not have any...

I would, by the way, be happy to add somebody as a maintainer for `ivy-prescient.el`, as I do not feel like I can maintain that particular component well anymore.

If indeed this bug also exists in `company-prescient.el`, then I will take a look and see if I can fix it there. Thanks for the report. I will not test...

Actually, I take it back. This is not a bug, because regular Company does not prioritize exact matches. The reason you see the behavior in Ivy and Selectrum is because...

You'd want to start by adding a new user option to toggle the behavior. You'd probably want to port something like ```elisp (defun selectrum--move-to-front-destructive (elt lst) "Move all instances of...

Thanks for the report. Just to clarify, you observe different highlighting behavior if you are using stock Ivy to search for a regexp, without `ivy-prescient.el`?

You could check to make sure the command you expect is being run, with `C-h k C-x C-f`. Aside from that, however, your configuration looks exactly correct and I would...