From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>, 65516@debbugs.gnu.org
Subject: bug#65516: 30.0.50; Edebug behavior of signaling errors in &or
Date: Mon, 28 Aug 2023 00:58:31 +0200 [thread overview]
Message-ID: <878r9w8548.fsf@web.de> (raw)
In-Reply-To: <jwv8r9w8pv7.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 27 Aug 2023 11:32:24 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Hmm... actually, looking at `def-form` again it seems it doesn't use
> `&define` nor `(edebug-)gate`.
Dunno if this helps, I'm understanding it only half, but AFAIU,
`def-form` falls back to `edebug-form' which looks at &define and uses
`edebug-gate' indirectly when calling `edebug-list-form'.
Michael.
next prev parent reply other threads:[~2023-08-27 22:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 6:28 bug#65516: 30.0.50; Edebug behavior of signaling errors in &or Gerd Möllmann
2023-08-26 12:04 ` Gerd Möllmann
2023-08-26 20:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-27 6:26 ` Gerd Möllmann
2023-08-27 15:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-28 5:44 ` Gerd Möllmann
2023-08-28 12:42 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-29 7:07 ` Gerd Möllmann
2023-08-29 15:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-30 5:11 ` Gerd Möllmann
2023-08-27 15:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-27 22:58 ` Michael Heerdegen [this message]
2023-08-28 3:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-28 5:52 ` Gerd Möllmann
2023-08-28 5:44 ` Gerd Möllmann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878r9w8548.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=65516@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.