From: Lars Ingebrigtsen <larsi@gnus.org>
To: martin rudalics <rudalics@gmx.at>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 47516@debbugs.gnu.org
Subject: bug#47516: 28.0.50; void-variable edebug-all-defs
Date: Sat, 08 May 2021 14:14:52 +0200 [thread overview]
Message-ID: <87sg2xqv5v.fsf@gnus.org> (raw)
In-Reply-To: <640e3d62-cb4d-b459-3e72-23ff20b0fb16@gmx.at> (martin rudalics's message of "Fri, 2 Apr 2021 20:24:03 +0200")
martin rudalics <rudalics@gmx.at> writes:
> No. But I just read the doc-string of `edebug-all-defs':
>
> edebug-all-defs is a variable defined in ‘edebug.el’.
>
> You can use the command ‘edebug-all-defs’ to toggle the value of this
> variable. You may wish to make it local to each buffer with
> (make-local-variable 'edebug-all-defs) in your
> ‘emacs-lisp-mode-hook’.
>
> and that's what I've apparently done.
>
>> I'm leaning towards considering this a "pilot error".
>
> Objection, your honor!
Skimming this thread, it seems like this is indeed a bug... so is the
right fix here just to reintroduce the autoloads removed by bae2cfe63c?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-05-08 12:14 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
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 [this message]
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=87sg2xqv5v.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47516@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--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).