[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#47843: 28.0.50; Setting enable-local-variables to nil *appears* to i
From: |
Phil Sainty |
Subject: |
bug#47843: 28.0.50; Setting enable-local-variables to nil *appears* to inhibit lexical-binding (but doesn't) |
Date: |
Tue, 4 May 2021 23:45:12 +1200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 |
On 4/05/21 10:22 pm, Lars Ingebrigtsen wrote:
> `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?
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.)
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.
-Phil