spacemacs 2023-08-12 | Slack Archive

murtaza5215:08:08

Hi, just updated all packages in spacemacs and now when spacemacs starts I get this error - Symbols value as variable is void - fun-name this leads to an initialization error, and all of emacs is unusable.

practicalli-johnny19:08:26

If the issue still occurs after the packages downloaded and Emacs was restarted, then it seems likely that there is an issue with one of the packages The quick approach would be to use the rollback packages link on the home buffer, SPC b h

practicalli-johnny19:08:18

From the other error output, it seems that window-purpose package is the problem. Normally I would suggest removing tha package and restart Emacs to download the package again. But as a clean install was done already then I doubt this would resolve the issue.

practicalli-johnny19:08:37

If code has been added to the user config to define where windows should be placed, then try comment that code and restart (helps determine if package config has changed)

practicalli-johnny20:08:41

Or as window-purpose is not a default package, comment the layer in the Spacemacs user configuration Maybe some info in the window-purpose layer docs will help with the correct config https://develop.spacemacs.org/layers/+spacemacs/spacemacs-purpose/README.html

murtaza5206:08:08

thanks for the reply. I am using practicalli spacemacs.d config, and have not modified anything. I greped the repo for window-purpose, and found it inside the emacs-custom-settings.el

practicalli-johnny07:08:36

The emacs-custom-settings.el contains configuration set by the Emacs customize command. Emacs may write other config info there when using Emacs. practicalli/spacemacs-config doe not include this file in the repository. The file is used by the Practicalli config to cache some user specific config once Emacs is run, e.g safe variables, layouts, options set by customize Suggest stopping Emacs and moving emacs-custom-settings.el to a backup location.

practicalli-johnny12:08:16

After some further investigation, it seems several other layers include the window-purpose package

layers/+tools/shell/packages.el:380:(defun shell/post-init-window-purpose ()
layers/+lang/python/packages.el:524:(defun python/post-init-window-purpose ()
layers/+email/mu4e/packages.el:191:(defun mu4e/post-init-window-purpose ()
layers/+email/gnus/packages.el:145:(defun gnus/post-init-window-purpose ()
layers/+chat/erc/packages.el:260:(defun erc/post-init-window-purpose ()
layers/+chat/jabber/packages.el:55:(defun jabber/post-init-window-purpose ()
layers/+chat/slack/packages.el:104:(defun slack/post-init-window-purpose ()
layers/+chat/rcirc/packages.el:191:(defun rcirc/post-init-window-purpose ()
layers/+email/notmuch/packages.el:175:(defun notmuch/post-init-window-purpose ()

The practicalli config does include the shell layer, so if there was a change in the window-purpose package that may be causing the issue, although looking in the Spacemacs elpa directory the latest package is window-purpose-20210628.715 so it seems it hasnt changed in several years.

practicalli-johnny12:08:39

I am not able to replicate the issue when updating the packages today. If backing up and moviing the emacs-custom-settings.el file does not resolve the issue, then perhaps something in the general troubleshooting guide will help. https://practical.li/spacemacs/install-spacemacs/troubleshooting/

murtaza5205:08:21

thanks, its working now

murtaza5219:08:53

the error has again started after a clean install of spacemacs -

⛔ 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/murtaza/.emacs.d/init.el':

Symbol's value as variable is void: fun-name

To ensure normal operation, you should investigate and remove the
cause of the error in your initialization file.  Start Emacs with
the '--debug-init' option to view a complete error backtrace.

didibus23:08:57

I get that as well. Seems 29.1 has broke my Spacemacs

murtaza5205:08:06

reinstalled spacemacs twice, and its working now. Second time I installed spacemacs again after removing the emacs-custom-settings.el file as suggested by @U05254DQM, maybe that did the trick.

didibus22:08:51

I'll have to try

practicalli-johnny07:08:17

There was an issue in the Evil package which has now been resolved. https://github.com/emacs-evil/evil/issues/1820 If this issue persists after a package update then try removing the evil package from the local Spacemacs elpa directory and restart Emacs to download the fixed package

2023-08-12

Channels