Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
88ab4340
Commit
88ab4340
authored
Dec 25, 2010
by
Eli Zaretskii
Browse files
Fix bug #7667: mention debug-on-quit in the manual.
trouble.texi (Checklist): Mention debug-on-quit.
parent
2e4ab211
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
11 additions
and
0 deletions
+11
-0
doc/emacs/ChangeLog
doc/emacs/ChangeLog
+4
-0
doc/emacs/trouble.texi
doc/emacs/trouble.texi
+7
-0
No files found.
doc/emacs/ChangeLog
View file @
88ab4340
2010-12-25 Eli Zaretskii <eliz@gnu.org>
* trouble.texi (Checklist): Mention debug-on-quit. (Bug#7667)
2010-12-18 Glenn Morris <rgm@gnu.org>
* maintaining.texi: Move inclusion of emerge after EDE, so that it
...
...
doc/emacs/trouble.texi
View file @
88ab4340
...
...
@@ -806,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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment