Skip to content
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

Open
WorldsEndless opened this issue Dec 15, 2020 · 4 comments
Open

Prescient-Selectrum just stops working #84

WorldsEndless opened this issue Dec 15, 2020 · 4 comments

Comments

@WorldsEndless
Copy link

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!

@raxod502
Copy link
Member

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 (prescient--history-as-list), to see if prescient.el is correctly recording the list of the most recently used commands for you.

@raxod502
Copy link
Member

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...?

@WorldsEndless
Copy link
Author

I've tried the prescient-sort-length-enable nil but no effect. What I really miss the most is a working M-x that remembers my last command...

@WorldsEndless
Copy link
Author

I disabled and then re-enabled prescient-selectrum-mode while also turning off persistent mode, and it appears to be working for the time being. I'll keep looking into when it stops.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants