Rendered at 16:46:08 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
ifh-hn 3 minutes ago [-]
I finished a BSc and an MSc with quarto and fossil. It had to be in Word so I wrote a VBA script that pulled comments so I could edit my markdown files easier.
Does seem like overkill but everyone scratches their own itch.
mlyle 9 minutes ago [-]
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).
hyperhello 7 minutes ago [-]
Is there a word for the right amount of engineering? Kind of a negative concept of not engaging in performative conceptualization. Just doing it in a way that the implementation was natural and not worth writing home about.
paulorlando 14 minutes ago [-]
And here I've just been using pen/paper for outlining and notes and then GoogleDocs for mine.
emil-lp 33 minutes ago [-]
Why not Markdown - pandoc - epub/pdf?
hk__2 3 minutes ago [-]
Not OP but probably to be able to tweak the layout without having a doctorate in LaTeX templates.
saaaaaam 5 minutes ago [-]
Presumably because the publisher takes the manuscript and does all the formatting and so on.
schnake 49 minutes ago [-]
This is very close to the philosophy behind something I've been building:
I built Mark2TeX while writing my thesis in Obsidian. I wanted to write the prose in Markdown, but keep a normal LuaLaTeX document for math, citations, cross-references, etc.
So Mark2TeX lets me use Markdown-like files and drop into real LaTeX whenever I need it.
I deliberately didn't try to build a complete Markdown/Pandoc replacement. It's basically an attempt to under-engineer the Markdown/LaTeX boundary.
Does seem like overkill but everyone scratches their own itch.
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).
https://github.com/simonschnake/Mark2Tex
I built Mark2TeX while writing my thesis in Obsidian. I wanted to write the prose in Markdown, but keep a normal LuaLaTeX document for math, citations, cross-references, etc.
So Mark2TeX lets me use Markdown-like files and drop into real LaTeX whenever I need it.
I deliberately didn't try to build a complete Markdown/Pandoc replacement. It's basically an attempt to under-engineer the Markdown/LaTeX boundary.