Live Preview for Large LuaTeX Documents
Change one line in a large LuaTeX document and see the affected PDF pages update in milliseconds, with a link back to the source that caused each refresh.
When authors of long technical documents change a reference, formula, or chapter, the editor recomputes only the affected portions and replaces the updated PDF pages in place. Each partial refresh can trace back to the source line that triggered it, preserving sophisticated typesetting while providing feedback close to that of a plain-text editor.
Authors can expand the dependency relationships to see why a one-line edit changed particular pages.
Why now
A preprint about recompiling large LuaTeX documents in “1ms” appeared on Hacker News on July 18. In a snapshot at 1:33 UTC on July 19, it had 26 points, 4 comments, and rank 19, suggesting the problem drew one round of community attention during this short observation window, but not supporting an inference about long-term demand. S1
Target user
LaTeX authors maintaining theses, technical books, specifications, or large research reports. They open it after adjusting formulas, citations, footnotes, figures, tables, or chapter structure to immediately see which pages moved and why the change propagated.
Minimal entry point
Start with a local VS Code extension for a defined, verifiable set of LuaLaTeX document structures and common packages. A persistent compilation process records dependencies among source files, auxiliary files, and output pages, then replaces the affected pages after each change; integrate source-to-PDF navigation directly through SyncTeX. S3
Punching above its weight
Build an open-source editor integration layer and compatibility-test repository, using public paper, thesis, and book templates for reproducible comparisons with full compilation. Collect failure cases through Hacker News, TeX Stack Exchange, and LaTeX communities, then turn the findings into a searchable package-compatibility list.
Competitors & gaps
- tex lodeGoogle
- It already claims paragraph-level incremental compilation with LuaTeX and uses live preview in book publishing workflows. The opening is to support existing LaTeX projects and code editors, emphasizing affected-page replacement, source backtracking, and expandable dependency explanations. S2
- TeXpressoGoogle
- It can already re-render changed portions of a document and synchronize the editor and preview in both directions, but it remains in early development and uses a customized XeTeX. The opening is LuaTeX project compatibility, in-place PDF page updates, and an explicit dependency graph. S4
How it makes money
Offer an annual individual subscription that includes the local editor plugin and ongoing updates; sell seat-based licenses to universities, labs, and publishers.
The case against
The hard part is not refreshing the PDF but guaranteeing that the incremental result is correct. Floats, page numbers, tables of contents, cross-references, footnotes, auxiliary files, and custom macros can cause a one-line change to propagate across paragraphs or even chapters. If the dependency graph misses a single edge, authors get a fast preview with stale content; relying frequently on full compilation as a fallback also weakens the speed advantage.