unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: 48585@debbugs.gnu.org
Cc: p.stephani2@gmail.com, larsi@gnus.org, monnier@iro.umontreal.ca
Subject: bug#48585: 28.0.50; Missing Edebug instrumentation for some 'if-let' variants
Date: Sun, 17 Jul 2022 02:13:22 +0200	[thread overview]
Message-ID: <877d4ch9zx.fsf@web.de> (raw)
In-Reply-To: <jwvv8rwd7jq.fsf-monnier+emacs@gnu.org> (Stefan Monnier via's message of "Sat, 16 Jul 2022 18:25:55 -0400")

Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:

> As someone who doesn't much like `if-let`, I'll let someone else figure
> out how to that somewhat cleanly.  Also to be honest I also wonder if
> that would be worthwhile.

It's easy to get rid of the `x` occurrence that *binds* (in the
expansion) by changing `internal--build-binding' - the name of the
binding symbol doesn't matter in this case.

Then I guess we could use this `&interpose' Edebug spec but it's
undocumented and not really trivial to understand.  But looks like the
right tool for this case... (?)

Michael.





  reply	other threads:[~2022-07-17  0:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22 11:37 bug#48585: 28.0.50; Missing Edebug instrumentation for some 'if-let' variants Philipp
2022-07-15 10:16 ` Lars Ingebrigtsen
2022-07-16 22:25   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17  0:13     ` Michael Heerdegen [this message]
2022-07-17  1:36       ` Michael Heerdegen
2022-07-17  2:04         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 15:45           ` Michael Heerdegen
2022-07-15 23:15 ` 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

  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=877d4ch9zx.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=48585@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=p.stephani2@gmail.com \
    /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).