Timeline for It is possible to instrument a literate Org-mode configuration file with a backing Emacs Lisp file?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 15, 2018 at 1:47 | comment | added | stardiviner |
Can set buffer-file-name to a temporary fake file. But if want to disable flycheck I think disable that is a good solution.
|
|
| Oct 14, 2018 at 22:16 | comment | added | Matthew Piziak |
@JohnKitchin @stardiviner I get emacs-lisp predicate:nil flycheck-verify-setup due to the fact that buffer-file-name is nil in the Org Src buffers.
|
|
| Oct 14, 2018 at 0:52 | comment | added | stardiviner | @MatthewPiziak If all your source blocks are emacs-lisp blocks, and evaluated, then all your elisp code should be available for Emacs, flycheck will be aware of that. And also, flycheck works fine on my org-edit-src-block too. | |
| Oct 13, 2018 at 19:36 | comment | added | John Kitchin | flycheck seems to work fine for me in org-edit mode for emacs-lisp. What does it not do for you? | |
| Oct 13, 2018 at 13:24 | comment | added | Matthew Piziak |
I'm afraid this does not do anything except evaluate the blocks and add RESULTS blocks. Flycheck remains unusable.
|
|
| Oct 13, 2018 at 7:45 | history | answered | stardiviner | CC BY-SA 4.0 |