Re: lexical-binding is turned on in more use cases

[Stefan Monnier]

>> We could say that to recover the original behavior, instead of
>> 
>>     --eval "<foo>"
>>
>> the command could use
>>
>>     --eval "(eval '<foo>)"
>
> And the same for M-:?

Right.  These are not *good* solutions, but they're expedient.
A way to kick the can a bit further down (I hope the
non-lexical-binding mode will disappear before next century).

The right solution is to fix the code so it works correctly with
lexical-binding, which is usually a matter of adding a few `defvar`s or
`require`s, but it takes more effort and knowledge.

Of course, in the vast majority of cases the old code should work
identically with lexical-binding as it did before.


        Stefan