From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: Proof-reading manuals (was Re: Rmail mbox-format branch)
Date: Thu, 16 Sep 2004 07:19:06 -0400 [thread overview]
Message-ID: <E1C7uI6-0000TT-9V@fencepost.gnu.org> (raw)
In-Reply-To: <200409150112.i8F1CnL22210@raven.dms.auburn.edu> (message from Luc Teirlinck on Tue, 14 Sep 2004 20:12:49 -0500 (CDT))
For lispref this way of organizing things may be reasonable, but for
man it makes no sense. It might be nice to have things like
man/cl.texi updated, but such things are a luxury right now. What we
worry about now is the Emacs and Elisp manual and info.texi.
I agree. Could you remove the other files from the `man' list, keeping
only info.texi and those that are part of the Emacs manual?
Also, remove gfdl.texi and gpl.texi if they are included.
I proofread all of the Elisp manual except the chapters (if you do
`C-h i elisp'):
Advising Functions
Debugging
Customization
Modes
Text
Processes
Display
Calendar
Nearly all the work that has been done, has been done by you,
and you are doing a very good job of it.
I am pretty sure there has been little change in the advice system.
If you could read the others of those sections, it would be very
useful.
I did also not check or update:
Antinews
GNU Free Documentation License
GPL
Standard Buffer-Local Variables
Standard Keymaps
Standard Hooks
New Symbols
The file lispref/anti.texi is for the Emacs 20 to 21 transition.
This file needs to be rewritten from zero, based on what's in
etc/NEWS since 21.1.
There is no need to review the GFDL and GPL sections.
Checking those four appendixes only needs to be done once,
if someone can do them in a careful way.
next prev parent reply other threads:[~2004-09-16 11:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 4:02 Rmail mbox-format branch Richard Stallman
2004-09-09 14:13 ` Stefan
2004-09-09 14:44 ` Paul Michael Reilly
2004-09-09 15:25 ` Stefan
2004-09-09 18:56 ` Eli Zaretskii
2004-09-09 22:19 ` Miles Bader
2004-09-10 7:36 ` Kim F. Storm
2004-09-10 9:18 ` Eli Zaretskii
2004-09-10 9:38 ` Miles Bader
2004-09-10 10:41 ` Kim F. Storm
2004-09-10 11:44 ` Eli Zaretskii
2004-09-10 11:36 ` Eli Zaretskii
2004-09-10 10:39 ` Kim F. Storm
2004-09-10 11:42 ` Eli Zaretskii
2004-09-10 12:38 ` Kim F. Storm
2004-09-10 16:17 ` Eli Zaretskii
2004-09-11 23:19 ` Kim F. Storm
2004-09-11 10:52 ` Richard Stallman
2004-09-11 11:17 ` Eli Zaretskii
2004-09-11 16:45 ` Kim F. Storm
2004-09-11 2:49 ` Luc Teirlinck
2004-09-11 18:46 ` Proof-reading manuals (was Re: Rmail mbox-format branch) Kim F. Storm
2004-09-15 1:12 ` Luc Teirlinck
2004-09-16 11:19 ` Richard Stallman [this message]
2004-09-18 22:06 ` Luc Teirlinck
2004-09-19 11:00 ` Richard Stallman
2004-09-19 16:29 ` Proof-reading manuals Kim F. Storm
2004-09-11 10:50 ` Rmail mbox-format branch Richard Stallman
2004-09-11 11:22 ` Eli Zaretskii
2004-09-11 16:57 ` Stefan
2004-09-13 6:59 ` Richard Stallman
2004-09-15 10:25 ` Thien-Thi Nguyen
2004-09-11 13:50 ` Robert J. Chassell
2004-09-13 23:04 ` Richard Stallman
2004-09-10 17:41 ` Richard Stallman
2004-09-10 20:27 ` Alex Schroeder
2004-09-12 9:09 ` 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=E1C7uI6-0000TT-9V@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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).