From: Richard Stallman <rms@gnu.org>
Cc: wohler@newt.com, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: defcustom :version
Date: Tue, 14 Mar 2006 11:09:53 -0500 [thread overview]
Message-ID: <E1FJC5p-0001Z1-08@fencepost.gnu.org> (raw)
In-Reply-To: <200603140326.k2E3QFs05473@raven.dms.auburn.edu> (message from Luc Teirlinck on Mon, 13 Mar 2006 21:26:16 -0600 (CST))
One could reduce it from 2811 to 2635 and possibly _slightly_ less
because there may be a few cases I overlooked. This requires
eliminating several :version keywords that are _older_ than the
:version in the defgroup, because the defcustom got moved to a new
group.
I don't follow the scenario you describe, but don't bother explaining
it. Reduction down to 2635 lines is not enough reduction to make the
situation much better. We need stronger measures. We need to give
this some structure.
Here's an idea. customize-changed could work like customize-browse,
except that it would show only the groups that cover settings which
have changed meanings.
What do you think?
next prev parent reply other threads:[~2006-03-14 16:09 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 3:18 Bill Wohler
2006-03-11 4:47 ` Luc Teirlinck
2006-03-11 20:40 ` Bill Wohler
2006-03-12 12:47 ` Richard Stallman
2006-03-12 20:30 ` Bill Wohler
2006-03-13 12:55 ` Richard Stallman
2006-03-14 2:58 ` Bill Wohler
2006-03-29 1:45 ` Bill Wohler
2006-03-29 23:02 ` Richard Stallman
2006-03-30 2:43 ` Bill Wohler
2006-03-30 3:11 ` Luc Teirlinck
2006-03-30 17:28 ` Bill Wohler
2006-03-31 17:28 ` Richard Stallman
2006-03-31 18:11 ` Bill Wohler
2006-04-01 13:46 ` Richard Stallman
2006-04-11 0:10 ` Bill Wohler
2006-04-01 14:23 ` Eli Zaretskii
2006-03-31 3:10 ` Richard Stallman
2006-03-30 19:53 ` Wolfram Fenske
2006-03-30 21:18 ` Bill Wohler
2006-04-07 18:44 ` Bill Wohler
2006-04-08 16:17 ` Richard Stallman
2006-04-10 23:49 ` Bill Wohler
2006-03-12 12:47 ` Richard Stallman
2006-03-12 14:54 ` Luc Teirlinck
2006-03-13 1:26 ` Richard Stallman
2006-03-14 3:26 ` Luc Teirlinck
2006-03-14 3:37 ` Luc Teirlinck
2006-03-14 16:09 ` Richard Stallman [this message]
2006-03-14 17:49 ` Bill Wohler
2006-03-15 20:20 ` Richard Stallman
2006-03-15 20:25 ` Bill Wohler
2006-03-14 23:32 ` Luc Teirlinck
2006-03-15 0:06 ` Bill Wohler
2006-03-15 1:36 ` Luc Teirlinck
2006-03-15 2:09 ` Bill Wohler
2006-03-17 16:32 ` Richard Stallman
2006-03-15 20:21 ` Richard Stallman
2006-03-11 5:02 ` Luc Teirlinck
2006-03-11 13:57 ` Reiner Steib
2006-03-11 23:57 ` Bill Wohler
2006-03-11 23:46 ` Richard 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=E1FJC5p-0001Z1-08@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=wohler@newt.com \
/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.
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 NNTP newsgroup(s).