I have added tooling so that I can get code listings into / out of the textbook that I'm writing so that I can easily and make sure that they work and produce correct code.

And I'm doing it in LaTeX so I have templates doing some work.

But it's sure nice to just be able to type `make` and see a pdf pop out and green unit tests on the code 3-4 minutes later.

(I have also standardized TODO things to make them easily searchable and show up in a distinctive style in the manuscript).

▲

OkayPhysicist a day ago | parent [-]

When I was working on my thesis, I had an appendix of annotated source code that was generated by a series of Julia macros that effectively turned my code inside out to make a LaTeX document. The custom macro-comments became the bulk of the LaTeX source, the code got wrapped in some environment that presented it with syntax highlighting and all that.

I was halfway through implmenting the syntax highlighting Vim plugin for the resulting Julia-LaTeX hybrid format when I realized that I had an actual deadline coming up, and just accepted solid-color LaTeX source.

	▲	noir_lord a day ago \| parent [-]
		I mean that honours the legacy of how TeX came to be - in spirit at least. > This method, dating back to the 19th century, produced a "classic style" appreciated by Knuth.[6] When the second edition was published, in 1976, the whole book had to be typeset again because the Monotype technology had been largely replaced by phototypesetting, and the original fonts were no longer available. When Knuth received the galley proofs of the new book on 30 March 1977, he found them inferior. Disappointed, Knuth set out to design his own typesetting system. [1] [1] https://en.wikipedia.org/wiki/TeX#History