From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Philipp Stephani <p.stephani2@gmail.com>, 47516@debbugs.gnu.org
Subject: bug#47516: 28.0.50; void-variable edebug-all-defs
Date: Thu, 01 Apr 2021 02:03:52 +0200 [thread overview]
Message-ID: <87sg4a6fbr.fsf@web.de> (raw)
In-Reply-To: <CAArVCkQVMSHvcRRqAvTy5901bsDD6UoF-71COf6VNe_+-igGYw@mail.gmail.com> (Philipp Stephani's message of "Wed, 31 Mar 2021 13:16:09 +0200")
Stefan,
You removed that autoload cookie in bae2cfe63c:
| * lisp/emacs-lisp/edebug.el (eval-defun): Simplify
|
| (edebug-all-defs, edebug-all-forms): Don't autoload since the problem
| it was working around has been fixed a while back.
Seems that was hasty - or not the only problem these autoload cured?
Philipp Stephani <p.stephani2@gmail.com> writes:
> > For decades I'm used to debug Lisp functions by calling `edebug-defun'.
> > To get rid of the debugging instrumentation I'm using `eval-buffer'. In
> > the not so distant past Emacs started to complain about this habit as
> > follows:
> >
> > Debugger entered--Lisp error: (void-variable edebug-all-defs)
> > edebug-read-and-maybe-wrap-form1()
> > edebug-read-and-maybe-wrap-form()
> > edebug--read(read #<buffer window.el>)
> > apply(edebug--read read #<buffer window.el>)
> > #f(advice-wrapper :around read edebug--read)(#<buffer window.el>)
> > eval-buffer() ; Reading at buffer position 990
> > funcall-interactively(eval-buffer)
> > call-interactively(eval-buffer nil nil)
> > command-execute(eval-buffer)
> >
> > I neither understand the error message nor why I should not be allowed
> > to evaluate the buffer in this situation.
> >
>
> Not sure whether it's related, but there's a comment in edebug.el:
>
> ;; edebug-all-defs and edebug-all-forms need to be autoloaded
> ;; because the byte compiler binds them; as a result, if edebug
> ;; is first loaded for a require in a compilation, they will be left
> unbound.
>
> But despite this explanation these two variables aren't autoloaded.
TIA,
Michael.
next prev parent reply other threads:[~2021-04-01 0:03 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 [this message]
2021-04-02 3:19 ` Stefan Monnier
2021-04-02 6:49 ` martin rudalics
2021-04-02 13:17 ` Stefan Monnier
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=87sg4a6fbr.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=47516@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=p.stephani2@gmail.com \
/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).