[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lexical-binding is turned on in more use cases
From: |
Eli Zaretskii |
Subject: |
Re: lexical-binding is turned on in more use cases |
Date: |
Sun, 08 Mar 2020 19:01:02 +0200 |
> From: Stefan Monnier <address@hidden>
> Cc: address@hidden
> Date: Sun, 08 Mar 2020 12:35:22 -0400
>
> > Commit e08e0880f made lexical-binding be non-nil in more use cases,
> > but the NEWS entry doesn't say how to get back the old behavior. Is
> > there a way of getting back the old behavior, say, for M-: or for
> > "--eval" options?
>
> Not really, no. You can do things like replacing `<foo>` with `(eval
> '<foo>)` or adding a bunch of `(defvar <bar>)`, but there's no
> config var to get back the old behavior.
And neither can one bind something in the form being evaluated,
AFAICS, right? Isn't that a bit too harsh?
- lexical-binding is turned on in more use cases, Eli Zaretskii, 2020/03/07
- Re: lexical-binding is turned on in more use cases, Stefan Monnier, 2020/03/08
- Re: lexical-binding is turned on in more use cases,
Eli Zaretskii <=
- Re: lexical-binding is turned on in more use cases, Stefan Monnier, 2020/03/08
- Re: lexical-binding is turned on in more use cases, Eli Zaretskii, 2020/03/08
- Re: lexical-binding is turned on in more use cases, Stefan Monnier, 2020/03/08
- Re: lexical-binding is turned on in more use cases, Eli Zaretskii, 2020/03/08
- Re: lexical-binding is turned on in more use cases, Alan Mackenzie, 2020/03/08
- Re: lexical-binding is turned on in more use cases, Eli Zaretskii, 2020/03/08
- Re: lexical-binding is turned on in more use cases, Alan Mackenzie, 2020/03/08
- Re: lexical-binding is turned on in more use cases, Eli Zaretskii, 2020/03/08
- Re: lexical-binding is turned on in more use cases, Alan Mackenzie, 2020/03/08
- Re: lexical-binding is turned on in more use cases, Richard Stallman, 2020/03/10