summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNoam Postavsky <npostavs@gmail.com>2016-10-22 11:52:14 -0400
committerNoam Postavsky <npostavs@gmail.com>2016-10-22 12:06:29 -0400
commitb2ba630739cf12db939cdcfe9cd19b6a7fdfbf97 (patch)
tree47a1e3b6e3f03c77eb72ccb2effe48085c908913
parent9da53e2d353c97ab955fe8c35482b5eb335316c1 (diff)
downloademacs-b2ba630739cf12db939cdcfe9cd19b6a7fdfbf97.tar.gz
Explain how to debug emacsclient lisp errors
* doc/lispref/debugging.texi (Error Debugging): Mention that debug-on-signal is useful for getting backtraces from emacsclient (Bug#24616).
-rw-r--r--doc/lispref/debugging.texi7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index c88a2fa60e0..371934377a8 100644
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -152,6 +152,13 @@ presence of @code{condition-case}. (To invoke the debugger, the error
must still fulfill the criteria specified by @code{debug-on-error} and
@code{debug-ignored-errors}.)
+@cindex emacsclient, getting a backtrace
+@cindex backtrace from emacsclient's @option{--eval}
+For example, setting this variable is useful to get a backtrace from
+code evaluated by emacsclient's @option{--eval} option. If Lisp code
+evaluated by emacsclient signals an error while this variable is
+non-@code{nil}, the backtrace will popup in the running Emacs.
+
@strong{Warning:} Setting this variable to non-@code{nil} may have
annoying effects. Various parts of Emacs catch errors in the normal
course of affairs, and you may not even realize that errors happen