all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: abq@bitrot.link
Cc: emacs-devel@gnu.org
Subject: Re: Why is lexical-binding's global value ignored?
Date: Mon, 30 Jan 2023 14:32:58 +0200	[thread overview]
Message-ID: <83r0vc5hj9.fsf@gnu.org> (raw)
In-Reply-To: <43216edcfeada34083e17a8230af2ee3@bitrot.link> (abq@bitrot.link)

> Date: Sun, 29 Jan 2023 20:53:30 -0700
> From: abq@bitrot.link
> Cc: emacs-devel@gnu.org
> 
> On 2023-01-28 23:54, Eli Zaretskii wrote:
> > Wasn't that already explained?  What happens if you say
> > 
> >   (setq-default lexical-binding t)
> > 
> > and then load a Lisp file that expects dynamic-binding by default?
> 
> Then it breaks!

We want to avoid such a breakage.  It is year 2023 out there, but
there's still gobs of code that assumes dynamic binding.

> As I wrote in my response to tomas: “In order to break 
> anything, you would have to do so explicitly, via (setq-default 
> lexical-binding t).”

We decided that was not explicit enough, because many people will not
understand the disastrous consequences.  E.g., even the user's init
file can fail to load.

> Of course, nobody actually does that. Therefore, it would be safe to 
> honor the global value in Emacs 29.

Sorry, we won't, not in Emacs 29.  And that's final.  Please accept
that, even if you disagree.



  reply	other threads:[~2023-01-30 12:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28  3:01 Why is lexical-binding's global value ignored? abq
2023-01-28  7:10 ` tomas
2023-01-29  9:36   ` Jean Louis
2023-01-31  4:19     ` Richard Stallman
2023-01-31 13:49       ` Eli Zaretskii
2023-01-28 16:11 ` abq
2023-01-28 18:44   ` tomas
2023-01-28 22:34   ` abq
2023-01-29  6:54     ` Eli Zaretskii
2023-01-30  3:53       ` abq
2023-01-30 12:32         ` Eli Zaretskii [this message]
2023-01-30 12:59           ` tomas
2023-01-30 13:45         ` Po Lu
2023-02-01  2:04     ` abq

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=83r0vc5hj9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=abq@bitrot.link \
    --cc=emacs-devel@gnu.org \
    /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.