From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Checking the Emacs Lisp manual
Date: Thu, 11 Mar 2004 18:43:11 -0600 (CST) [thread overview]
Message-ID: <200403120043.i2C0hBR22616@raven.dms.auburn.edu> (raw)
Nic Ferrier wrote:
After some network problems, I'm just at the point where I'm able to
start checking parts of the Emacs Lisp Reference manual.
Is there a list somewhere of what has already been checked? If there
isn't maybe we should add a file to the CVS?
I have read or soon will have read all chapters except:
Customization, Advising Functions, Debugging, Command Loop, Keymaps,
Modes, Documentation, Backups and Auto-Saving, Windows, Frames, Text,
Processes, Display , Calendar and System Interface.
I have also read Text up to and including (elisp)Maintaining Undo.
I have not yet installed my planned changes to "Sequences Arrays Vectors",
"Files" and "Buffers", because there still are outstanding issues.
I am waiting for Richard's comments before installing my proposed
(small) changes to the introduction.
I believe that Richard would like to have at least _double_ coverage
of every section, but due to lack of volunteers, that could be
difficult. Anyway, the fact that I have already read or am reading a
given section should definitely not keep anybody from double checking
it.
Note that I have found it very useful to do C-h f and C-h v on all
described functions and variables. When people make changes, they are
supposed to mention them in the NEWS, but in practice, that does
definitely not always happen and sometimes the only record of a very
non-trivial change is in the docstring or the argument list.
Sincerely,
Luc.
next reply other threads:[~2004-03-12 0:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 0:43 Luc Teirlinck [this message]
2004-03-13 11:23 ` Checking the Emacs Lisp manual Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2004-01-27 18:50 Richard Stallman
[not found] ` <87wu7d9n35.fsf@tf2.tapsellferrier.co.uk>
2004-01-28 18:57 ` Richard Stallman
2004-03-08 12:20 ` Nic Ferrier
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=200403120043.i2C0hBR22616@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--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).