all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: Why is lexical-binding's global value ignored?
Date: Sat, 28 Jan 2023 19:44:59 +0100	[thread overview]
Message-ID: <Y9VtK1QuVcX09bZm@tuxteam.de> (raw)
In-Reply-To: <d3092baf2c685ee92630dcbfea46ea09@bitrot.link>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

On Sat, Jan 28, 2023 at 09:11:41AM -0700, abq@bitrot.link wrote:
> tomas wrote:
> > I think it's backward compatibility, mainly. Files with no explicit
> > lexical binding setting (may) contain code which expects dynamic
> > binding and would break.
> 
> As I mentioned, the global value of lexical-binding defaults to nil.

Yes, you did mention that.

>                                                                     This is
> the case in Emacs 24 through 28, and obviously will be in 29 too. Therefore,
> even if the global value were honored in 29 and future versions, files with
> no explicit setting would continue to get dynamic binding, as they expect.
> They won't break.
> 
> In order to break anything, you would have to do so explicitly, via
> (setq-default lexical-binding t).

The docs only talk about a buffer-local variable, so I'd guess that the
global variable of the same name is simply ignored.

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2023-01-28 18:44 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 [this message]
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
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=Y9VtK1QuVcX09bZm@tuxteam.de \
    --to=tomas@tuxteam.de \
    --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.