Reset and recur?

Hi Nana

This confused me too, and I ended up looking at the Sync script. Which turns out to be 66 pages of code. Ethan has put an aamazing amount of work into kGTD. Fortunately the part dealing with recur & reset is pretty short.

I think it works like this, using a week as an example:

Recur every week creates a new action which has a start date 7 days after the start date of the action that was marked completed. If there’s a dues date, the new action’s due date is set 7 days after the prior action’s due date.

Reset 1 week creates a new action which has a start date 7 days after the day the action that was marked completed. If it has a due date, then the due date is set the same number of days after the due date of the prior iteration.

The words after recur or reset are treated as a period of time, even though the code accepts “every week” or “each Month.”
You can’t use days of the week, “recur Tuesday” but you can type “Tuesday” (or “tomorrow”) into the start and due dates, where it’ll get translated into the date of the next Tuesday (or of tomorrow).

The new action doesn’t show in the Actions lists until the start date. If you don’t have a start date, then it shows in the Actions list as soon as you sync.

I thought I had examples where the dates were set to be one day different than what this explanation says, so there may be something flakey in the date arithmetic. Or in my understanding.

Paul

If you use reset or recur, does anything get archived?

(What I’d like is to have the completed task archived, and a new replicant spawned at the set time.)

Victor