From: joakim@verona.se
To: Dave Abrahams <dave@boostpro.com>
Cc: emacs-devel@gnu.org
Subject: Re: customization theme users/use-cases/info
Date: Fri, 21 Oct 2011 15:42:52 +0200 [thread overview]
Message-ID: <m3fwimo3z7.fsf@chopper.vpn.verona.se> (raw)
In-Reply-To: <m2ty72em8m.fsf@pluto.luannocracy.com> (Dave Abrahams's message of "Fri, 21 Oct 2011 05:18:33 -0400")
Dave Abrahams <dave@boostpro.com> writes:
> I've been trying to use the themes feature that's been in Emacs since
> v23.x, and I am finding it a little bit awkward... most of what's in
> Emacs is oriented around using the regular customization interface,
> which stomps on anything set up by a theme. There isn't much
> information in the Emacs manual about how one might use themes, there's
> no information on EmacsWiki, and the facilities go un-mentioned in the
> Elisp manual. I might expect to find information there about the theme
> data structure, for example. Especially because of the silence of
> EmacsWiki (I think I made the one page that mentions themes there---no,
> color-theme is something different) it makes me wonder how the feature
> was designed, who's actually using it, and whether they're being
> well-served by it.
>
> Any information appreciated,
I'm using themes in my zen-mode.el package. I use it to create a
stackable set of features. Maybe it's easier with an example:
0:
1: A
2: A B
3: A B C
so; A B C are features. 0 1 2 3 are levels that you can switch between.
Customize makes this feature a bit problematic, as you have observed. It
happens frequently that a variable I want the theme to own winds up in
the default customize level instead. Then my entire stack fails, since
it means feature C winds up in level 0. I haven't delved much further. I
reported a bug at least.
--
Joakim Verona
next prev parent reply other threads:[~2011-10-21 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 9:18 customization theme users/use-cases/info Dave Abrahams
2011-10-21 13:42 ` joakim [this message]
2011-10-23 17:09 ` Policy for backwards-incompatible changes? (was: customization theme users/use-cases/info) Dave Abrahams
2011-10-25 4:08 ` Policy for backwards-incompatible changes? Chong Yidong
2011-10-31 19:13 ` Dave Abrahams
2011-11-06 6:48 ` Chong Yidong
2011-10-25 4:10 ` customization theme users/use-cases/info Chong Yidong
2011-10-31 19:42 ` Dave Abrahams
2011-11-06 6:45 ` Chong Yidong
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3fwimo3z7.fsf@chopper.vpn.verona.se \
--to=joakim@verona.se \
--cc=dave@boostpro.com \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).