← All research

Research / Compiler

From source to page. And back.

Follow the local build pipeline, then see how LatexDo turns compiler output into useful feedback.

From source to page Local compilation
05 / 05

Build again. See the page.

  1. Start with your source.
  2. Your local TeX engine builds.
  3. The log points to the problem.
  4. You correct the source.
  5. Build again. See the page.
An illustrative build: latexmk runs the local TeX engine; log analysis locates an error. After a source edit, a successful rebuild returns a PDF and SyncTeX positions. LatexDo explains errors; the compiler does not edit your source.

01 / Build locally

A fresh folder for every job.

The Electron compile service resolves latexmk, selects pdfLaTeX, XeLaTeX, or LuaLaTeX, and writes artifacts into a unique .latexdo/build/job-… directory. Builds support cancellation and a timeout.

02 / Connect the output

Three outputs, three jobs.

The PDF becomes the preview. SyncTeX maps positions between the PDF and source. The build log is parsed for file-and-line errors, warnings, and layout issues.

03 / Explain the failure

Find the useful error in the noise.

Source analysis adds context, likely locations, and suggested fixes. Diagnostic ranking distinguishes a likely primary error from follow-on failures. These are heuristic explanations; the original log remains available.

Inside the implementation

Based on the desktop source reviewed at revision 4059a3d . File paths are relative to the application repository.