Evaluate using lexical-binding if the file is lexically scoped #91
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Author
|
And as a side note, while debugging I ended up simplifying the code a bit, but there too many changes to make a clean sequence of commits. Ultimately, I just grouped them all into one big dummy commit, and if you are interested, I could extract certain changes and propose them as separate push requests. |
Author
|
Ping? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have code in my init.el that requires lexical scoping, and it could not be evaluated correctly without passing setting
lexicalwhen callingeval.This patch uses the buffer-local value of
lexical-bindingto invokeevalcorrectly.