From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: luangruo@yahoo.com, monnier@iro.umontreal.ca,
66636@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#66636: Move lexical-binding warning from checkdoc to byte-compiler
Date: Sat, 21 Oct 2023 14:17:45 +0300 [thread overview]
Message-ID: <831qdorzqe.fsf@gnu.org> (raw)
In-Reply-To: <F9AC6CC0-AD89-4B09-8101-5F722CD4646B@gmail.com> (message from Mattias Engdegård on Sat, 21 Oct 2023 11:53:58 +0200)
> From: Mattias Engdegård <mattias.engdegard@gmail.com>
> Date: Sat, 21 Oct 2023 11:53:58 +0200
> Cc: monnier@iro.umontreal.ca,
> luangruo@yahoo.com,
> 66636@debbugs.gnu.org,
> stefankangas@gmail.com
>
> We certainly care about users of legacy code. The warning is intended as a soft nudge to encourage users to convert their code to lexical binding, which is quite straightforward most of the time.
>
> When it's not, or when the user simply doesn't have the time or expertise to perform the conversion, it's just a matter of inserting `-*- lexical-binding: nil -*-`. Doing so will both silence the warning and buy the user some reprieve. A lot of reprieve, in fact.
>
> This should probably be pointed out in the NEWS entry as well.
If specifying lexical-binding:nil in the first line is the solution
for those who want to keep dynamically-bound code, then yes, it should
be definitely in NEWS, and probably also in the ELisp manual.
next prev parent reply other threads:[~2023-10-21 11:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 11:48 bug#66636: Move lexical-binding warning from checkdoc to byte-compiler Mattias Engdegård
2023-10-19 11:55 ` Eli Zaretskii
2023-10-19 14:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-19 17:40 ` Stefan Kangas
2023-10-20 10:15 ` Mattias Engdegård
2023-10-20 20:55 ` Stefan Kangas
2023-10-20 6:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-20 7:01 ` Eli Zaretskii
2023-10-20 7:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-20 7:21 ` Eli Zaretskii
2023-10-20 19:44 ` Stefan Kangas
2023-10-20 13:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-20 17:40 ` Mattias Engdegård
2023-10-20 19:27 ` Eli Zaretskii
2023-10-21 9:53 ` Mattias Engdegård
2023-10-21 11:17 ` Eli Zaretskii [this message]
2023-10-21 13:17 ` Mattias Engdegård
2023-10-21 14:42 ` Drew Adams
2023-10-21 15:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 16:08 ` Eli Zaretskii
2023-10-22 0:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-22 4:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-22 5:16 ` Eli Zaretskii
2023-10-22 5:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-20 16:27 ` Drew Adams
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=831qdorzqe.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66636@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=mattias.engdegard@gmail.com \
--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).