recent org-mode changes: completion of repeated tasks cause rewriting of LOGBOOK 'Rescheduled from' entries

recent org-mode changes: completion of repeated tasks cause rewriting of LOGBOOK 'Rescheduled from' entries

[Daniel Ortmann]

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

I have a daily scheduled task with ...
  SCHEDULED: <2019-01-11 Fri 07:50 .+1d>

Recently, when I complete the task it not only moves the schedule to the
next day
... but it also /_rewrites_/ all of the "Rescheduled from ..." entries
in the LOGBOOK.

For example,
  - Rescheduled from "[2019-01-11 Fri 07:50 .+1d]" on [2019-01-02 Wed 10:54]
  - Rescheduled from "[2019-01-11 Fri 07:50 .+1d]" on [2018-12-31 Mon 11:50]
  - Rescheduled from "[2019-01-11 Fri 07:50 .+1d]" on [2018-12-16 Sun 19:29]
  - Rescheduled from "[2019-01-11 Fri 07:50 .+1d]" on [2018-12-03 Mon 10:49]
 etc.

Those previous LOGBOOK entries no longer are available; they are wiped
out by new task completions.



[-- Attachment #2: Type: text/html, Size: 1050 bytes --]

Re: recent org-mode changes: completion of repeated tasks cause rewriting of LOGBOOK 'Rescheduled from' entries

[cesar mena]

[-- Attachment #1: Type: text/plain, Size: 59 bytes --]


sorry. forgot to do a wide reply. fwd'ing the list.

-cm


[-- Attachment #2: Type: message/rfc822, Size: 1980 bytes --]

From: cesar mena <cesar.mena@gmail.com>
To: Daniel Ortmann <daniel.ortmann@oracle.com>
Subject: Re: [O] recent org-mode changes: completion of repeated tasks cause rewriting of LOGBOOK 'Rescheduled from' entries
Date: Fri, 11 Jan 2019 09:43:27 -0500
Message-ID: <875zuvfe5s.fsf@gnu.org>

hello daniel,

Daniel Ortmann <daniel.ortmann@oracle.com> writes:

> I have a daily scheduled task with ...
>   SCHEDULED: <2019-01-11 Fri 07:50 .+1d>
>
> Recently, when I complete the task it not only moves the schedule to the next day
> ... but it also rewrites all of the "Rescheduled from ..." entries in the LOGBOOK.
>
> For example,
>   - Rescheduled from "[2019-01-11 Fri 07:50 .+1d]" on [2019-01-02 Wed 10:54]
>   - Rescheduled from "[2019-01-11 Fri 07:50 .+1d]" on [2018-12-31 Mon 11:50]
>   - Rescheduled from "[2019-01-11 Fri 07:50 .+1d]" on [2018-12-16 Sun 19:29]
>   - Rescheduled from "[2019-01-11 Fri 07:50 .+1d]" on [2018-12-03 Mon 10:49]
>  etc.

see this thread for the details:
http://lists.gnu.org/archive/html/emacs-orgmode/2019-01/msg00095.html

the short of it is that as of commit af81211fdc *any* inactive timestamp
within your "headline" that has a repeater will update when you mark the
task as DONE. it doesn't matter where that timestamp is.

> Those previous LOGBOOK entries no longer are available; they are wiped out by new
> task completions.

i feel your pain. i hope you source control your org files. in the
meantime move the HEAD of your tree to some parent of af81211fdc or go
back to release_9.1.14.

good luck!

best,
-cm