view BUGS @ 86328:6276fcac4dc8

(spam-find-spam, spam-enter-list): Doc fixes. (spam-split-symbolic-return-positive): Reflow docstring. (spam-backends, spam-summary-exit-behavior, spam-mark-ham-unread-before-move-from-spam-group, spam-summary-score-preferred-header, spam-sa-learn-spam-switch, spam-sa-learn-ham-switch, spam-sa-learn-unregister-switch, spam-clear-cache, spam-backend-check, spam-install-backend, spam-install-statistical-backend, spam-list-of-processors, spam-group-processor-p, spam-split, spam-bogofilter-score, spam-bsfilter-score, spam-check-bsfilter, spam-crm114-score, spam-check-crm114, spam-initialize, spam-unload-hook): Fix typos in docstrings.
author Juanma Barranquero <lekktu@gmail.com>
date Thu, 22 Nov 2007 16:10:00 +0000
parents 8ce686bd7f4f
children fb8bf24d2eb9
line wrap: on
line source

If you think you may have found a bug in GNU Emacs, please
read the Bugs section of the Emacs manual for advice on
(1) how to tell when to report a bug, and
(2) how to write a useful bug report and what information
it needs to have.

There are three ways to read the Bugs section.

(1) In a printed copy of the Emacs manual.
You can order one from the Free Software Foundation;
see the file etc/ORDERS.  But if you don't have a copy on
hand and you think you have found a bug, you shouldn't wait
to get a printed manual; you should read the section right away
as described below.

(2) With Info.  Start Emacs, do C-h i to enter Info,
then m Emacs RET to get to the Emacs manual, then m Bugs RET
to get to the section on bugs.  Or use standalone Info in
a like manner.  (Standalone Info is part of the Texinfo distribution,
not part of the Emacs distribution.)

(3) By hand.  Do
    cat info/emacs* | more "+/^File: emacs,  Node: Bugs,"

Please first check the file etc/PROBLEMS (e.g. with C-h C-e in Emacs) to
make sure it isn't a known issue.