unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: More bugs in Custom themes
Date: Thu, 30 Jun 2005 20:04:53 -0500 (CDT)	[thread overview]
Message-ID: <200507010104.j6114rD07388@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1Do6bp-0001Zh-Ub@fencepost.gnu.org> (rms@gnu.org)

       First new bug.  After requiring a theme and then setting and saving
       some option through Custom, all my customizations for all options for
       which the theme specified a value were deleted.

   Can you fix that?

       Second new bug: `custom-create-theme' can not handle variables with
       a defcustom that needs a :require and there are a lot of those.

   Can you fix that one?

The current code appears to need a complete rewrite, not just fixing
of a few bugs.  This rewrite has to be done carefully, because the
current attempt at implementation has been superimposed on the entire
Custom code.

   No need.  We won't make the release before fixing this up.

   This is an important feature.  We are not going to give up on it.
   We're going to *fix it and make it work*, and then we will make
   the release.

Custom themes would be a completely new complex feature, not a bug
fix: Custom themes did not come remotely close to working in any prior
Emacs version.  I do not suggest giving up on it, but I do suggest
putting it off until after the 22 release.  Custom themes may be
important, but I do not believe that they are important enough to put
off the release of 22 from a possible 2005 date to some very vague and
very distant future.

I know of various remaining problems concerning the manuals and the
code.  These _really_ need fixing and fixing all of them would be less
difficult and less time consuming than coming up with a workable
Custom themes implementation.  If we fix these first, we can make a
release and we may have a shot at still doing that in 2005.  After
that, we could concentrate on Custom themes.

Correctly implementing Custom themes is complex and will be time-consuming.
People have a need for multiple themes with conflicting settings, that can
be individually removed, so we can not make any simplifying assumptions.
The implementation, once ready, will need thorough testing (people writing
and using themes).  It is impossible to guarantee a time table.

Sincerely,

Luc.

  reply	other threads:[~2005-07-01  1:04 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 [this message]
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
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=200507010104.j6114rD07388@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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).