Timeline for Can turning on lexical binding in a legacy init file cause problems?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 22, 2019 at 16:32 | vote | accept | Tom | ||
| Jun 22, 2019 at 5:32 | comment | added | Tom | Thanks. I was unsure, because I created a simple .el file which only printed the value of lexical-binding. Then in scratch I set lexical-binding to t and then evaluated loading that file (load "test.el"). And it printed t which confused me. But now I realize t was the result of the evaluated load function which I confused with the print output. Silly mistake. B) | |
| Jun 22, 2019 at 3:32 | history | edited | phils | CC BY-SA 4.0 |
I'm assuming "literal" was a typo. Also fixed formatting (tabs -> spaces).
|
| Jun 21, 2019 at 22:53 | comment | added | Tobias | @Tom I address your comment with an example in my answer. | |
| Jun 21, 2019 at 22:52 | history | edited | Tobias | CC BY-SA 4.0 |
added 1534 characters in body
|
| Jun 21, 2019 at 18:03 | comment | added | Tom | My question is about setting lexical-binding to t in the init.file at the top and then the init.file requires and loads some packages. Can those packages can break if they are not prepared for lexical scoping? | |
| Jun 21, 2019 at 17:55 | history | answered | Tobias | CC BY-SA 4.0 |