[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 17:30:30 +0200 |
Alan Mackenzie <acm@muc.de> writes:
> I mean something like the following, which to a first approximation,
> works. To use it, do M-x debug-next-command and the execute the command
> expected to give errors:
Good idea, but how about just making it into a manual toggle? I might
need to run more than one command to reproduce a bug.
- 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?,
Stefan Kangas <=
- 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