From: Stefan Monnier <monnier@iro.umontreal.ca>
To: martin rudalics <rudalics@gmx.at>
Cc: 47516@debbugs.gnu.org
Subject: bug#47516: 28.0.50; void-variable edebug-all-defs
Date: Fri, 02 Apr 2021 09:17:29 -0400 [thread overview]
Message-ID: <jwv4kgo25no.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <08ed7c1c-093b-eed2-8442-3cac05bf6b0a@gmx.at> (martin rudalics's message of "Fri, 2 Apr 2021 08:49:31 +0200")
> Suppose I put point within a function like `window-min-pixel-height' and
> then type C-M-# which here
>
> runs the command edebug-defun (found in edebug-mode-map), which is
> an alias for ‘edebug-eval-top-level-form’ in ‘edebug.el’.
Hmm... this is a bit odd: `edebug-mode-map` is the map used when we're
stepping through execution with Edebug, so are you saying that Edebug
was already in use before this `edebug-defun`?
> insert (window-min-pixel-height) into *scratch* and do C-x e and debug
> that call. When I now type M-# in window.el which here
>
> runs the command eval-buffer (found in edebug-mode-map), which is an
> interactive built-in function in ‘C source code’.
>
> I get
>
> Debugger entered--Lisp error: (void-variable edebug-all-defs)
Hmm... still can't reproduce it here. Can you reproduce it with `emacs -Q`?
Also (stab in the dark), could you check (boundp 'edebug-all-defs) in
a few different buffers?
Stefan
next prev parent reply other threads:[~2021-04-02 13:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 8:10 bug#47516: 28.0.50; void-variable edebug-all-defs martin rudalics
2021-03-31 11:16 ` Philipp Stephani
2021-04-01 0:03 ` Michael Heerdegen
2021-04-02 3:19 ` Stefan Monnier
2021-04-02 6:49 ` martin rudalics
2021-04-02 13:17 ` Stefan Monnier [this message]
2021-04-02 14:15 ` martin rudalics
2021-04-02 15:31 ` Stefan Monnier
2021-04-02 18:24 ` martin rudalics
2021-05-08 12:14 ` Lars Ingebrigtsen
2021-05-08 23:31 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-09 8:41 ` martin rudalics
2021-05-09 9:47 ` Lars Ingebrigtsen
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=jwv4kgo25no.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=47516@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).