view BUGS @ 60356:3f394ef46f57

Revision: [e-mail]--gnu-2005/emacs--cvs-trunk--0--patch-151 Merge from gnus--rel--5.10 Patches applied: * [e-mail]--gnu-2005/gnus--rel--5.10 (patch 34-35) - Merge from emacs--cvs-trunk--0 - Update from CVS 2005-03-03 Reiner Steib <[e-mail]> * lisp/gnus/message.el (message-get-reply-headers, message-followup): Mention related variables `message-use-followup-to' and `message-use-mail-followup-to', in the information buffer. * lisp/gnus/nnweb.el (nnweb-type-definition): Use groups.google.de instead of broken groups(-beta).google.com. 2005-03-03 Reiner Steib <[e-mail]> * man/gnus.texi (Slow/Expensive Connection): Don't abbreviate "very".

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.