unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: More bugs in Custom themes
Date: Tue, 05 Jul 2005 00:35:30 -0400	[thread overview]
Message-ID: <E1Dpf9e-0004mg-A9@fencepost.gnu.org> (raw)
In-Reply-To: <200507030215.j632FHG09392@raven.dms.auburn.edu> (message from Luc Teirlinck on Sat, 2 Jul 2005 21:15:17 -0500 (CDT))

      The Themes code
    needs to be rewritten using a proper conflict resolution algorithm and
    a proper design.

"A proper design" doesn't identify a specific problem I could address,
but I think we already discussed the proper conflict resolution
method.  What I suggested was that the themes are listed in an order,
and later themes override earlier themes.  Disabling any of the themes
works by getting rid of all of them, then reloading the ones that
remain enabled.  You've already got the function which turns them all
off.

If you think it would be hard to write this, could you tell me which
functions deal with this part of things?  Then I will try.

  reply	other threads:[~2005-07-05  4:35 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 [this message]
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
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

  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=E1Dpf9e-0004mg-A9@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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).