From: Lars Ingebrigtsen <larsi@gnus.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 47843@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#47843: 28.0.50; Setting enable-local-variables to nil *appears* to inhibit lexical-binding (but doesn't)
Date: Wed, 05 May 2021 10:56:47 +0200 [thread overview]
Message-ID: <87r1il7e40.fsf@gnus.org> (raw)
In-Reply-To: <dd44cabe-6a77-4de5-bf54-1b8ebf37b913@orcon.net.nz> (Phil Sainty's message of "Tue, 4 May 2021 23:45:12 +1200")
Phil Sainty <psainty@orcon.net.nz> writes:
> I see the same thing. I also note that `eval-region' produces the
> same result as `eval-defun'. (I'd only tested `eval-buffer' initially,
> and that respects the `lexical-binding' setting.)
Ah, right. Hm... well, I guess that's kinda logical? But it's a bit
confusing; yes...
> My main point was that I'm dubious that enable-local-variables should
> be allowed to affect lexical-binding in any situation.
>
> While it's strictly true that the lexical-binding implementation
> utilises a file-local variable, I feel like this particular variable
> should be guaranteed to be respected when set, because it fundamentally
> changes how the code will be interpreted.
>
> Are there are any other file-local variables in that same category?
> I couldn't think of any offhand, and so this seemed worthy of having
> an exception made.
Hm... can't think of any other variables like this, either.
I don't really have an opinion here -- I can see arguments for both
sides. Perhaps Stefan has an opinion here (added to the CCs).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-05-05 8:56 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
2021-05-04 11:45 ` Phil Sainty
2021-05-05 8:56 ` Lars Ingebrigtsen [this message]
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=87r1il7e40.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47843@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--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).