From: Lars Ingebrigtsen <larsi@gnus.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 47843@debbugs.gnu.org
Subject: bug#47843: 28.0.50; Setting enable-local-variables to nil *appears* to inhibit lexical-binding (but doesn't)
Date: Tue, 04 May 2021 12:22:29 +0200 [thread overview]
Message-ID: <87v97y94t6.fsf@gnus.org> (raw)
In-Reply-To: <e69baad1-7a4c-a103-c8df-fad88bfdbfce@orcon.net.nz> (Phil Sainty's message of "Sun, 18 Apr 2021 01:51:51 +1200")
Phil Sainty <psainty@orcon.net.nz> writes:
> With enable-local-variables set to nil, when editing an elisp buffer
> using lexical-binding it can *seem* as though lexical-binding is not
> enabled, as -*- lexical-binding: t -*- is being inhibited along with
> any others.
>
> Experimentally, Emacs appears to do the right thing, still evaluating
> the code using lexical-binding. I tested loading compiled and
> uncompiled code, as well as `eval-buffer', and all of those seemed
> to work correctly.
enable-local-variables doesn't affect byte-compiling or loading the
file -- only the current buffer settings.
So I tried visiting this file, with enable-local-variables set to nil:
;; -*- lexical-binding: t; -*-
(defun foo ()
(let ((a 1))
(lambda ()
(message "%s" a))))
(funcall (foo))
And `C-M-x' on the two forms failed, as expected. (When enabling the
variable, they are successful.)
So I think everything works as expected here? That is, the buffer
doesn't use lexical mode if you set enable-local-variables to nil.
Are you seeing something different?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-05-04 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 13:51 bug#47843: 28.0.50; Setting enable-local-variables to nil *appears* to inhibit lexical-binding (but doesn't) Phil Sainty
2021-05-04 10:22 ` Lars Ingebrigtsen [this message]
2021-05-04 11:45 ` Phil Sainty
2021-05-05 8:56 ` Lars Ingebrigtsen
2021-05-05 12:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-06 9:04 ` Lars Ingebrigtsen
2021-05-06 13:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-10 10:42 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v97y94t6.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47843@debbugs.gnu.org \
--cc=psainty@orcon.net.nz \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).