From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Version of the Lisp Manual.
Date: Wed, 08 Jun 2005 21:11:59 +0300 [thread overview]
Message-ID: <u4qc8afbk.fsf@gnu.org> (raw)
In-Reply-To: <87oeagambh.fsf@xs4all.nl> (message from Lute Kamstra on Wed, 08 Jun 2005 17:40:50 +0200)
> Cc: emacs-devel@gnu.org
> From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
> Date: Wed, 08 Jun 2005 17:40:50 +0200
>
> Why not let the edition of the manual equal the version of Emacs?
I think that's because not every version of Emacs automatically causes
a new edition of the manual to be printed by the FSF. Producing a
printed manual for sale in bookstores is a costly process; I think the
FSF only does that from time to time, not when a new Emacs version is
released.
> When you see edition 2.5 of the Lisp manual, that probably doesn't
> tell you much.
It tells me that it is different from an older edition if that older
edition's number is different. The same as when you see a book named
"The Great Foo Bar Book, second edition".
> The first thing you will do is figure out to which Emacs version
> that corresponds.
That's why the title page says:
@titlepage
@sp 6
@center @titlefont{GNU Emacs Manual}
@sp 4
@center @value{EDITION} Edition, Updated for Emacs Version @value{EMACSVER}.
That is, the relevant Emacs version appears right next to the manual's
edition. No need to go hunting for it.
next prev parent reply other threads:[~2005-06-08 18:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 10:49 Version of the Lisp Manual Lute Kamstra
2005-06-08 14:41 ` Eli Zaretskii
2005-06-08 15:40 ` Lute Kamstra
2005-06-08 18:11 ` Eli Zaretskii [this message]
2005-06-09 8:44 ` Lute Kamstra
2005-06-09 19:54 ` Eli Zaretskii
2005-06-09 22:34 ` Lute Kamstra
2005-06-10 6:22 ` Eli Zaretskii
2005-06-10 10:45 ` Lute Kamstra
2005-06-10 22:37 ` Richard Stallman
2005-06-09 14:40 ` 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=u4qc8afbk.fsf@gnu.org \
--to=eliz@gnu.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.
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).