-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Symbol's value as variable is void - after update system #16119
Comments
Hi, Today when I started the elpa/melpa package update I will try to make an initial install without custom .spacemacs. My guess is that some elpa package has a major bug "bricking" spacemacs Bye, |
Ok, initial "installation" with default .spacemacs works. as --debug-init does not make a difference (does not stop in the debugger) I will |
I have just installed Emacs 28.2 on a new company Windows (using MSYS2) and I am starting up Spacemacs. I have the same problem. In the
I have Emacs 28.2 & (a several months old devel version of) Spacemacs running on another Windows machine, and Other files/commands that issue the error while loading or in action are:
|
Installation with default .spacemacs "works" (which I forced by just deleting my customized .spacemacs file), but if I exit and relaunch spacemacs, I'm right back in these errors. I even tried removing all layers and user-added packages, and I still get the error, so I fear it's something very core. Of course, I too tried cleaning my repo of all local files which borked my ability to do a package rollback. Although spacemacs was too broken to do it, I suppose I could've done it manually, but not anymore :( I hope that if this breaks things for so many people, it'll get noticed and fixed quickly |
Running I suspect this is where the bug was introduced: emacs-evil/evil@0cbd61f#diff-47302cddd5e39bfe2c8dcd1b006b8a2c683f070472d9bb138d20a243a3d71aa1L61-L62 |
W00t! Crudely reverting that edit by manually editing my local
fixes the issue for me. For anyone coming to this and wanting to quickly fix it, the file I edited was at |
TLDR: This is a bug in If you have updated your packages and received the bugged version of evil, you can fix it by editing
and it's likely prudent to also delete the corresponding |
Just to add some details to I found two identical instances of Spacemacs came up. |
Thanks @dankessler, that works!! and I see that they responded to your issue in the evil repository. |
Great! While this now seems fixed upstream, anyone whose spacemacs is currently bricked may need to first use my suggested fix in order to get spacemacs working well enough to update packages, at which point they should be good to go. |
Is another option to delete that package manually from |
That would probably also work |
I did:
Spacemacs picked up the just released 20230813.1704 evil package and resumed normally. Thank you for identifying the bug and alerting maintainers. |
Description
After updating the emacs version to 29.1-4 (the latest stable version in my system Linux 6.1.44-1-MANJARO #1 SMP PREEMPT_DYNAMIC Wed Aug 9 09:02:26 UTC 2023 x86_64 GNU/Linux).
When emacs start I only get this message:
⛔ Error (use-package): window-purpose/:config: Symbol’s value as variable is void: fun-name
⛔ Error (use-package): winum/:catch: Symbol’s value as variable is void: fun-name
⛔ Error (use-package): ws-butler/:catch: Symbol’s value as variable is void: fun-name
⛔ Error (use-package): xterm-color/:catch: Symbol’s value as variable is void: fun-name
⛔ Warning (initialization): An error occurred while loading ‘/home/username/.emacs.d/init.el’:
Symbol's value as variable is void: fun-name
Reproduction guide 🪲
Observations: 👀 💔
I tried with a new fresh installation (removing .emacs.d folder and .spacemacs file) but still the issue remains there.
If I try to update the packages I get this message:
⛔ Warning (spacemacs):
Error while contacting melpa repository!
I also tried this: How to fix Symbol's value as variable is void errors on startup? but didn't work.
And when I run emacs with the flag --debug-init I didn't get any error in the terminal.
The text was updated successfully, but these errors were encountered: