Timeline for debugging some elisp -- "end of file during parsing error" in init.el
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 12, 2016 at 19:49 | comment | added | Stefan | Please don't use custom-set-variables in your own Elisp code. This is meant to be auto-generated only. Don't copy&paste it. Look for equivalent code using setq or something like that. | |
| Sep 11, 2016 at 16:22 | history | edited | Drew | edited tags | |
| Sep 11, 2016 at 15:58 | comment | added | lawlist | If the file is large, you can use M-x check-parens to jump to the offending section. If the file is short, or you are looking at a short section of code, then there are methods to highlight matching parentheses to visually see where a parentheses is misplaced or missing. Here is a link to my own variation of highlight-parentheses-mode: stackoverflow.com/a/23998965/2112489 | |
| Sep 11, 2016 at 15:57 | answer | added | sds | timeline score: 41 | |
| Sep 11, 2016 at 15:56 | answer | added | lawlist | timeline score: 5 | |
| Sep 11, 2016 at 15:30 | history | asked | loukios | CC BY-SA 3.0 |