From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 65620@debbugs.gnu.org
Subject: bug#65620: void function edebug-after
Date: Fri, 1 Sep 2023 14:27:42 +0200 [thread overview]
Message-ID: <f9e1bdd9-c5b0-e58f-ce63-8c4bd3830333@gmail.com> (raw)
In-Reply-To: <ZPGtl74FoH5RMsXH@ACM>
On 01.09.23 11:23, Alan Mackenzie wrote:
> I think a better way of handling this would be to have a "base function"
> for edebug-after (and for edebug-before), as opposed to the nil that each
> of these currently has. These functions would throw an error asking the
> user to check the edebug spec. Something like (untested):
>
> (defun edebug-after (before-index after-index form)
> "Version of `edebug-after' to call when edebug is not yet set up.
> This function gets temporarily replaced by a real function when
> edebug becomes active."
> (error "Invalid call to `edebug-after' for %S: Is your debug spec \
> correct?" form))
>
> .. What do you think?
I find that an excellent idea! The error "void function edebug-after"
might indeed be considered a bit unhelpful by some :-). Haven't tested
anything either, though...
next prev parent reply other threads:[~2023-09-01 12:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 12:57 bug#65620: void function edebug-after Alan Mackenzie
2023-08-30 23:09 ` Michael Heerdegen
2023-08-31 7:55 ` Gerd Möllmann
2023-08-31 8:02 ` Gerd Möllmann
2023-08-31 13:50 ` Alan Mackenzie
2023-08-31 14:41 ` Gerd Möllmann
2023-09-01 9:23 ` Alan Mackenzie
2023-09-01 12:27 ` Gerd Möllmann [this message]
2023-09-01 21:27 ` Alan Mackenzie
2023-09-02 4:27 ` Gerd Möllmann
2023-09-02 13:10 ` Alan Mackenzie
2023-09-02 13:15 ` Gerd Möllmann
2023-09-02 13:57 ` Alan Mackenzie
2023-09-03 4:29 ` Michael Heerdegen
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=f9e1bdd9-c5b0-e58f-ce63-8c4bd3830333@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=65620@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=michael_heerdegen@web.de \
/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.