Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: ding@gnus.org
Subject: Re: defcustom :version
Date: Sat, 11 Mar 2006 14:57:20 +0100	[thread overview]
Message-ID: <v9k6b1t77j.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <15499.1142047137@olgas.newt.com> (Bill Wohler's message of "Fri,  10 Mar 2006 19:18:57 -0800")

On Sat, Mar 11 2006, Bill Wohler wrote:

> We don't use any :version keywords in the MH-E package at the moment,
> although I'd like to add them. Before doing so, I hope you can help me
> answer a couple of questions about them.
>
> First, how are people using the defcustom :version keyword?

Maybe you already know this but... you don't need to add the keyword
to each variable: You can also add it to the custom group. 

> The big problem I have with them is that it seems we have to use the
> Emacs version. That makes them pretty useless for the MH-E package which
> has turned three *major* releases and a score of minor releases since
> Emacs 21 came out. In the past few years, I would have used 21.4, 21.5,
> 22.0, and 22.1 as the "next" version kept creeping up. How would I have
> documented the variables? [...]
>
> I see the Gnus folks are using the Emacs version in their
> variables. 

Admittedly, many Gnus developers weren't aware of :version, so I added
many of version numbers after Jan D. pointed it out on emacs-devel
after Gnus was updated there.

> How have you folks answered these questions?

Not really an answer to the questions you raised, but this is how I
suggest to handle it in Gnus:

,----[ (info "(gnus-coding)Gnus Maintainance Guide") ]
| For new customizable variables introduced in Oort Gnus (including the
| v5-10 branch) use `:version "22.1" ;; Oort Gnus' including the comment.
| If the variable is new in No Gnus use `:version "23.0" ;; No Gnus'.
`----

> Unless, of course, folks think is reasonable and proper that large
> independent packages that happen to be bundled with Emacs can use their
> versions with the defcustom :version keyword.

This only would make sense if `customize-changed-options' could handle
such "package versions".  Maybe extending the format to allow plists
such as...

  :version '(:emacs 22.1 :mh-e 7.0)
  :version '(:emacs 22.1 :gnus 5.10.2)

("mh-e" / "gnus" could either refer to the package or to a
customization group.  The later might be difficult for Gnus because
not everything included in Gnus is within the `gnus' customization
group)

Limiting `customize-changed-options' to certain custom groups (and
subgroups) would be useful independent of extending :version keyword.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

  parent reply	other threads:[~2006-03-11 13:57 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
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 [this message]
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=v9k6b1t77j.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.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).