From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: please read: bug when marking tasks done Date: Mon, 07 Jan 2019 09:52:13 -0500 Message-ID: <8736q47c6a.fsf@norang.ca> References: <87d0paprs6.fsf@gnu.org> <87wonhcpnj.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:40008) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ggWGa-0003MN-Ho for emacs-orgmode@gnu.org; Mon, 07 Jan 2019 09:52:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ggWGZ-0008D1-8U for emacs-orgmode@gnu.org; Mon, 07 Jan 2019 09:52:36 -0500 Received: from outbound1a.eu.mailhop.org ([52.58.109.202]:58323) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ggWGU-00089N-P1 for emacs-orgmode@gnu.org; Mon, 07 Jan 2019 09:52:32 -0500 In-Reply-To: <87wonhcpnj.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 07 Jan 2019 00:49:52 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: cesar mena Cc: emacs-orgmode Nicolas Goaziou writes: > Hello, > > cesar mena writes: > >> hello everyone, >> >> in the maint branch, marking a repeatable task as DONE causes the >> "Rescheduled from" dates to be lost in the :LOGBOOK:. >> >> in the below diff all of the from dates are rewritten with the new >> scheduled date: >> >> - SCHEDULED: <2018-12-04 Tue .+1m> >> + SCHEDULED: <2019-02-05 Tue .+1m> >> :PROPERTIES: >> - :LAST_REPEAT: [2018-08-08 Wed 07:40] >> + :LAST_REPEAT: [2019-01-05 Sat 18:47] >> :END: >> :LOGBOOK: >> - - Rescheduled from "[2018-11-28 Wed .+1m]" on [2018-11-28 Wed 0= 8:35] >> - - Rescheduled from "[2018-11-25 Sun .+1m]" on [2018-11-25 Sun 0= 9:17] >> - - Rescheduled from "[2018-11-20 Tue .+1m]" on [2018-11-22 Thu 1= 0:03] >> - - Rescheduled from "[2018-11-13 Tue .+1m]" on [2018-11-17 Sat 0= 9:48] >> - - Rescheduled from "[2018-11-06 Tue .+1m]" on [2018-11-08 Thu 0= 7:02] >> - - Rescheduled from "[2018-10-28 Sun .+1m]" on [2018-10-30 Tue 1= 6:22] >> - - Rescheduled from "[2018-10-25 Thu .+1m]" on [2018-10-25 Thu 0= 7:34] >> - - Rescheduled from "[2018-10-19 Fri .+1m]" on [2018-10-19 Fri 0= 7:48] >> - - Rescheduled from "[2018-10-16 Tue .+1m]" on [2018-10-16 Tue 1= 6:21] >> - - Rescheduled from "[2018-10-11 Thu .+1m]" on [2018-10-14 Sun 1= 0:31] >> - - Rescheduled from "[2018-10-07 Sun .+1m]" on [2018-10-08 Mon 0= 8:48] >> - - Rescheduled from "[2018-09-27 Thu .+1m]" on [2018-09-29 Sat 1= 8:50] >> - - Rescheduled from "[2018-09-20 Thu .+1m]" on [2018-09-20 Thu 0= 9:50] >> - - Rescheduled from "[2018-09-08 Sat .+1m]" on [2018-09-14 Fri 0= 7:10] >> + - State "DONE" from "TODO" [2019-01-05 Sat 18:47] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-28 Wed 0= 8:35] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-25 Sun 0= 9:17] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-22 Thu 1= 0:03] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-17 Sat 0= 9:48] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-08 Thu 0= 7:02] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-30 Tue 1= 6:22] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-25 Thu 0= 7:34] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-19 Fri 0= 7:48] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-16 Tue 1= 6:21] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-14 Sun 1= 0:31] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-08 Mon 0= 8:48] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-29 Sat 1= 8:50] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-20 Thu 0= 9:50] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-14 Fri 0= 7:10] >>=20=20=20 >> bisect says it was introduced in >> af81211fdc01b64449179bcdb77fb1c8ecb3fb94. > > Which is a bugfix=E2=80=A6 > > I think a solution would be to remove the repeater from timestamps > inserted upon logging a state change or a re-scheduling. > > However, you would have to fix your old documents manually. > > Regards, Hi Nicholas, I think this commit is a problem: af81211fd (Also obey to repeaters in inactive time stamps, 2018-11-10) At the beginning of the year I close my repeating tasks with lots of logging and clocking entries and create a new one as follows: 1) Clone repeating task to new task for next year 2) Unscheduled old task which writes the scheduled repeater to the log as above 3) Mark old task DONE=20 Step 3 fails. It moves the repeater in the log message from the old scheduled task makes the task TODO again. Example: ---------------------------------------------------------------------------= ----- * TODO Sample repeating task 2018 SCHEDULED: <2019-01-07 Mon ++1w> :LOGBOOK: - Note taken on [2019-01-07 Mon 09:44] \\ Log note 2 - Note taken on [2019-01-07 Mon 09:44] \\ Log note 1 :END: [2019-01-07 Mon 09:44] ---------------------------------------------------------------------------= ----- Now clone the task with C-c C-x c 1 RET RET ---------------------------------------------------------------------------= ----- * TODO Sample repeating task 2018 SCHEDULED: <2019-01-07 Mon ++1w> :LOGBOOK: - Note taken on [2019-01-07 Mon 09:44] \\ Log note 2 - Note taken on [2019-01-07 Mon 09:44] \\ Log note 1 :END: [2019-01-07 Mon 09:44] * TODO Sample repeating task 2018 SCHEDULED: <2019-01-07 Mon ++1w> :LOGBOOK: - Note taken on [2019-01-07 Mon 09:44] \\ Log note 2 - Note taken on [2019-01-07 Mon 09:44] \\ Log note 1 :END: [2019-01-07 Mon 09:44] ---------------------------------------------------------------------------= ----- Rename the second task to 2019 and unschedule the first task: ---------------------------------------------------------------------------= ----- * TODO Sample repeating task 2018 :LOGBOOK: - Not scheduled, was "[2019-01-07 Mon ++1w]" on [2019-01-07 Mon 09:47] - Note taken on [2019-01-07 Mon 09:44] \\ Log note 2 - Note taken on [2019-01-07 Mon 09:44] \\ Log note 1 :END: [2019-01-07 Mon 09:44] * TODO Sample repeating task 2019 SCHEDULED: <2019-01-07 Mon ++1w> :LOGBOOK: - Note taken on [2019-01-07 Mon 09:44] \\ Log note 2 - Note taken on [2019-01-07 Mon 09:44] \\ Log note 1 :END: [2019-01-07 Mon 09:44] ---------------------------------------------------------------------------= ----- And finally Mark the first task DONE ---------------------------------------------------------------------------= ----- * TODO Sample repeating task 2018 :PROPERTIES: :LAST_REPEAT: [2019-01-07 Mon 09:48] :END: :LOGBOOK: - State "DONE" from "TODO" [2019-01-07 Mon 09:48] - Not scheduled, was "[2019-01-14 Mon ++1w]" on [2019-01-07 Mon 09:47] - Note taken on [2019-01-07 Mon 09:44] \\ Log note 2 - Note taken on [2019-01-07 Mon 09:44] \\ Log note 1 :END: [2019-01-07 Mon 09:44] * TODO Sample repeating task 2019 SCHEDULED: <2019-01-07 Mon ++1w> :LOGBOOK: - Note taken on [2019-01-07 Mon 09:44] \\ Log note 2 - Note taken on [2019-01-07 Mon 09:44] \\ Log note 1 :END: [2019-01-07 Mon 09:44] ---------------------------------------------------------------------------= ----- The first task should now be DONE not TODO but instead it has updated the repeater in the log message from unscheduling instead and it's not possible to mark this task as DONE with C-c C-t anymore. Should this problem commit be reverted? af81211fd (Also obey to repeaters in inactive time stamps, 2018-11-10) Regards, Bernt