[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How can I rethrow an error after recording a backtrace?
From: |
Eli Zaretskii |
Subject: |
Re: How can I rethrow an error after recording a backtrace? |
Date: |
Sat, 06 Aug 2016 13:03:23 +0300 |
> From: Stefan Monnier <address@hidden>
> Date: Fri, 05 Aug 2016 22:11:55 -0400
> Cc: address@hidden
>
> As I said elsewhere, I think this num-* side-condition can be dropped
> because the inhibit-debugger variable should catch the same problems
> but better.
So maybe we should avoid entering the debugger only if _both_
variables say we shouldn't. That would be safer than just tossing
num-nonmacro-input-events.
- Re: How can I rethrow an error after recording a backtrace?, (continued)
- Message not available
- Re: How can I rethrow an error after recording a backtrace?, Eli Zaretskii, 2016/08/05
- Re: How can I rethrow an error after recording a backtrace?, Clément Pit--Claudel, 2016/08/05
- Re: How can I rethrow an error after recording a backtrace?, Eli Zaretskii, 2016/08/06
- Re: How can I rethrow an error after recording a backtrace?, Clément Pit--Claudel, 2016/08/06
- Re: How can I rethrow an error after recording a backtrace?, Eli Zaretskii, 2016/08/06
- Re: How can I rethrow an error after recording a backtrace?, Clément Pit--Claudel, 2016/08/06
- Re: How can I rethrow an error after recording a backtrace?, Eli Zaretskii, 2016/08/06
Re: How can I rethrow an error after recording a backtrace?, Stefan Monnier, 2016/08/05