[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 10:25:08 +0300 |
> From: npostavs@users.sourceforge.net
> Date: Fri, 05 Aug 2016 22:15:09 -0400
> Cc: 24166@debbugs.gnu.org
>
> > Is the following a bug?
>
> Yes, it's another instance of #23949
Indeed.
> Actually, I wonder why the trivial fix suggested there wasn't applied already:
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.
Would you please make that change?
TIA
- 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 <=
- 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?!), 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