From: "Mattias Engdegård" <mattiase@acm.org>
To: 50738@debbugs.gnu.org
Subject: bug#50738: `ert-deftest` bodies should not use lexical-binding=nil
Date: Wed, 22 Sep 2021 16:26:46 +0200 [thread overview]
Message-ID: <77669ED1-89A0-4E01-9382-7D77EFAE5C3F@acm.org> (raw)
In-Reply-To: <8620C815-C0FC-4C81-A1A0-1F0AFBD603AD@acm.org>
> 1. Make with-temp-buffer use the current value of lexical-binding for the temporary buffer, instead of always using nil.
This causes three tests to fail, of which two just lazy test assumptions (fixed in 6ad77d36fd3f) and the third was the anonymous &rest case which is a real bug that was previously hidden.
next prev parent reply other threads:[~2021-09-22 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 11:13 bug#50738: `ert-deftest` bodies should not use lexical-binding=nil Mattias Engdegård
2021-09-22 14:26 ` Mattias Engdegård [this message]
2021-09-22 20:33 ` Lars Ingebrigtsen
2021-09-23 5:50 ` Eli Zaretskii
2021-09-25 18:33 ` Mattias Engdegård
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=77669ED1-89A0-4E01-9382-7D77EFAE5C3F@acm.org \
--to=mattiase@acm.org \
--cc=50738@debbugs.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).