From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Cc: emacs-devel@gnu.org
Subject: Re: Version of the Lisp Manual.
Date: Fri, 10 Jun 2005 12:45:07 +0200 [thread overview]
Message-ID: <8764wmv6bw.fsf@xs4all.nl> (raw)
In-Reply-To: <umzpy91ec.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Jun 2005 09:22:35 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
>> Date: Fri, 10 Jun 2005 00:34:34 +0200
>> Cc: emacs-devel@gnu.org
>>
>> > As long as the manual is not printed, who would see the edition
>> > number?
>>
>> C-h i m elisp RET shows me:
>>
>> This Info file contains edition 2.9 of the GNU Emacs Lisp Reference
>> Manual, corresponding to GNU Emacs version 22.1.
>
> I know that. I don't expect anyone to pay attention to this line,
> though.
Well, it's the first thing you see when you read the manual in info.
I think people will read it.
> And if we think it could confuse, we could remove the edition from
> this sentence.
I'm in favor of that. What about the patch below?
Lute.
Index: lispref/elisp.texi
===================================================================
RCS file: /cvsroot/emacs/emacs/lispref/elisp.texi,v
retrieving revision 1.57
diff -c -r1.57 elisp.texi
*** lispref/elisp.texi 10 Jun 2005 10:03:29 -0000 1.57
--- lispref/elisp.texi 10 Jun 2005 10:42:29 -0000
***************
*** 94,101 ****
@node Top, Introduction, (dir), (dir)
@top Emacs Lisp
! This Info file contains edition @value{VERSION} of the GNU Emacs Lisp
! Reference Manual, corresponding to GNU Emacs version @value{EMACSVER}.
@end ifnottex
@menu
--- 94,101 ----
@node Top, Introduction, (dir), (dir)
@top Emacs Lisp
! This Info file contains the GNU Emacs Lisp Reference Manual
! corresponding to GNU Emacs version @value{EMACSVER}.
@end ifnottex
@menu
Index: lispref/intro.texi
===================================================================
RCS file: /cvsroot/emacs/emacs/lispref/intro.texi,v
retrieving revision 1.29
diff -c -r1.29 intro.texi
*** lispref/intro.texi 10 Jun 2005 10:05:22 -0000 1.29
--- lispref/intro.texi 10 Jun 2005 10:42:29 -0000
***************
*** 35,42 ****
--- 35,48 ----
chapters describe features that are peculiar to Emacs Lisp or relate
specifically to editing.
+ @iftex
This is edition @value{VERSION} of the GNU Emacs Lisp Reference
Manual, corresponding to Emacs version @value{EMACSVER}.
+ @end iftex
+ @ifnottex
+ This is the GNU Emacs Lisp Reference Manual corresponding to Emacs
+ version @value{EMACSVER}.
+ @end ifnottex
@menu
* Caveats:: Flaws and a request for help.
next prev parent reply other threads:[~2005-06-10 10:45 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
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 [this message]
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=8764wmv6bw.fsf@xs4all.nl \
--to=lute.kamstra.lists@xs4all.nl \
--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).