tuicr/Q/Is there a percent burn-down of my review progress in tuicr?

• Is there a percent burn-down of my review progress in tuicr?

  • AI Answer

    • Short answer: not literally a percentage — tuicr tracks review progress as a reviewed/total fraction in the file tree title (e.g. Files · 2/12 · 12 of 58), plus a "burn-down loop" behavior for r when reviewed files are hidden. There's no % figure anywhere in the docs or source.
    • The tree title's reviewed/total count is deliberately not scoped to the currently visible rows — it stays the true count of the whole review population even while files are hidden or filtered, "since scoping it to the visible rows would collapse it to 0/n exactly when progress matters most" (KEYBINDINGS.md, "Hiding reviewed files").
    • The literal phrase "burn-down" in the docs refers to a workflow, not a stat: with :set noreviewed active (hiding already-reviewed files), pressing r on the file you're reading marks it reviewed and jumps you to the next unreviewed file, wrapping at the end — a "burn-down loop" through the remaining diff.
    • A file whose hunks are individually marked with R is not hidden by that toggle — only the file-level r flag counts toward hiding/burn-down.
    • Source: KEYBINDINGS.md on GitHub ("Hiding reviewed files" section); confirmed in source comments read at commit 2e8475c:
      • file_filter.rs:20-28 — file_matches_patterns doc comment names it the review population the reviewed/total fraction counts.
      • file_filter.rs:44-54 — file_passes_filter doc comment explains why hiding reviewed files would collapse the fraction to 0/n.
      • reviewed.rs:387-393 — file_count is the fraction's denominator, deliberately not scoped by the reviewed-files toggle.
      • file_list.rs:23-34 — where the tree title's reviewed/total string is built.