GNU bug report logs - #24166
With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!)

Previous Next

Full log

Message #26 received at 24166 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Noam Postavsky <npostavs <at> users.sourceforge.net>
Cc: 24166 <at> debbugs.gnu.org, clement.pitclaudel <at> live.com
Subject: Re: bug#24166: With --eval, errors in string-match-p do not produce
 backtraces (but errors in string-match do?!)
Date: Sat, 06 Aug 2016 14:19:50 +0300

> From: Noam Postavsky <npostavs <at> users.sourceforge.net>
> Date: Sat, 6 Aug 2016 06:49:41 -0400
> Cc: Clément Pit--Claudel <clement.pitclaudel <at> live.com>, 
> 	24166 <at> debbugs.gnu.org
> 
> On Sat, Aug 6, 2016 at 6:34 AM, Eli Zaretskii <eliz <at> gnu.org> wrote:
> >> From: Noam Postavsky <npostavs <at> users.sourceforge.net>
> >> Date: Sat, 6 Aug 2016 06:28:10 -0400
> >> Cc: Clément Pit--Claudel <clement.pitclaudel <at> live.com>,
> >>       24166 <at> debbugs.gnu.org
> >>
> >> On Sat, Aug 6, 2016 at 3:25 AM, Eli Zaretskii <eliz <at> 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?
> 
> Not related to this issue as such, but if we want to bind
> inhibit-changing-match-data for all debuggers, why not the others too?

Which ones specifically did you have in mind?  We need to consider
each one carefully, in order to determine whether every debugger needs
that, or just debug.el.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.