From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Greg Minshall <minshall@umich.edu>,
Michael Heerdegen <michael_heerdegen@web.de>,
66867@debbugs.gnu.org
Subject: bug#66867: lexical binding?
Date: Thu, 02 Nov 2023 15:35:10 -0400 [thread overview]
Message-ID: <jwvlebgeyqb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkmm94k-kgNo-M73z6KB=ZCUDUk=u-rtJf6Ha+UVsdpwutA@mail.gmail.com> (Stefan Kangas's message of "Thu, 2 Nov 2023 12:21:37 -0700")
>> maybe the Oclosure code should enforce lexical-binding, if it can, or
>> throw an informative error in the case it can't so enforce?
> Stefan M, what do you think?
A (cl-assert lexical-binding) in something like `oclosure--lambda`
sounds good, yes.
Stefan
next prev parent reply other threads:[~2023-11-02 19:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 2:34 bug#66867: 30.0.50; oclosure problem Greg Minshall
2023-11-01 5:16 ` bug#66867: lexical binding? Greg Minshall
2023-11-02 1:15 ` Michael Heerdegen
2023-11-02 17:41 ` Greg Minshall
2023-11-02 19:21 ` Stefan Kangas
2023-11-02 19:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-11-02 19:39 ` Stefan Kangas
2023-11-02 21:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-02 22:11 ` Stefan Kangas
2023-11-03 3:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-03 17:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04 0:29 ` Stefan Kangas
[not found] ` <handler.66867.D66867.169903440116577.notifdone@debbugs.gnu.org>
2023-11-06 19:25 ` bug#66867: closed (Re: bug#66867: lexical binding?) Greg Minshall
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=jwvlebgeyqb.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=66867@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=minshall@umich.edu \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@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).