GNU bug report logs - #66706
[PATCH] Automatic elisp dialect insertion

Previous Next

Full log

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

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: luangruo <at> yahoo.com, mattias.engdegard <at> gmail.com, 66706 <at> debbugs.gnu.org,
 stefankangas <at> gmail.com
Subject: Re: bug#66706: [PATCH] Automatic elisp dialect insertion
Date: Wed, 25 Oct 2023 11:11:52 -0400

> I thought we already decided on that: we should make lexical-binding
> the default at some point.

The question is how to get to that point.

My understanding is that we're waiting for enough files/packages to use
lexbind so that the change will not introduce too much breakage.

> Until then, I see no reason why the prominent indication on the mode
> line should not be enough.

It's much easier to write code directly in lexbind dialect than to go
back and change existing code to adapt to the lexbind dialect.

Since "we should make lexical-binding the default at some point",
all files which come without `lexical-binding:t` cookie will need to go
through the harder path, compared to those who started their life
with that cookie.
So inserting that cookie in new files would help our users take the
easier road.

For that same reason, it will cause less breakage when the default is
changed, and thus will let us make this change sooner rather than later.

Of course, maybe I'm not being bold enough and we shouldn't wait: let's
change the default `lexical-binding` to t right away and just tell
people to add a `lexical-binding:nil` cookie if they don't know how (or
don't want to) adjust their code to the new dialect.


        Stefan

Previous Next

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