diff options
Diffstat (limited to '2023/talks/doc.md')
| -rw-r--r-- | 2023/talks/doc.md | 44 |
1 files changed, 44 insertions, 0 deletions
diff --git a/2023/talks/doc.md b/2023/talks/doc.md index 0f7edf2c..1a2ce701 100644 --- a/2023/talks/doc.md +++ b/2023/talks/doc.md @@ -19,6 +19,50 @@ We'll also show how these literate documents can be exported to LaTeX and ultima Also shared at SeaGL 2023 +# Discussion + +## Questions and answers + +- Q: Did you develop a variant of your document for Centos? + - A: +- Q: Great presentation. The preparation is outstanding. For someone + like me that never touched the org\--mode side of emacs, what do you + feel its the more complex part to tackle? You made it seem simple + but the complexity there.. woof + - A: +- Q: How do you normally debug, e.g. view the logs or see failed + statuses, when the commands in the src blocks fail? Especially if + they output lots and lots of logs, and you need to see the full + history of the build. + - A: +- Q: Do you find yourself doing plain-text exports? I saw you doing + that as an example for a bit. How do you like to format them so they + come out looking nice? + - A: +- Q: IIUC if you commit that eval line to your config then theoretically you could open an Org file prepared by someone else and it would automatically run the code in a "startup" block that might be malicious, right? + - A: for sure. if you agree to have a block run when you load the document, you could get burned if it changes into something eveil. + +### Notes and discussion + +- Seems like we could use some kind of extension that would hash a source block and allow you to automatically run ones you've marked safe +- Property inheritance I still don't completely understand, heh. +- seeing section on Org MACRO, recall having trouble a while back invoking a MACRO from inside a MACRO; is this a limitation or was I holding it wrong? + - AFAIR, macros do support recursion + - actually my issue was passing TITLE to a MACRO <https://paste.rs/LZunR> + - yeah. "eval" macro arguments in particular are not expanded. you may raise it on the mailing list - looks like something worth considering +- I almost wanted to pre-process my org mode files with a more advanced macro system like m4. But then I came to my senses. + - When discussing Org mode as replacement of TexInfo, it has been rised (Texinfo uses m4) (<https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#External-Macro-Processors>) but why do you need m4 when there is Elisp... can just put a code block that will do all the work and eval on export + - A: True. You can write elisp to do all the macro replacement, but you end up editing the buffer when you do that, which has its own disadvantages. + - during export, it is a throwaway buffer + - A: oh, I didn't think of that. Ultimately though org macros have a ways to go before they're truly useful in all context you might want to use them. + - org-export-before-processing-hook runs before macro expansion but around the same time (we really need to document the export process step by step) +- Thanks for the awesome presentation, I can't wait to add some of this stuff to my documents +- I was pretty terrified to see that ChatGPT could write elisp +- Also, loved the presentation — great walk-through of the thought process & how to improve. Was happy when Macros made their way in +- Yeah. tramp would have been cool, but can be dangerous if you start doing sudo apt in the wrong machine +- I can't imagine cross-compiling Emacs for Windows on Linux is easy, but sounds "fun". +- I tried cross-compiling Emacs for Serenity. Emacs uses some intermediate binaries (like make-docfile) during its build process, which causes issues with cross-compiling that I couldn't quite figure out. + [[!inline pages="internal(2023/info/doc-after)" raw="yes"]] [[!inline pages="internal(2023/info/doc-nav)" raw="yes"]] |