From 81ce4b0e4ee18520f174cc5b46219e4475fcc956 Mon Sep 17 00:00:00 2001 From: Lars Ingebrigtsen Date: Sun, 1 May 2022 13:07:14 +0200 Subject: [PATCH] Correct Using Debugger lispref node * doc/lispref/debugging.texi (Using Debugger): Make documentation reflect reality (bug#36145). --- doc/lispref/debugging.texi | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi index 469ff2d943d..c258a9adc0e 100644 --- a/doc/lispref/debugging.texi +++ b/doc/lispref/debugging.texi @@ -387,11 +387,9 @@ possibilities.) variable is temporarily set according to @code{eval-expression-debug-on-error}. If the latter variable is non-@code{nil}, @code{debug-on-error} will temporarily be set to -@code{t}. This means that any further errors that occur while doing a -debugging session will (by default) trigger another backtrace. If -this is not what you want, you can either set -@code{eval-expression-debug-on-error} to @code{nil}, or set -@code{debug-on-error} to @code{nil} in @code{debugger-mode-hook}. +@code{t}. However, further errors that occur while debugging won't +(by default) trigger another debugger, because @code{inhibit-debugger} +will also be bound to non-@code{nil}. The debugger itself must be run byte-compiled, since it makes assumptions about the state of the Lisp interpreter. These -- 2.39.2