From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 50245@debbugs.gnu.org, "Daniel Martín" <mardani29@yahoo.es>
Subject: bug#50245: 28.0.50; Instrumenting a function does not show "Edebug:" in the echo area
Date: Thu, 25 Aug 2022 14:38:13 +0200 [thread overview]
Message-ID: <87v8qgjy6i.fsf@gnus.org> (raw)
In-Reply-To: <jwvh7215bdc.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 24 Aug 2022 22:06:53 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> What makes us think that `edebug-all-defs` will always be defined when
> we get here? Doesn't this code signal an error if called before
> edebug.el is loaded (e.g. in the case of `emacs -Q` soon followed by
> a plain `C-M-x`)?
edebug-all-defs is autoloaded, so it's safe to use here (and the (defvar
isn't needed, so I removed it).
next prev parent reply other threads:[~2022-08-25 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1wno5hxij.fsf.ref@yahoo.es>
2021-08-29 1:04 ` bug#50245: 28.0.50; Instrumenting a function does not show "Edebug:" in the echo area Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-29 19:48 ` Lars Ingebrigtsen
2021-10-02 13:06 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-02 15:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-22 15:39 ` Lars Ingebrigtsen
2022-08-24 22:32 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25 2:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25 12:38 ` Lars Ingebrigtsen [this message]
2022-08-25 13:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25 12:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87v8qgjy6i.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50245@debbugs.gnu.org \
--cc=mardani29@yahoo.es \
--cc=monnier@iro.umontreal.ca \
/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).