Gnus development mailing list
 help / color / mirror / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: defcustom :version
Date: Wed, 29 Mar 2006 21:11:12 -0600 (CST)	[thread overview]
Message-ID: <200603300311.k2U3BCa12687@raven.dms.auburn.edu> (raw)
In-Reply-To: <87zmj8zm7x.fsf@olgas.newt.com> (message from Bill Wohler on Wed,  29 Mar 2006 18:43:14 -0800)

Note that there is a bug in the current implementation of the :version
keyword.  For instance, `M-x customize-changed' lists the group
gnus-agent as new in Emacs 22.1 whereas it was already present in
Emacs 20.7 and possibly earlier.  The problem is that the :version for
`foo' gets stored in the custom-version property of the symbol 'foo.
But `foo' could be two or three of a customizable variable, a custom
group and a face.  All three could have been introduced in different
versions.  One of those could be new in a new release, the others not.
Only that one should be listed by `customize-changed'.  But depending
on luck, either none or all get listed, because only one of the three
:version's winds up being the lucky winner of the "symbol foo
custom-version property contest".

In the case of gnus-agent, the group is not new in 22.1, but the
variable gnus-agent is.

Maybe we should have {option,face,group}-custom-version properties,
maybe after the release.

Sincerely,

Luc.

  reply	other threads:[~2006-03-30  3:11 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 [this message]
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
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=200603300311.k2U3BCa12687@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=ding@gnus.org \
    --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.
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).