GNU bug report logs - #78381
30.1.50; Show a stack trace if an error occurs in safe hooks

Previous Next

Package: emacs;

Reported by: Daniel Mendler <mail <at> daniel-mendler.de>

Date: Sun, 11 May 2025 19:32:02 UTC

Severity: normal

Found in version 30.1.50

To reply to this bug, email your comments to 78381 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#78381; Package emacs. (Sun, 11 May 2025 19:32:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Daniel Mendler <mail <at> daniel-mendler.de>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Sun, 11 May 2025 19:32:02 GMT) Full text and rfc822 format available.

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

From: Daniel Mendler <mail <at> daniel-mendler.de>
To: bug-gnu-emacs <at> gnu.org
Subject: 30.1.50; Show a stack trace if an error occurs in safe hooks
Date: Sun, 11 May 2025 21:30:38 +0200

Hello!

This is a feature request to improve the situation around debugging safe
hooks. Right now if an error occurs in a safe hook occurs, only a brief
message is shown (safe_run_hooks_error in keyboard.c, "Error in %s (%S):
%S"). Would it be possible to dump a stack trace to the *Messages*
buffer? The problem is likely to avoid flooding the *Messages* buffer.
On the other hand, hooks which throw errors are disabled anyway?

Thank you!

Daniel
This bug report was last modified 4 days ago.

Previous Next

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