[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] emacs-25 b2ba630: Explain how to debug emacsclient lisp er
From: |
Noam Postavsky |
Subject: |
[Emacs-diffs] emacs-25 b2ba630: Explain how to debug emacsclient lisp errors |
Date: |
Sat, 22 Oct 2016 16:06:49 +0000 (UTC) |
branch: emacs-25
commit b2ba630739cf12db939cdcfe9cd19b6a7fdfbf97
Author: Noam Postavsky <address@hidden>
Commit: Noam Postavsky <address@hidden>
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).
---
doc/lispref/debugging.texi | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index c88a2fa..3719343 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}.)
address@hidden emacsclient, getting a backtrace
address@hidden 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
address@hidden, the backtrace will popup in the running Emacs.
+
@strong{Warning:} Setting this variable to address@hidden 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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] emacs-25 b2ba630: Explain how to debug emacsclient lisp errors,
Noam Postavsky <=