From: Noam Postavsky <npostavs@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Joost Kremers <joostkremers@fastmail.fm>, 40088@debbugs.gnu.org
Subject: bug#40088: 27.0.90; Symbol’s value as variable is void: debugger-outer-match-data
Date: Tue, 17 Mar 2020 07:44:01 -0400 [thread overview]
Message-ID: <874kun6wam.fsf@gmail.com> (raw)
In-Reply-To: <87y2rz94m5.fsf@web.de> (Michael Heerdegen's message of "Tue, 17 Mar 2020 02:01:22 +0100")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Joost Kremers <joostkremers@fastmail.fm> writes:
>
>> *** Eval error *** Symbol’s value as variable is void:
>> debugger-outer-match-data
>
> Another defvar with a missing init value so the variable is not globally
> special? Or is this case intentional for some reason?
It's something more complicated than that I think. There are some extra
errors that get raised during the handling of the initial inciting
error, that somehow ends in inhibit-debugger being left set to t. So
some spec/let-binding is getting snuck out of incorrectly perhaps?
It seems to be ielm specific, but I guess ielm just happens to be doing
something tricky enough to trigger the real bug which lies elsewhere.
As a workaround, you can (setq inhibit-debugger nil) after the first
failure happens.
I can't trigger the debugger-outer-match-data error in Emacs 26, but the
debugger doesn't seem to trigger from ielm at all in that version.
next prev parent reply other threads:[~2020-03-17 11:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 11:40 bug#40088: 27.0.90; Symbol’s value as variable is void: debugger-outer-match-data Joost Kremers
2020-03-17 1:01 ` Michael Heerdegen
2020-03-17 10:41 ` Robert Pluim
2020-03-17 11:06 ` Dmitry Gutov
2020-03-18 0:06 ` Michael Heerdegen
2020-03-18 0:12 ` bug#40088: 27.0.90; Symbol?s " Drew Adams
2020-03-18 1:44 ` Noam Postavsky
2020-03-18 1:49 ` Drew Adams
2020-03-18 22:31 ` Michael Heerdegen
2020-03-18 6:34 ` bug#40088: 27.0.90; Symbol’s " Dmitry Gutov
2020-03-18 22:24 ` Michael Heerdegen
2020-03-18 22:30 ` Dmitry Gutov
2020-03-18 22:46 ` Michael Heerdegen
2020-03-17 11:44 ` Noam Postavsky [this message]
2020-03-19 0:04 ` Noam Postavsky
2020-03-19 0:18 ` Stefan Monnier
2020-03-20 8:37 ` Noam Postavsky
2020-03-20 8:56 ` Eli Zaretskii
2020-03-21 23:47 ` Noam Postavsky
2020-03-22 14:25 ` Eli Zaretskii
2020-03-23 3:17 ` Noam Postavsky
2020-03-23 3:30 ` Eli Zaretskii
2020-03-23 3:40 ` Noam Postavsky
2020-03-23 14:16 ` Eli Zaretskii
2020-03-23 14:34 ` Noam Postavsky
2020-03-23 15:53 ` Joost Kremers
2020-03-20 13:20 ` Stefan Monnier
2020-03-20 14:00 ` Robert Pluim
2020-03-20 14:51 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kun6wam.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=40088@debbugs.gnu.org \
--cc=joostkremers@fastmail.fm \
--cc=michael_heerdegen@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).