Daniel Ortmann <daniel.ortm...@oracle.com> writes: > No other tasks. Here is the complete text with only one url removed: > > * TODO [#C] p6 time entry > DEADLINE: <2019-01-18 Fri ++1w -0d> > :PROPERTIES: > :LAST_REPEAT: [2019-01-11 Fri 17:03] > :END: > :LOGBOOK: > <snip>
> On 1/13/19 10:12 AM, Bernt Hansen wrote: > > Daniel Ortmann <daniel.ortm...@oracle.com> writes: > > I have a weekly scheduled task with ... > DEADLINE: <2019-01-18 Fri ++1w -0d> > > Recently, when I complete the task it reports the following: > > Clock stopped at [2019-01-11 Fri 17:03] after 0:05 > 10 repeater intervals were not enough to shift date past today. > Continue? (y or n) n > > Thoughts? > > Hi Daniel, > > Do you have some other repeating timestamp buried somewhere in that > task? It is probably moving that one forward and it is the one that > needs more than 10 repeats to become current. > > There was a recent change that updates all repeating timestamps in the > task. > > Regards, > Bernt Sorry I can't reproduce what you are seeing. Regards, Bernt
