From: Sam Halliday <sam.halliday@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: "clean" starting point for custom-theme-set-faces
Date: Wed, 17 Sep 2014 03:00:54 -0700 (PDT) [thread overview]
Message-ID: <287e4dab-9ee0-4840-bb8f-0fc1b18a5501@googlegroups.com> (raw)
Hi all,
I'm creating a custom colour theme for emacs inspired by IntelliJ's Darcula. Work in progress here:
https://github.com/fommil/unix/blob/master/.emacs.d/lisp/Darkula-theme.el
But there are a couple of things that confuse me about emacs faces, even after reading the documentation and I'd appreciate some guidance:
1. When a theme is loaded, what are the default "inherit" values for all the faces that I'm defining? Is there an implicit "inherit" based on what that face was before the theme was loaded?
I've found that I need to override a lot of things with e.g. ":underline nil" when actually I want to be defining my faces from a clean slate, inheriting from "default" without having to explicitly write that.
2. How do I re-use attributes inside custom-theme-set-faces? I can't put the list of faces inside a (let ) because custom-theme-set-faces is expecting one parameter per face. Ideally I'd like to define a bunch of things in some form of data structure so that I don't have to repeat the values, and also so that I can parametrise the theme. (e.g. I could have a function that returns my theme with a permutation on font-lock colours)
Best regards,
Sam
next reply other threads:[~2014-09-17 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 10:00 Sam Halliday [this message]
2014-09-17 11:41 ` "clean" starting point for custom-theme-set-faces Alex Kost
[not found] ` <mailman.9025.1410954123.1147.help-gnu-emacs@gnu.org>
2014-09-17 12:31 ` Sam Halliday
2014-09-18 5:23 ` Alex Kost
2014-09-17 15:41 ` Sam Halliday
2014-09-18 9:52 ` Sam Halliday
2014-09-17 16:42 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=287e4dab-9ee0-4840-bb8f-0fc1b18a5501@googlegroups.com \
--to=sam.halliday@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.