[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#24166: With --eval, errors in string-match-p do not produce backtrac
|
From: |
Eli Zaretskii |
|
Subject: |
bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!) |
|
Date: |
Sat, 06 Aug 2016 13:34:06 +0300 |
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Sat, 6 Aug 2016 06:28:10 -0400
> Cc: Clément Pit--Claudel <clement.pitclaudel@live.com>,
> 24166@debbugs.gnu.org
>
> On Sat, Aug 6, 2016 at 3:25 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > I think Andreas's suggestion to do this in call_debugger is more
> > robust, because it does that for _any_ debugger whose value is placed
> > in the 'debugger' variable, not just for debug.el.
>
> What about all the other variables that debug.el is binding? (I see
> that they both bind inhibit-redisplay to nil)
Sorry, I don't understand how those variables are related to the issue
at hand. What am I missing?
- bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Clément Pit--Claudel, 2016/08/05
- bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), npostavs, 2016/08/05
- bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Clément Pit--Claudel, 2016/08/05
- bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Eli Zaretskii, 2016/08/06
- bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Noam Postavsky, 2016/08/06
- bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!),
Eli Zaretskii <=
- bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Noam Postavsky, 2016/08/06
- bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Eli Zaretskii, 2016/08/06
- bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), npostavs, 2016/08/06
- bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Eli Zaretskii, 2016/08/07
- bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), npostavs, 2016/08/07
- bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Clément Pit--Claudel, 2016/08/07
- Message not available
- Message not available
- bug#23949: acknowledged by developer (Re: bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!)), Kaushal Modi, 2016/08/09