[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

defcustom :version

From: Bill Wohler
Subject: defcustom :version
Date: Fri, 10 Mar 2006 19:18:57 -0800

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?

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? The numbers would have kept changing, and
would have been for a version that turned into a patch release (21.4) or
were never released (21.5) (apologies if I've rewritten history, but you
get the idea). And what would the user, who is using a released version
of MH-E, supposed to do with a documented version that doesn't exist?

I see the Gnus folks are using the Emacs version in their variables. How
have you folks answered these questions?

It seems that the answer is, "Ignore the versions unless you are using
the package bundled with an Emacs release." I guess I could live with

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.

Bill Wohler <address@hidden>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]