[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#36145: 26.2; Unable to "trigger another backtrace"
From: |
Lars Ingebrigtsen |
Subject: |
bug#36145: 26.2; Unable to "trigger another backtrace" |
Date: |
Sun, 01 May 2022 13:07:38 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Xu Chunyang <mail@xuchunyang.me> writes:
>> temporarily set according to ‘eval-expression-debug-on-error’. If the
>> latter variable is non-‘nil’, ‘debug-on-error’ will temporarily be set
>> to ‘t’. This means that any further errors that occur while doing a
>> debugging session will (by default) trigger another backtrace.
>
> Text before "This means.." is correct, but the conclusion seems
> incorrect, to reproduce
>
> - emacs -Q
> - M-: (/ 1 0) ;; enter the debugger
> - M-: (/ 2 0) ;; just message the error, no another backtrace
I've now fixed the documentation here in Emacs 29.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
- bug#36145: 26.2; Unable to "trigger another backtrace",
Lars Ingebrigtsen <=