all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <turnbull@sk.tsukuba.ac.jp>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 'Chong Yidong' <cyd@gnu.org>, Drew Adams <drew.adams@oracle.com>,
	emacs-devel@gnu.org
Subject: Re: What version of Emacs still requires '*' in defcustom docs?
Date: Mon, 13 Feb 2012 15:16:13 +0900	[thread overview]
Message-ID: <87ty2vdzrm.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <jwvlio8c7lv.fsf-monnier+emacs@gnu.org>

Stefan Monnier writes:
 > > Why is it important to make such a change?
 > 
 > Because complexity is a problem in itself and as maintainers our main
 > task is to try and keep it in check, so the code doesn't crumble under
 > its own weight.

The problem is that this is complexity for the maintainers, and it's
minor.

Making the change of `defvar ... "*..."' to defcustom is imposing
maintenance costs on 3rd-party package maintainers, and potential
additional complexity (in the custom interface) on users.  The custom
hierarchies for Gnus and VM are awful in my experience.  In reaction,
in some cases I've made a distinction between things that a very few
users might want to change, and defcustoms.

YMMV, but I think if somebody proposes porting this change to XEmacs,
I'll oppose it at least at first.



      parent reply	other threads:[~2012-02-13  6:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-11 22:29 What version of Emacs still requires '*' in defcustom docs? Glenn Morris
2012-02-11 22:49 ` Drew Adams
2012-02-11 22:53 ` Glenn Morris
2012-02-11 23:33   ` Drew Adams
2012-02-12 10:16 ` Chong Yidong
2012-02-12 15:42   ` Drew Adams
2012-02-12 16:58     ` Stefan Monnier
2012-02-12 17:18       ` Drew Adams
2012-02-12 18:17         ` Stefan Monnier
2012-02-13  6:16       ` Stephen J. Turnbull [this message]

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=87ty2vdzrm.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=turnbull@sk.tsukuba.ac.jp \
    --cc=cyd@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.