-
Notifications
You must be signed in to change notification settings - Fork 113
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
Cannot use spacemacs-theme-custom colors with variables #139
Comments
I just discover that the issue has nothing to do with variable passing. If I assign the value before a call to |
For the the record, I'm using |
I was trying out ewal and ran into this. The current definition of (cl-loop for (var . val) in spacemacs-theme-custom-colors
do (set var val)) This would fix the issue here and make it possible to later change the custom colors and (re)generate a theme. |
Amazing! Should I make the changes in a PR branch to test them out or do you prefer to make the chnages? Also what do you think of ewal? |
Feel free to make a PR. I won't be able to get around to it immediately.
It looks really good for some of the themes I've tried, and it looks better than the Xresources theme for the colors I've tried (often a lot better). It's also nice that it's easy to change the theme on the fly when using the daemon (e.g. |
The fewer colors thing is intentional for a more modern look, but you bring up a fair point in that it shouldn't be forced on the user. What do you think about making two functions? One modern/minimal, and the other with all the bells and whistles? If you wanna see all the available colors use |
…yer. Currently, the theme also modifies `spacemacs-dark` if also loaded in `dotspacemacs-themes`. A [fix](nashamri/spacemacs-theme#144) for this is on it's way upstream to `spacemacs-theme`, but the maintainer already gave their [blessing](nashamri/spacemacs-theme#139).
…yer. Currently, the theme also modifies `spacemacs-dark` if also loaded in `dotspacemacs-themes`. A [fix](nashamri/spacemacs-theme#144) for this is on it's way upstream to `spacemacs-theme`, but the maintainer already gave their [blessing](nashamri/spacemacs-theme#139).
Remove dyn-let as discussed in issue #139.
…yer. Currently, the theme also modifies `spacemacs-dark` if also loaded in `dotspacemacs-themes`. A [fix](nashamri/spacemacs-theme#144) for this is on it's way upstream to `spacemacs-theme`, but the maintainer already gave their [blessing](nashamri/spacemacs-theme#139).
…yer. Currently, the theme also modifies `spacemacs-dark` if also loaded in `dotspacemacs-themes`. A [fix](nashamri/spacemacs-theme#144) for this is on it's way upstream to `spacemacs-theme`, but the maintainer already gave their [blessing](nashamri/spacemacs-theme#139).
…yer. Currently, the theme also modifies `spacemacs-dark` if also loaded in `dotspacemacs-themes`. A [fix](nashamri/spacemacs-theme#144) for this is on it's way upstream to `spacemacs-theme`, but the maintainer already gave their [blessing](nashamri/spacemacs-theme#139).
…yer. Currently, the theme also modifies `spacemacs-dark` if also loaded in `dotspacemacs-themes`. A [fix](nashamri/spacemacs-theme#144) for this is on it's way upstream to `spacemacs-theme`, but the maintainer already gave their [blessing](nashamri/spacemacs-theme#139).
Regardless of whether I use
custom-set-variables
orsetq
custom colors are only applied if I explicitly quote analist
. I cannot pass in a variable that contains an alist.The text was updated successfully, but these errors were encountered: