No Wayman writes:
The third case I outlined.
Tangling a :lexical t src block sults in a dynamically scoped
file unless the
user manually inserts the file-local variable line.
*results
That's adjacent to the issue I originally raised, but we could do
better in that case.
Timothy writes:
Hi NoWayman,
I ran into this with some code I’m writing which checks against
`lexical-binding’.
Should the following result in “lexical binding enabled” or
“lexical binding disabled”?:
Can you think of any examples where this results in different
behaviour (without
Hi NoWayman,
> I ran into this with some code I’m writing which checks against
> `lexical-binding’.
> Should the following result in “lexical binding enabled” or
> “lexical binding disabled”?:
Can you think of any examples where this results in different behaviour (without
explicitly checking
My thoughts on this would be that if lexical-bindings is
supposed to be
bound to t, it should be done by eval when it gets a non-nil
value for
it's optional argument. If I execute (eval FORM t) in an emacs
lisp
buffer, it looks like lexical-bind is not set either, so I don't
think
it should
No Wayman writes:
> I ran into this with some code I'm writing which checks against
> `lexical-binding'.
> Should the following result in "lexical binding enabled" or
> "lexical binding disabled"?:
>
> #+begin_src emacs-lisp :lexical t
> (message "lexical binding %sabled" (if lexical-binding
I ran into this with some code I'm writing which checks against
`lexical-binding'.
Should the following result in "lexical binding enabled" or
"lexical binding disabled"?:
#+begin_src emacs-lisp :lexical t
(message "lexical binding %sabled" (if lexical-binding "en"
"dis"))
#+end_src
