From: Alan Mackenzie <acm@muc.de>
To: Stefan Kangas <stefan@marxist.se>
Cc: 37540@debbugs.gnu.org
Subject: bug#37540: [PATCH] Wishlist: Allow edebug-specs to signal arbitrary error strings on syntax errors in macros.
Date: Thu, 16 Jan 2020 20:57:03 +0000 [thread overview]
Message-ID: <20200116205703.GA19757@ACM> (raw)
In-Reply-To: <87h80vwj8v.fsf@marxist.se>
Hello, Stefan.
On Thu, Jan 16, 2020 at 15:47:44 +0100, Stefan Kangas wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
> >> Date: Sat, 28 Sep 2019 12:30:34 +0000
> >> From: Alan Mackenzie <acm@muc.de>
> >> The following patch implements an &error mechanism in edebug.el, and
> >> illustrates its use in the case which motivated it.
> >> Any objections to committing this patch (together with the needed
> >> amendments to documentation and NEWS)?
> > Please wait with such changes until the emacs-27 branch is cut (which
> > should happen soon, I hope). I don't want to risk destabilizing Emacs
> > 27 with potentially risky low-level changes, more than it already is.
> Now that the emacs-27 branch is cut, perhaps it is time to look into
> this again?
Indeed, I posted a post on this bug just on Tuesday. It has not yet
attracted much feedback. I suppose it is a particularly arcane topic,
but such an &error feature would enable me to tidy up the edebug-spec for
backquote properly.
> Best regards,
> Stefan Kangas
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2020-01-16 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-28 12:30 bug#37540: [PATCH] Wishlist: Allow edebug-specs to signal arbitrary error strings on syntax errors in macros Alan Mackenzie
2019-09-28 13:42 ` Eli Zaretskii
2019-09-28 20:34 ` Alan Mackenzie
2019-09-29 6:18 ` Eli Zaretskii
2020-01-16 14:47 ` Stefan Kangas
2020-01-16 20:57 ` Alan Mackenzie [this message]
2020-01-14 20:14 ` bug#37540: Bug 37540: " Alan Mackenzie
2020-01-17 22:01 ` Alan Mackenzie
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=20200116205703.GA19757@ACM \
--to=acm@muc.de \
--cc=37540@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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.