On 2025-04-20 22:38, Remind list wrote:
> Is there a way to mark a task as completed? I like to be sure I didn't
> miss anything when I look back on past tasks.
It depends on how you track tasks.
For one-off tasks, because I track all my reminder files in git (feel
free to use whatever version-control you prefer, even if that's RCS or
CVS), I have no qualms deleting completed tasks. I can always resurrect
them from the repo, either as a one-off checkout to see what I was doing
at a point-in-time, or to extract the reminder for re-use.
That said, if you really do want to keep them around, you could mark it
Done with a TAG like
REM Apr 22 2025 TAG done MSG Accounting audit report to Pat
If you have repeating tasks like balancing the checkbook monthly on the
8th with a few days of reminder depending on when the statment usually
shows up in the mail:
REM 8 +3 MSG %"Balance checkbook%" %b
or getting your car inspected annually by the end of each July with
reminders all month until you do it:
REM Jul 31 +30 MSG %"Car inspection%" %b
perhaps this little set of helper functions would be useful:
FSET done_ym(y, m) y < $Ty || (y == $Ty && m < $Tm)
FSET done_y(y) y < $Ty
which I use like:
REM 8 +3 SATISFY [done_ym(2025, 4)] MSG %"Balance checkbook%" %b
REM Jul 31 +30 SATISFY [done_y(2024)] MSG %"Car inspection%" %b
I can then update when I last did the task so that it doesn't keep
showing up until the next time it's about to come due.
I actually tweak the %b with
FSET due() "by " + $T + " (" + dosubst("%b", $T) + ")"
and then
REM 8 +3 SATISFY [done_ym(2025, 4)] MSG %"Balance checkbook%" [due()]
REM Jul 31 +30 SATISFY [done_y(2024)] MSG %"Car inspection%" [due()]
so it reads a little more cleanly.
Hopefully some of that is helpful to you,
-tim
_______________________________________________
Remind-fans mailing list
[email protected]
https://dianne.skoll.ca/mailman/listinfo/remind-fans
Remind is at https://dianne.skoll.ca/projects/remind/
