From: Philipp Stephani <p.stephani2@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Glenn Morris <rgm@gnu.org>, 48489@debbugs.gnu.org
Subject: bug#48489: 28.0.50; Incorrect Edebug instrumentation for old `when-let' form
Date: Tue, 18 May 2021 18:34:35 +0200 [thread overview]
Message-ID: <CAArVCkQk5=7dYBZFhm5bKo0TNYG0YyV29Hf4Q_mpK15VLicpSA@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkSzmAeid048SHN_ZWQh79OBpsOPKE3R=c3CTkHwG03kxA@mail.gmail.com>
Am Di., 18. Mai 2021 um 18:27 Uhr schrieb Philipp Stephani
<p.stephani2@gmail.com>:
>
> Am Di., 18. Mai 2021 um 18:25 Uhr schrieb Lars Ingebrigtsen <larsi@gnus.org>:
> >
> > Philipp Stephani <p.stephani2@gmail.com> writes:
> >
> > > Hmm, I can't reproduce this on Debian. But I don't see how this could
> > > be OS-dependent.
> >
> > It reproduces fine here on Debian/bullseye, at least:
> >
> > 1 unexpected results:
> > FAILED edebug-tests-duplicate-symbol-backtrack
> >
>
> Yeah, I can also reproduce it now. Not sure what changed in the
> meantime on my system.
Ah. See the FIXME in the test:
;; FIXME: There are twice as many inner
;; definitions as expected due to Bug#42701.
;; Once that bug is fixed, remove the duplicates.
Bug#42701 still isn't fixed, but the fix to bug#48489 has "suppressed"
its symptom in this case. We can therefore resolve this FIXME.
However, then the edebug-tests-duplicate-symbol-backtrack doesn't
really test any more what it should be testing. So I'll see that I can
change it to restore the previous behavior (which requires
backtracking and overlapping &or branches).
next prev parent reply other threads:[~2021-05-18 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 22:08 bug#48489: 28.0.50; Incorrect Edebug instrumentation for old `when-let' form Philipp
2021-05-18 7:29 ` Philipp Stephani
2021-05-18 14:59 ` Glenn Morris
2021-05-18 15:55 ` Philipp Stephani
2021-05-18 16:25 ` Lars Ingebrigtsen
2021-05-18 16:27 ` Philipp Stephani
2021-05-18 16:34 ` Philipp Stephani [this message]
2021-05-18 16:49 ` Philipp Stephani
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='CAArVCkQk5=7dYBZFhm5bKo0TNYG0YyV29Hf4Q_mpK15VLicpSA@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=48489@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rgm@gnu.org \
/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).