diff options
Diffstat (limited to 'doc/emacs/trouble.texi')
| -rw-r--r-- | doc/emacs/trouble.texi | 14 |
1 files changed, 11 insertions, 3 deletions
diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi index e2b27083243..b8cfd322bd4 100644 --- a/doc/emacs/trouble.texi +++ b/doc/emacs/trouble.texi @@ -630,9 +630,10 @@ you can use. All mail sent to the @samp{bug-gnu-emacs} mailing list is also gatewayed to the @samp{gnu.emacs.bug} newsgroup. The reverse is also -true, but we ask you not to post bug reports via the newsgroup. It -can make it much harder to contact you if we need to ask for more -information, and it does not integrate well with the bug tracker. +true, but we ask you not to post bug reports (or replies) via the +newsgroup. It can make it much harder to contact you if we need to ask +for more information, and it does not integrate well with the bug +tracker. If your data is more than 500,000 bytes, please don't include it directly in the bug report; instead, offer to send it on request, or @@ -805,6 +806,13 @@ This use of the debugger is possible only if you know how to make the bug happen again. If you can't make it happen again, at least copy the whole error message. +@vindex debug-on-quit +If Emacs appears to be stuck in an infinite loop or in a very long +operation, typing @kbd{C-g} with the variable @code{debug-on-quit} +non-@code{nil} will start the Lisp debugger and show a backtrace. +This backtrace is useful for debugging such long loops, so if you can +produce it, copy it into the bug report. + @item Check whether any programs you have loaded into the Lisp world, including your @file{.emacs} file, set any variables that may affect the |