all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Default lexical-binding to t
Date: Fri, 01 Nov 2024 12:03:23 -0500	[thread overview]
Message-ID: <874j4qyjhg.fsf@red-bean.com> (raw)
In-Reply-To: <jwv34kbf79m.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 01 Nov 2024 08:55:56 -0400")

On 01 Nov 2024, Stefan Monnier wrote:
>In bug#74145 I suggest that it is time to change the default of
>`lexical-binding` to t.  Clearly this is a breaking change, but 
>only for
>those files which:
>
>- Don't have a `lexical-binding` cookie.
>- Have code which happens to behave differently under the new 
>dialect
>  (such code is not rare, but a lot of code works identically in 
>  the
>  two dialects).
>
>I believe by the time Emacs-31 will be released, such files will 
>be
>uncommon, and it is easy to fix them (either by adjusting he 
>code, or
>by slapping a `lexical-binding` cookie).

+1  It's time.

Anecdata, but: a lot of the random Emacs packages I encounter in 
the wild lately have `lexical-binding` cookies already (and 
usually to t anyway).  Most recently 
https://github.com/kmonad/kbd-mode/blob/master/kbd-mode.el, for 
example.  No doubt there are also many that don't, but I think 
knowledge about the new dialect is diffused widely enough now that 
when Emacs' default switches over, some user of a given package 
will quickly recognize what's going on and submit the appropriate 
change to that package; in a few cases I have done so myself.

Best regards,
-Karl



      parent reply	other threads:[~2024-11-01 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 12:55 Default lexical-binding to t Stefan Monnier
2024-11-01 14:42 ` Gerd Möllmann
2024-11-01 17:03 ` Karl Fogel [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874j4qyjhg.fsf@red-bean.com \
    --to=kfogel@red-bean.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.