I was surprised by this, since I don't use themes at all. It seems to be related to #881. It happens the first time (use-package …) is called. It isn't a problem with a specific package being configured — if I comment out the first use-package call, I get the same error with the second. If I comment out every use-package call, the error doesn't occur.
I generally run a newer Emacs in a GUI, but due to some funky hardware setup, in this case, I'm using 27.1 on a terminal.
My custom-file specifies:
'(tool-bar-mode nil)
And this get applied prior to use-package being called. Strangely, C-h a tool-bar-mode RET shows that the function is known and loaded, and evaluating (tool-bar-mode 1) or … -1 in ielm works as expected. So I have no idea why use-package specifically is causing this.
This is happening with commit bcf0984cf55b70fe6896c6a15f61df92b24f8ffd.
Certain package definitions are causing an error on Emacs 27.1, when run in a terminal. Here's a stacktrace:
I was surprised by this, since I don't use themes at all. It seems to be related to #881. It happens the first time
(use-package …)
is called. It isn't a problem with a specific package being configured — if I comment out the firstuse-package
call, I get the same error with the second. If I comment out everyuse-package
call, the error doesn't occur.I generally run a newer Emacs in a GUI, but due to some funky hardware setup, in this case, I'm using 27.1 on a terminal.
My
custom-file
specifies:And this get applied prior to
use-package
being called. Strangely,C-h a tool-bar-mode RET
shows that the function is known and loaded, and evaluating(tool-bar-mode 1)
or… -1
in ielm works as expected. So I have no idea whyuse-package
specifically is causing this.This is happening with commit bcf0984cf55b70fe6896c6a15f61df92b24f8ffd.