-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prescient-Selectrum just stops working #84
Comments
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 the other session. But under no circumstances should you see the behavior you're describing. One thing you could check is the return value 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...? |
I've tried the |
I disabled and then re-enabled |
When I have Prescient, things are amazing. I love it. However, it seems to periodically just STOP, and I'm having trouble finding the right combination of turning it off, re-evaluating, deleting the persistent file, etc which brings it back (I'm still searching). I have verified that in "off" periods, my M-x results are the same as if there were no prescient at all. Any help?
Some notes:
I am using Selectrum
I am an EXWM user and sometimes open sub-emacs sessions, so that there would be two different sessions utilizing prescient simultaneously. It's possible that this is breaking it.
My files are under version control, so occasionally git might touch my prescient file.
I have the impression that one of these two are to blame. I have tasted the wonderful success of prescient and am going into withdrawals without it. Help!
The text was updated successfully, but these errors were encountered: