Customization Appendices A Programmers Guide to Gnus
Gnus works so well straight out of the box---I can't imagine any problems, really.
Gnus v5.46; nntp 4.0' you have the right files loaded. If, on the other hand, you get something like `
NNTP 3.x' or `
nntp flee', you have some old `
.el' files lying around. Delete these.
max-lisp-eval-depthto 500 or something like that.
If all else fails, report the problem as a bug.
If you find a bug in Gnus, you can report it with the M-x gnus-bug command. M-x set-variable RET debug-on-error RET t RET, and send me the backtrace. I will fix bugs, but I can only fix them if you send me a precise description as to how to reproduce the bug.
You really can never be too detailed in a bug report. Always use the M-x gnus-bug command when you make bug reports, even if it creates a 10Kb mail each time you use it, and even if you have sent me your environment 500 times before. I don't care. I want the full info each time.
It is also important to remember that I have no memory whatsoever. If you send a bug report, and I send you a reply, and then you just send back ``No, it's not! Moron!'', I will have no idea what you are insulting me about. Always over-explain everything. It's much easier for all of us---if I don't have all the information I need, I will just mail you and ask for more info, and everything takes more time.
If the problem you're seeing is very visual, and you can't quite explain
it, copy the Emacs window to a file (with
xwd, for instance), put
it somewhere it can be reached, and include the URL of the picture in
the bug report.
If you just need help, you are better off asking on
gnu.emacs.gnus'. I'm not very helpful.
You can also ask on the ding mailing list---`
Write to `
email@example.com' to subscribe.