Go to the first, previous, next, last section, table of contents.

Reporting Bugs

Mailing Lists and USENET Newsgroup

There are two mailing lists and one USENET newsgroup for discussing GNUS related topics. These are intended for exchanging useful information about GNUS, such as bug reports, useful hooks, and extensions of GNUS. If you have any questions or problems, feel free to ask about them. Suggestions are also welcome.

This is a USENET newsgroup under the gnu.all hierarchy which is concerned with the GNU Project of the Free Software Foundation.
This is an Internet mailing list which is gated bi-directionally with the gnu.emacs.gnus newsgroup. English is the official language of the list. Please send subscription requests to:
This is a JUNET mailing list. Messages of info-gnus-english and gnu.emacs.gnus are forwarded to this list. English and Japanese are the official languages of the list. Please send subscription requests to:

The major difference between info-gnus-english/gnu.emacs.gnus and info-gnus is the official language. There is no need to subscribe to info-gnus if you cannot read messages written in Japanese since most discussions and important announcements will be sent to info-gnus-english.

How to Report a Bug

If you find a bug, it is important to report it and to report it in a way which is useful. If it is a bug of a lisp program, what is the most useful is an exact backtrace information of the lisp program with the version number of GNUS that you are using.

To make the backtrace information, you must set the Emacs variable debug-on-error to t before the error happens. A backtrace obtained from a byte-compiled lisp program is not usually understandable. To make a human readable backtrace, load the source program which is not byte-compiled yet and then produce the error.

See Info file `emacs', node `Bugs', for more information.

Go to the first, previous, next, last section, table of contents.