-
-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It should be possible to base the next recurrence of an event on the time it was done #53
Comments
Hmm, good point. Thank you for reporting this. Which version of Tasks do you use? |
1.2.0. The latest. |
Thank you. I opened #261 as a separate issue to track the bug. |
+1 P.S. This plugin is really cool! Thanks for developing it! |
+1 for this request |
@schemar I totally understand that you don't have time to work on this now. If and when you do, I'd love to see support added for either
|
I've seen the notion of a a strict recurrence. if you put a date of 2 weeks it recurs every 2 weeks from completion. if you have a strict recurrence when completed it would be scheduled 2 weeks from the due date. I strict occurrence is indicated by having a + in front of the date in todo.txt format. so rec:2w is a recurrence from complete and rec:+2w is a recurrence from original due date |
It should be possible to base the next recurrence of an event on the time the original event was done - instead of the time the original event was scheduled.
Todoist supports that with the
!
operator (i.e. usingevery!
instead ofevery
). We could do the same.The text was updated successfully, but these errors were encountered: