[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Attaching context info to an error
From: |
Stefan Monnier |
Subject: |
Re: Attaching context info to an error |
Date: |
Tue, 26 Dec 2023 15:12:28 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
> Just to be clear what I meant by this to those unfamiliar with
> Common Lisp and interactive restarts. It means I can invoke
> the restart interactively from the Common Lisp debugger that
> is invoked as the last step of the non-returning error.
>
> 'baz' will be called again and again with different arguments
> and always errors until I recompile it to something else that
> doesn't error, which I can do while the debugger is active.
>
> I expected to be able to do the same from the Emacs Lisp
> debugger-mode/backtrace-mode *Backtrace* buffer, but I never
> get one such buffer.
FWIW, it works for me (with an Emacs compiled from the
`scratch/handler-bind` branch).
when I do `C-x C-e` at the end of `(foo)`, I get into the debugger, and
I do
M-: (funcall (nth 2 (car pm/restarts))) RET
I get back into the debugger but with a different gensymd symbol.
And if I redefine `baz` to something that doesn't signal an error,
M-: (funcall (nth 2 (car pm/restarts))) RET
then lets me return to the toplevel.
Stefan
- Attaching context info to an error, Stefan Monnier, 2023/12/21
- Re: Attaching context info to an error, Gerd Möllmann, 2023/12/22
- Re: Attaching context info to an error, Jens Schmidt, 2023/12/22
- Re: Attaching context info to an error, João Távora, 2023/12/22
- Re: Attaching context info to an error, Stefan Monnier, 2023/12/27
- Re: Attaching context info to an error, João Távora, 2023/12/27
- Re: Attaching context info to an error, João Távora, 2023/12/27
- Re: Attaching context info to an error, Stefan Monnier, 2023/12/27
- Re: Attaching context info to an error, João Távora, 2023/12/27