[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why is it so difficult to get a Lisp backtrace?
From: |
Stefan Kangas |
Subject: |
Re: Why is it so difficult to get a Lisp backtrace? |
Date: |
Sat, 25 Jun 2022 18:27:40 +0200 |
Alan Mackenzie <acm@muc.de> writes:
> One idea I had was to have an optional numerical argument, saying how
> many commands to leave the thing in place for. Yet another, conflicting,
> idea would be to have an optional boolean argument to exclude
> debug-on-signal from the mix, so as not to get too many "expected"
> backtraces.
In my personal use, I'd probably put this behind a timer so that it is
disabled again automatically after 30 seconds (or something). I do
that for `menu-bar-mode', for example, since I also only ever enable
that temporarily for testing. But that might be too hacky for general
use.
- Why is it so difficult to get a Lisp backtrace?, Alan Mackenzie, 2022/06/25
- Re: Why is it so difficult to get a Lisp backtrace?, Alan Mackenzie, 2022/06/25
- Re: Why is it so difficult to get a Lisp backtrace?, Lars Ingebrigtsen, 2022/06/25
- Re: Why is it so difficult to get a Lisp backtrace?, Alan Mackenzie, 2022/06/25
- Re: Why is it so difficult to get a Lisp backtrace?, Eli Zaretskii, 2022/06/25
- Re: Why is it so difficult to get a Lisp backtrace?, Alan Mackenzie, 2022/06/25
- Re: Why is it so difficult to get a Lisp backtrace?, Eli Zaretskii, 2022/06/26
- Fontification error backtrace [Was: Why is it so difficult to get a Lisp backtrace?], Alan Mackenzie, 2022/06/27
- Re: Fontification error backtrace [Was: Why is it so difficult to get a Lisp backtrace?], Lars Ingebrigtsen, 2022/06/28
- Re: Fontification error backtrace [Was: Why is it so difficult to get a Lisp backtrace?], Eli Zaretskii, 2022/06/28
- Re: Fontification error backtrace [Was: Why is it so difficult to get a Lisp backtrace?], Alan Mackenzie, 2022/06/28
- Re: Fontification error backtrace [Was: Why is it so difficult to get a Lisp backtrace?], Eli Zaretskii, 2022/06/28