Compile Loss Check finds manuscript paragraphs with no match

Name: Compile Loss Check
Author: theluckystrike

Find compiled paragraphs with no Longform match.

MIT · no telemetry · core features free

The result lists five paragraph texts without a match with scene paths and line numbers. — Open larger

version: 1.1.0
released: 2026-10-21
downloads: 17
review: Passed
health: Excellent
license: MIT
listed for: Desktop, Mobile
obsidian: 1.13.4 or later

The README reports macOS app tests on Obsidian 1.13.4 and 1.14.4 with a handwritten manuscript. Mobile use, real Longform compiles, large-manuscript speed and real GitHub sign-in remain untested.

Directory facts fetched 2026-10-23 07:28 UTC from community.obsidian.md/users/theluckystrike.

About Compile Loss Check

You draft in Longform scenes and want to check a compiled manuscript before sending it.

Compile Loss Check compares your current scenes with a compiled Markdown note. It saves paragraphs with no match in a new report with scene links and line numbers.

The comparison counts matching paragraph text after collapsing whitespace. Changed quotes or joined paragraphs can produce mismatches, so read the report before treating a result as lost text.

The check runs on a sample Longform project, shows the paragraphs with no match and opens the saved report

Free features

Check a compiled note against its scenes

Compare paragraph text and occurrence counts after collapsing whitespace. The check skips initial YAML properties and paragraphs containing only a thematic break. Extra compiled text does not fail the check.

Pick the index and the compiled note

Run Check a compiled manuscript and select your index, then your compiled note. The checker reads nested scene order from the index without starting Longform.

The index picker lists two notes with a longform property. — Open larger

A new Markdown report

Each check creates a report with scene links and source line numbers. Reports go beside the compiled note unless you choose a report folder in settings. An occupied report name gets a number.

The saved report shows a repeated paragraph and its possible source lines. — Open larger

Incomplete checks

Missing scenes, invalid scene lists and unsupported project formats produce an incomplete result with errors. If an input note changes during the scan, run another check.

An incomplete result names the missing Harbor scene note. — Open larger

The free version checks one index against one compiled note and saves a report; profiles, exclusions and report history need Pro.

Pro features

Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.

Comparison profiles with exclusions Pro

Save your last check as a named profile with paragraph texts and scene paths to skip. The report counts excluded source paragraphs. Profiles stay in the plugin data of your vault.

Several compiled notes and report history Pro

Add several compiled notes to one profile and get a report section for each. With Pro active, saved checks enter a history that keeps the newest 200 entries. Open an earlier report by date, profile and result.

Open larger

See how Pro works

Set up Compile Loss Check

needs

Obsidian 1.13.4 or later
A Longform scenes index and a compiled Markdown note in your vault.

steps

Compile your Longform project to a note, or use a compiled note you already have.
Run Check a compiled manuscript from the command palette.
Select your project index, then your compiled note.
Read the result and select Open report to review the saved note.

If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.

How to check a Longform compile for missing text

Known limits of Compile Loss Check

The checker compares current scenes and cannot recover their text at compile time.
Changed quotes, words or paragraph boundaries can produce mismatches even when text remains in the manuscript.
Repeated text with only some matching copies produces uncertain source locations.
Only Longform scenes projects and compiled Markdown notes are supported; single-note projects produce an incomplete result.
A check becomes incomplete above 2,000 scenes or 20,000,000 JavaScript string units of scene and compiled text.
The result window shows at most 20 paragraph texts without a match; the saved report contains the remaining entries.
Quote and containment hints cover at most the first 300 paragraph texts without a match.
Report links open scene notes; their line numbers appear as text rather than line targets.
Saved profile paths do not follow renamed or moved notes.
The report history keeps the newest 200 entries, and saving a profile with an existing name replaces that profile.
Mobile use, large-manuscript speed, real Longform compiles and GitHub sign-in with a real account remain untested.

Questions about Compile Loss Check

Why does existing text show without a match?

Changed words, quote marks or paragraph boundaries can prevent a strict match. The report can hint at changed quotes or a longer paragraph containing the text.

Can this check prove what I compiled earlier?

No. It reads your scenes as they are now. Later edits can show as mismatches against an older manuscript.

Does the checker edit my manuscript?

It reads your index, scenes and compiled note. It creates a new report note and makes the report folder if needed.

What does Pro cost?

Sponsor theluckystrike through GitHub Sponsors for $5 a month or $15 once, then sign in through plugin settings. A total payment of $15 meets the payment requirement without further payment. Sign-in and sponsorship checks still apply.

Network use

After you select Sign in with GitHub, github.com receives the public client ID, profile scope and device-flow sign-in requests. Queries to api.github.com ask for your sponsorship tier and total payment on sign-in, scheduled refreshes or Refresh. The plugin sends no note content, file names or vault data, and makes no network requests before sign-in.

Read the full network disclosure