diff options
| author | Glenn Morris | 2021-09-03 08:45:16 -0700 |
|---|---|---|
| committer | Glenn Morris | 2021-09-03 08:45:16 -0700 |
| commit | e1050492d1daa7a4059b99fa0587b80cd781d088 (patch) | |
| tree | aa3ebe9fe413b1e2251979c85ed506e672c147a0 | |
| parent | 0aa0410372dc9dbd251fec0ec71a28e88b9697ec (diff) | |
| download | emacs-e1050492d1daa7a4059b99fa0587b80cd781d088.tar.gz emacs-e1050492d1daa7a4059b99fa0587b80cd781d088.zip | |
* doc/misc/efaq.texi (Reporting bugs): Refer to the Emacs manual.
That is better than having a separate, outdated text.
| -rw-r--r-- | doc/misc/efaq.texi | 27 |
1 files changed, 8 insertions, 19 deletions
diff --git a/doc/misc/efaq.texi b/doc/misc/efaq.texi index c0536e0e3a2..c718e34433f 100644 --- a/doc/misc/efaq.texi +++ b/doc/misc/efaq.texi | |||
| @@ -415,27 +415,16 @@ archive the @code{gnu.*} groups. | |||
| 415 | @cindex How to submit a bug report | 415 | @cindex How to submit a bug report |
| 416 | @cindex Reporting bugs | 416 | @cindex Reporting bugs |
| 417 | 417 | ||
| 418 | The correct way to report Emacs bugs is to use the command | 418 | Please see the Emacs manual for information on how to report bugs. |
| 419 | @kbd{M-x report-emacs-bug}. It sets up a mail buffer with the | 419 | @xref{Checklist, , Checklist for Bug Reports, emacs, The GNU Emacs Manual}. |
| 420 | essential information and the correct e-mail address, | 420 | |
| 421 | @email{bug-gnu-emacs@@gnu.org}. | 421 | It is better to report bugs as described there than to ask on the help |
| 422 | Anything sent there also appears in the | 422 | mailing list. RMS says: |
| 423 | newsgroup @uref{news:gnu.emacs.bug}, but please use e-mail instead of | ||
| 424 | news to submit the bug report. This ensures a reliable return address | ||
| 425 | so you can be contacted for further details. | ||
| 426 | |||
| 427 | Be sure to read the ``Bugs'' section of the Emacs manual before reporting | ||
| 428 | a bug! The manual describes in detail how to submit a useful bug | ||
| 429 | report (@pxref{Bugs, , Reporting Bugs, emacs, The GNU Emacs Manual}). | ||
| 430 | (@xref{Emacs manual}, if you don't know how to read the manual.) | ||
| 431 | |||
| 432 | RMS says: | ||
| 433 | 423 | ||
| 434 | @quotation | 424 | @quotation |
| 435 | Sending bug reports to | 425 | Sending bug reports to |
| 436 | @url{https://lists.gnu.org/mailman/listinfo/help-gnu-emacs, | 426 | @url{https://lists.gnu.org/mailman/listinfo/help-gnu-emacs, |
| 437 | the help-gnu-emacs mailing list} | 427 | the help-gnu-emacs mailing list} is |
| 438 | (which has the effect of posting on @uref{news:gnu.emacs.help}) is | ||
| 439 | undesirable because it takes the time of an unnecessarily large group | 428 | undesirable because it takes the time of an unnecessarily large group |
| 440 | of people, most of whom are just users and have no idea how to fix | 429 | of people, most of whom are just users and have no idea how to fix |
| 441 | these problem. | 430 | these problem. |
| @@ -445,12 +434,12 @@ more likely to know what to do and have expressed a wish to receive | |||
| 445 | more messages about Emacs than the others. | 434 | more messages about Emacs than the others. |
| 446 | @end quotation | 435 | @end quotation |
| 447 | 436 | ||
| 448 | RMS says it is sometimes fine to post to @uref{news:gnu.emacs.help}: | 437 | RMS says it is sometimes fine to post to the help list: |
| 449 | 438 | ||
| 450 | @quotation | 439 | @quotation |
| 451 | If you have reported a bug and you don't hear about a possible fix, | 440 | If you have reported a bug and you don't hear about a possible fix, |
| 452 | then after a suitable delay (such as a week) it is okay to post on | 441 | then after a suitable delay (such as a week) it is okay to post on |
| 453 | @code{gnu.emacs.help} asking if anyone can help you. | 442 | the help list asking if anyone can help you. |
| 454 | @end quotation | 443 | @end quotation |
| 455 | 444 | ||
| 456 | If you are unsure whether you have found a bug, consider the following | 445 | If you are unsure whether you have found a bug, consider the following |