mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-09 07:40:39 -08:00
Improve documentation of signaling errors in batch mode
* doc/lispref/control.texi (Signaling Errors) (Processing of Errors): * doc/lispref/os.texi (Batch Mode): * doc/lispref/debugging.texi (Invoking the Debugger): * lisp/emacs-lisp/debug.el (debug): * src/eval.c (Fsignal): * lisp/subr.el (error): Document more prominently that signaling an unhandled error in batch mode kills Emacs. Better documentation of backtrace in batch mode.
This commit is contained in:
parent
103ca678ac
commit
fe000236cf
6 changed files with 78 additions and 23 deletions
|
|
@ -158,6 +158,13 @@ where CAUSE can be:
|
|||
;;;###autoload
|
||||
(defun debug (&rest args)
|
||||
"Enter debugger. \\<debugger-mode-map>`\\[debugger-continue]' returns from the debugger.
|
||||
|
||||
In interactive sessions, this switches to a backtrace buffer and shows
|
||||
the Lisp backtrace of function calls there. In batch mode (more accurately,
|
||||
when `noninteractive' is non-nil), it shows the Lisp backtrace on the
|
||||
standard error stream (unless `backtrace-on-error-noninteractive' is nil),
|
||||
and then kills Emacs, causing it to exit with a negative exit code.
|
||||
|
||||
Arguments are mainly for use when this is called from the internals
|
||||
of the evaluator.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue