From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: fx@gnu.org, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: missing Custom :versions
Date: Sat, 30 Oct 2004 15:57:32 -0500 (CDT) [thread overview]
Message-ID: <200410302057.i9UKvWM03308@raven.dms.auburn.edu> (raw)
In-Reply-To: <20041030183945.IOIU44.mxfep02.bredband.com@coolsville.localdomain> (jan.h.d@swipnet.se)
Jan D. wrote:
Here is a list, it is rather long, 1222 new variables.
I guess that this is a list of all new defcustoms, not a list of new
defcustoms missing a :version keyword.
Note that when looking at this, one has to be careful. From
`(elisp)Group Definitions':
`:version VERSION'
This option specifies that the group was first introduced in
Emacs version VERSION. The value VERSION must be a string.
Tag the group with a version like this when it is introduced,
rather than the individual members (*note Variable Definitions::).
In other words, the defcustoms that are defined during the same
version as their group should not have a :version keyword. The
defgroup should.
This is especially relevant for files that are new in "21.4".
Sincerely,
Luc.
next prev parent reply other threads:[~2004-10-30 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rzqfz3ylqkn.fsf@loveshack>
2004-10-30 3:27 ` missing Custom :versions Richard Stallman
2004-10-30 18:38 ` Jan D.
2004-10-30 20:57 ` Luc Teirlinck [this message]
2004-10-31 15:15 ` Dave Love
2004-10-31 18:56 ` Jan D.
2004-10-31 19:06 ` Luc Teirlinck
2004-10-31 23:21 ` Jan D.
2004-11-01 18:27 ` Reiner Steib
2004-11-01 7:23 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200410302057.i9UKvWM03308@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
--cc=fx@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).