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: Sat, 2 Jul 2005 21:15:17 -0500 (CDT)	[thread overview]
Message-ID: <200507030215.j632FHG09392@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1DohBq-0006Ob-MB@fencepost.gnu.org> (rms@gnu.org)

Richard Stallman wrote:

   This feature is already in Emacs, it is important, and I will not
   stand for giving up on it.  That is the wrong attitude.

I repeat: I do not suggest giving up on (proper) Themes support.  I
suggest putting it off until after the release.  Are those two equivalent?

   Would you please work on fixing this?

I already fixed six bugs and fixing some of them properly was actually
not as trivial as you suggested.  Four more would be ten.  But it does
not stop there.  As I already said, it makes no sense to fix 1001+
bugs only to create 1001+ others and I will not do that.  I have already
wasted enough time on the nonsense in custom.el.  The Themes code
needs to be rewritten using a proper conflict resolution algorithm and
a proper design.

   You have been doing great so far, whenever you decide to fix
   something rather than say it can't be done.

Just fixing bugs is not doing great if you keep discovering bugs at a
much faster rate than you can solve them and if the lack of design
guarantees the complete impossibility of ever getting the code close to
bugfree (unless it gets a proper design).

It is not very difficult to come up with a good conflict resolution
algorithm (I have outlined one), but it will take time to implement it.

Sincerely,

Luc.

  parent reply	other threads:[~2005-07-03  2:15 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 [this message]
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=200507030215.j632FHG09392@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).