GNU bug report logs - #66636
Move lexical-binding warning from checkdoc to byte-compiler

Previous Next

Full log

Message #53 received at 66636 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Mattias Engdegård <mattias.engdegard <at> gmail.com>
Cc: luangruo <at> yahoo.com, monnier <at> iro.umontreal.ca, 66636 <at> debbugs.gnu.org,
 stefankangas <at> gmail.com
Subject: Re: bug#66636: Move lexical-binding warning from checkdoc to
 byte-compiler
Date: Sat, 21 Oct 2023 14:17:45 +0300

> From: Mattias Engdegård <mattias.engdegard <at> gmail.com>
> Date: Sat, 21 Oct 2023 11:53:58 +0200
> Cc: monnier <at> iro.umontreal.ca,
>  luangruo <at> yahoo.com,
>  66636 <at> debbugs.gnu.org,
>  stefankangas <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.