From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: please read: bug when marking tasks done Date: Mon, 07 Jan 2019 00:49:52 +0100 Message-ID: <87wonhcpnj.fsf@nicolasgoaziou.fr> References: <87d0paprs6.fsf@gnu.org> 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]:38436) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ggIB3-0007Hs-4m for emacs-orgmode@gnu.org; Sun, 06 Jan 2019 18:49:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ggIB2-0001Lx-6g for emacs-orgmode@gnu.org; Sun, 06 Jan 2019 18:49:57 -0500 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:52467) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ggIB1-0001KD-7x for emacs-orgmode@gnu.org; Sun, 06 Jan 2019 18:49:56 -0500 In-Reply-To: <87d0paprs6.fsf@gnu.org> (cesar mena's message of "Sat, 05 Jan 2019 19:13:13 -0500") 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 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 08= :35] > - - Rescheduled from "[2018-11-25 Sun .+1m]" on [2018-11-25 Sun 09= :17] > - - Rescheduled from "[2018-11-20 Tue .+1m]" on [2018-11-22 Thu 10= :03] > - - Rescheduled from "[2018-11-13 Tue .+1m]" on [2018-11-17 Sat 09= :48] > - - Rescheduled from "[2018-11-06 Tue .+1m]" on [2018-11-08 Thu 07= :02] > - - Rescheduled from "[2018-10-28 Sun .+1m]" on [2018-10-30 Tue 16= :22] > - - Rescheduled from "[2018-10-25 Thu .+1m]" on [2018-10-25 Thu 07= :34] > - - Rescheduled from "[2018-10-19 Fri .+1m]" on [2018-10-19 Fri 07= :48] > - - Rescheduled from "[2018-10-16 Tue .+1m]" on [2018-10-16 Tue 16= :21] > - - Rescheduled from "[2018-10-11 Thu .+1m]" on [2018-10-14 Sun 10= :31] > - - Rescheduled from "[2018-10-07 Sun .+1m]" on [2018-10-08 Mon 08= :48] > - - Rescheduled from "[2018-09-27 Thu .+1m]" on [2018-09-29 Sat 18= :50] > - - Rescheduled from "[2018-09-20 Thu .+1m]" on [2018-09-20 Thu 09= :50] > - - Rescheduled from "[2018-09-08 Sat .+1m]" on [2018-09-14 Fri 07= :10] > + - State "DONE" from "TODO" [2019-01-05 Sat 18:47] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-28 Wed 08= :35] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-25 Sun 09= :17] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-22 Thu 10= :03] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-17 Sat 09= :48] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-08 Thu 07= :02] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-30 Tue 16= :22] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-25 Thu 07= :34] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-19 Fri 07= :48] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-16 Tue 16= :21] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-14 Sun 10= :31] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-08 Mon 08= :48] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-29 Sat 18= :50] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-20 Thu 09= :50] > + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-14 Fri 07= :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, --=20 Nicolas Goaziou