Spacemacs doesn't recognize theme belongs to a package #15538
Comments
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid! |
|
I was having this issue with 'doom-old-hope', I checked out and saw that 'spacemacs-theme-name-to-package' is a list which holds the themes and its location(? Not sure), I'm not good with elisp. That's why I didn't think much and manually added 'doom-old-hope' to the list, instead of finding an actual solution. |
github-actions
bot
removed
the
stale
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid! |
smile13241324
added
Feature request
and removed
stale
|
Currently this is not officially supported, I will see if I can add a solution |
|
I believe I have previously ran into this issue with the modus-themes package. The modus themes themselves are built-in to Emacs now (28+), but if a user installs the modus-themes package on Emacs 27.X and includes the theme in their theme rotation they can experience it. |
Indeed, that's the culprit. I had a conversation with @lebensterben about it once in another PR but that wasn't merged if I recall. |
|
#15453 was the PR. It was merged, but that just added to the alist. There was discussion about a different solution using a hash table. |
I have the package
color-theme-moderninstalled and have addedword-perfect-themefrom that package to my rotation of default Spacemacs themes. Unlike thethemes-megapacklayer,color-theme-modernis a monolithic package that supports multiple themes. Spacemacs keeps searching for a package namedword-perfect-themeat startup, apparently because it thinks each theme must be individually packaged. Can I suppress this behavior?The text was updated successfully, but these errors were encountered: