GNU bug report logs - #36145
26.2; Unable to "trigger another backtrace"

Previous Next

Package: emacs;

Reported by: Xu Chunyang <mail <at> xuchunyang.me>

Date: Sun, 9 Jun 2019 07:19:02 UTC

Severity: minor

Found in version 26.2

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log

Message #33 received at 36145 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Xu Chunyang <mail <at> xuchunyang.me>
Cc: 36145 <at> debbugs.gnu.org
Subject: Re: bug#36145: 26.2; Unable to "trigger another backtrace"
Date: Sun, 01 May 2022 13:07:38 +0200

Xu Chunyang <mail <at> 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
This bug report was last modified 3 years and 77 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.