News for hackers. Stuff that matters.
Re:A literate Org doc on building Emacs from source by euroderf on Sunday October 29, 2023 @09:36AM (#38058511)
I'd like to see literate programming melded with the docs as code approach. A simple way to see (say) myfile.go and myfile.md displayed side-by-side, with comments and their code targets aligned side-by-side during scrolling.

(Or, alternatively, comments & code interleaved... but then when the comments and code are both collapsible, it's not much different from current IDEs.)

This shouldn't be too awfully difficult. Process myfile.go to autogenerate myfile.md, which contains markers or tags or labels to indicate the points to align with the course code.

Is this making any sense ?

Re:A literate Org doc on building Emacs from source by jhidding on Sunday October 29, 2023 @10:19AM (#38058884)
Yes it does. We (at the Netherlands eScience Center) will be building such an interface next January, extending Entangled (https://entangled.github.io). This approach uses Markdown and enables editing your code both in Markdown and generated source codes, synchronizing when files are written to. Currently with traditional documentation site generators like MkDocs, you can get nicely presented content, but what you suggest requires a bit more work. We will build better content navigation in Pandoc, and a side-by-side view as you suggest is definitely on the table. Also: outside contributions are more than welcome ;)
Re:A literate Org doc on building Emacs from source by euroderf on Monday October 30, 2023 @05:57AM (#38067449)
It does look nifty. Altho getting up to speed is non-trivial. I don't suppose you have any working examples in the Go language ?
Re:A literate Org doc on building Emacs from source by jhidding on Tuesday October 31, 2023 @05:45PM (#38091846)
Sadly nothing Go specific. We're working on making it easier to work with.
Re:A literate Org doc on building Emacs from source by euroderf on Wednesday November 01, 2023 @06:34AM (#38096574)
Go already has built-in support for tests and for executable examples (that go into generated package documentation), so it might get hairy.