doom-vibrant not a first class citizen theme? about themes

[hlissner]

Could you check the value of custom-theme-load-path and let me know if it contains the path to the doom-theme? (M-x describe-variable RET custom-theme-load-path)

If not, it is likely that something, elsewhere in your config is modifying this variable. To get around this, you can do:

;; no need for (require 'doom-themes)
(require 'doom-vibrant-theme)
(load-theme 'doom-vibrant t)

[ekaschalk]

I can confirm the same situation with (the most recent dev branch of) spacemacs. Doom theme is on the loadpath and the load-theme snippet doesn't work. It can be gotten around with a call to cycle-spacemacs-theme in the user-config but this is not ideal.

[hlissner]

(Sorry for the late reply)

@ekaschalk It's possible spacemacs has its own theme-loading code that runs later in the startup process; this would override any custom effort of yours. I'm not a spacemacs users to know for certain, but from the documentation, I suspect this will work:

(require 'doom-themes)
(setq-default dotspacemacs-themes '(doom-one))

Let me know how that fares.