<feed xmlns='http://www.w3.org/2005/Atom'>
<title>org-drill/tests/test-org-drill-resume-clears-end-pos.el, branch main</title>
<subtitle>Spaced-repetition flashcards for Org Mode
</subtitle>
<id>https://git.cjennings.net/org-drill/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/org-drill/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/org-drill/'/>
<updated>2026-05-05T10:23:34+00:00</updated>
<entry>
<title>fix: clear stale end-pos on resume so final-report fires (upstream #33)</title>
<updated>2026-05-05T10:23:34+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-05T10:23:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/org-drill/commit/?id=bac40a5dbc241cab055f92431a80b7971896fde4'/>
<id>urn:sha1:bac40a5dbc241cab055f92431a80b7971896fde4</id>
<content type='text'>
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.
</content>
</entry>
</feed>
