-
Notifications
You must be signed in to change notification settings - Fork 87
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
setq: End of file during parsing #23
Comments
Which Smex version do you use? Check the version info at the beginning of smex.el. Please post a backtrace:
|
Smex version 1.1.1, although the problem also exists with 1.1.4. I used smex for a long time with no issue, the problem started appearing only last week or so. Not sure how this is possible Unfortunately, toggle-debug-on-error did nothing. The messages buffer says
No new buffers appeared which could contain the trace. |
That indicates that something in your Emacs environment has changed. Vanilla Emacs 24.1.1 plus |
I investigated further and found out that the root of the problem was that I had a ".smex-items" file in my home directory that was empty. I deleted it, now it works fine again. I don't know how this file came to be. If it happens again, I will report back so we can find out. Thanks for your time. |
This happened to me too yesterday, with no obvious changes to my environment as far as I can see. After removing the ~/.smex-items file everything worked fine again. |
I've added a fix to ignore empty save files, but I still have no idea how they could appear in the first place. Did your save files suddenly become empty or were you just getting started with Smex? |
In my case, they became empty. Smex has been working with no problems for years before. |
Same here - I have been using smex for years, and the file suddenly I have another computer with mostly the same setup and there the file is |
Hi
I start emacs with
emacs -q -l smex.el
(so no other modules are loaded).M-x smex-intitalize
fails withsetq: End of file during parsing
.Emacs version: 24.1.1.
Do you know what causes this? If not, I can dig into it sometime.
The text was updated successfully, but these errors were encountered: