unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stuart D. Herring" <herring@lanl.gov>
Cc: emacs-devel@gnu.org
Subject: Re: "Emacs 21"
Date: Fri, 6 Oct 2006 10:21:55 -0700 (PDT)	[thread overview]
Message-ID: <35344.128.165.123.18.1160155315.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <E1GVimt-0004lw-I9@fencepost.gnu.org>

> Would someone please volunteer to check all uses of "21" in the
> manuals to make sure there is nothing which inappropriately presume
> that is the version number?  Antinews should say it is for version 21,
> but nothing else should.

OK, I've looked at the Lisp Introduction now; it's more complicated.  The
number 21 is used on 75 lines; 54 of these are non-comment references to
the version number (instead of just the integer).  15 of those are
references to the CVS version 21.0.100 (presumably current at the time of
writing), including in example pathnames.  (There are already comments
noting this inclusion.)  Most of the rest are comparisons between 20 (or
19) and 21 in terms of error reporting, mark handling, echo area resizing,
and mode line formats.

A few examples detect the version of Emacs, but do so using string
comparison against `emacs-version' rather than the numeric variables, and
phrase the result in terms of "21" or "not 21", so that's an implication
of currency as well.

So I imagine that the version-detection examples need to be changed
(although I see nothing wrong with determining ">=21" and "<21"), and the
comparisons need to note that they apply to 21 or later.  I'm not sure
what to do with the CVS references.  Any thoughts?  If there's a
consensus, I can do the changes, but I'd like to know what they should be
first.

Davis

-- 
This product is sold by volume, not by mass.  If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.

  parent reply	other threads:[~2006-10-06 17:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06  6:02 "Emacs 21" Richard Stallman
2006-10-06  7:12 ` CHENG Gao
2006-10-06  7:30   ` Romain Francoise
2006-10-06  9:54     ` CHENG Gao
2006-10-06 16:58       ` Romain Francoise
2006-10-06 13:04     ` Andrew M. Scott
2006-10-07  1:07       ` Richard Stallman
2006-10-06 13:17     ` Piet van Oostrum
2006-10-06 16:54 ` Stuart D. Herring
2006-10-06 19:10   ` Reiner Steib
2006-10-07  1:07   ` Richard Stallman
2006-10-06 17:21 ` Stuart D. Herring [this message]
2006-10-06 18:26   ` CHENG Gao
2006-10-06 18:46     ` Romain Francoise
2006-10-06 18:50       ` CHENG Gao
2006-10-06 18:48     ` David Kastrup
2006-10-06 22:16       ` Kim F. Storm
2006-10-07  1:07       ` Richard Stallman
2006-10-07  1:07     ` Richard Stallman
2006-10-07  1:07   ` Richard Stallman
2006-10-10 22:13     ` Stuart D. Herring
2006-10-10 22:34       ` David Kastrup
2006-10-11 18:50       ` Richard Stallman
2006-10-27 22:15         ` Stuart D. Herring
2006-11-04  0:54           ` Kim F. Storm
2006-11-04  3:17             ` Robert J. Chassell
2006-11-08 21:24               ` Stuart D. Herring
2006-11-09 17:13                 ` Robert J. Chassell
2006-11-05  7:07             ` Richard Stallman
2006-10-06 19:48 ` Stuart D. Herring

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=35344.128.165.123.18.1160155315.squirrel@webmail.lanl.gov \
    --to=herring@lanl.gov \
    --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.
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).