diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-05 05:23:34 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-05 05:23:34 -0500 |
| commit | bac40a5dbc241cab055f92431a80b7971896fde4 (patch) | |
| tree | 304ab69cdeecba695137043644ab9a8659dbecac /test-from-git | |
| parent | 6afd53b644c9b1fe0592892464c2d7fb37fa29e7 (diff) | |
| download | org-drill-bac40a5dbc241cab055f92431a80b7971896fde4.tar.gz org-drill-bac40a5dbc241cab055f92431a80b7971896fde4.zip | |
fix: clear stale end-pos on resume so final-report fires (upstream #33)
When a user interrupted a drill session to edit or capture, the
session's end-pos slot got set to a marker (or :quit). The end-of-
org-drill cond branched on end-pos: if set, show resume message and
skip org-drill-final-report.
That worked for the first interruption. But on org-drill-resume,
the session was reused with end-pos still carrying the prior marker.
Even when the resumed session completed normally, the same cond
branch fired again — silently skipping final-report.
Clear end-pos at the top of org-drill when resume-p is non-nil, per
Markus's proposed patch on the upstream issue. The resumed session
can now reach the final-report branch.
Diffstat (limited to 'test-from-git')
0 files changed, 0 insertions, 0 deletions
