From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: More bugs in Custom themes
Date: Mon, 25 Jul 2005 13:53:01 +0200 [thread overview]
Message-ID: <rj4qajumoy.fsf@sheridan.dina.kvl.dk> (raw)
In-Reply-To: <200507250104.j6P14h911761@raven.dms.auburn.edu> (Luc Teirlinck's message of "Sun, 24 Jul 2005 20:04:43 -0500 (CDT)")
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Sorry for the delay in replying to this.
>
> Could you please look at the code and see if the design is clear
> to you?
>
> I have not had the time to study things in detail, but the design is
> certainly clearer than what it used to be. Very non-trivial questions
> remain, like how Custom Themes is going to treat hooks and certain
> list variables. At present, even without Themes, Custom has serious
> problems handling these, as we discussed earlier.
I don't believe it is a good idea trying to make Custom Themes solve
problems that Customize can't solve, such as merging of different
values for options. Treat that as a problem orthogonal to theme
support, even though theme support makes it more urgent.
I.e. if three active themes all add a function to the the same hook
variable, only the function from the dominating theme will actually be
active.
next prev parent reply other threads:[~2005-07-25 11:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 1:52 More bugs in Custom themes Luc Teirlinck
2005-06-30 21:30 ` Richard M. Stallman
2005-07-01 1:04 ` Luc Teirlinck
2005-07-02 12:33 ` Richard M. Stallman
2005-07-02 13:46 ` David Kastrup
2005-07-03 1:55 ` Luc Teirlinck
2005-07-04 6:16 ` Richard M. Stallman
2005-07-03 2:15 ` Luc Teirlinck
2005-07-05 4:35 ` Richard M. Stallman
2005-07-06 2:39 ` Luc Teirlinck
2005-07-06 3:32 ` Luc Teirlinck
2005-07-11 5:34 ` Richard M. Stallman
2005-07-11 5:35 ` Richard M. Stallman
2005-07-25 1:04 ` Luc Teirlinck
2005-07-25 11:53 ` Per Abrahamsen [this message]
2005-07-25 13:10 ` Richard M. Stallman
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=rj4qajumoy.fsf@sheridan.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
--cc=emacs-devel@gnu.org \
--cc=rms@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.