[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: |
npostavs |
Subject: |
bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!) |
Date: |
Fri, 05 Aug 2016 22:15:09 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.93 (gnu/linux) |
merge 23949 24166
quit
Clément Pit--Claudel <clement.pitclaudel@live.com> writes:
> Hey bug-gnu-emacs,
>
> Is the following a bug?
Yes, it's another instance of #23949
Actually, I wonder why the trivial fix suggested there wasn't applied already:
>From d7c19f35861f12a16e7571340f3f0802a7e85adb Mon Sep 17 00:00:00 2001
From: Noam Postavsky <npostavs@gmail.com>
Date: Fri, 5 Aug 2016 22:11:00 -0400
Subject: [PATCH v1] Fix debugging of string-match-p errors
* lisp/emacs-lisp/debug.el (debug): Bind inhibit-changing-match-data to
nil so that debugger code that needs to do regexp match won't break
(Bug #23949, Bug #24166, Bug#16294).
---
lisp/emacs-lisp/debug.el | 1 +
1 file changed, 1 insertion(+)
diff --git a/lisp/emacs-lisp/debug.el b/lisp/emacs-lisp/debug.el
index 22a3f39..22f86e4 100644
--- a/lisp/emacs-lisp/debug.el
+++ b/lisp/emacs-lisp/debug.el
@@ -177,6 +177,7 @@ debug
(or enable-recursive-minibuffers (> (minibuffer-depth) 0)))
(standard-input t) (standard-output t)
inhibit-redisplay
+ inhibit-changing-match-data
(cursor-in-echo-area nil)
(window-configuration (current-window-configuration)))
(unwind-protect
--
2.8.0
- 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 <=
- 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, 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