From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: rms@gnu.org, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: defcustom :version
Date: Tue, 14 Mar 2006 19:36:53 -0600 (CST) [thread overview]
Message-ID: <200603150136.k2F1ar101049@raven.dms.auburn.edu> (raw)
In-Reply-To: <12521.1142381164@olgas.newt.com> (message from Bill Wohler on Tue, 14 Mar 2006 16:06:04 -0800)
Bill Wohler wrote:
p.s. Shouldn't customize-changed-options-previous-release be 21.4, not
21.1?
No, it is supposed to be the last _major_ release, which is 21.1.
By the way, the prompt for customize-browse says "(default all
versions)". I don't understand what that means. It tells me, Show all
options that are different from any other version. But this is
essentially *every* option. I think this prompt should read, (default
last version).
Last major release, but this is long and the prompt is already long.
We could just make it (default 21.1), without hardcoding the 21.1,
using the following patch, which I can install if desired.
===File ~/cus-edit-diff=====================================
*** cus-edit.el 03 Mar 2006 11:17:02 -0600 1.287
--- cus-edit.el 14 Mar 2006 18:52:54 -0600
***************
*** 1092,1098 ****
With argument SINCE-VERSION (a string), customize all settings
that were added or redefined since that version."
! (interactive "sCustomize options changed, since version (default all versions): ")
(if (equal since-version "")
(setq since-version nil)
(unless (condition-case nil
--- 1092,1102 ----
With argument SINCE-VERSION (a string), customize all settings
that were added or redefined since that version."
! (interactive
! (list
! (read-from-minibuffer
! (format "Customize options changed, since version (default %s): "
! customize-changed-options-previous-release))))
(if (equal since-version "")
(setq since-version nil)
(unless (condition-case nil
============================================================
next prev parent reply other threads:[~2006-03-15 1:36 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
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 [this message]
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=200603150136.k2F1ar101049@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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.
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).