all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Checking the Emacs Lisp manual
Date: Wed, 28 Jan 2004 13:57:21 -0500	[thread overview]
Message-ID: <E1AlusL-0008K8-7l@fencepost.gnu.org> (raw)
In-Reply-To: <87wu7d9n35.fsf@tf2.tapsellferrier.co.uk> (message from Nic Ferrier on 27 Jan 2004 20:02:38 +0000)

    Could you tell me a little bit about what sort of checking needs to
    be done? Do you want checks for code functioning correctly, or for
    obvious ommisions or changes in emacs?

That is a good question, so I will send the answer to the list.

The idea is to check the Emacs Lisp Manual, primarily for inaccuracies
(perhaps due to changes in Emacs since the text was updated).  Of
course, I would not mind being informed of other kinds of errors, but
people can spot those without being Emacs experts.  So it makes sense
for Emacs experts to focus on looking for the errors that only Emacs
experts could spot.

Before checking part of the manual, I suggest you refresh your memory
of the changes, by rereading etc/NEWS as far back as Emacs 21.1's
release announcement.

  parent reply	other threads:[~2004-01-28 18:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27 18:50 Checking the Emacs Lisp manual Richard Stallman
     [not found] ` <87wu7d9n35.fsf@tf2.tapsellferrier.co.uk>
2004-01-28 18:57   ` Richard Stallman [this message]
2004-03-08 12:20     ` Nic Ferrier
  -- strict thread matches above, loose matches on Subject: below --
2004-03-12  0:43 Luc Teirlinck
2004-03-13 11:23 ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1AlusL-0008K8-7l@fencepost.gnu.org \
    --to=rms@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.