From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Wahl Subject: Re: [feature] Handle recurrence in <> and [] dates Date: Wed, 14 Nov 2018 16:29:40 +0100 Message-ID: <848t1vllsr.fsf@gmail.com> References: <87tvldzzn8.fsf@llwynog.ekleog.org> <8736segzal.fsf@llwynog.ekleog.org> <776968cf-5976-4648-4f24-93eb506abbfa@gmx.de> <87muqmff3b.fsf@llwynog.ekleog.org> <87muqgbvus.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54143) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gMx78-0004QZ-BH for emacs-orgmode@gnu.org; Wed, 14 Nov 2018 10:29:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gMx75-0001ZB-MY for emacs-orgmode@gnu.org; Wed, 14 Nov 2018 10:29:58 -0500 Received: from [195.159.176.226] (port=40607 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gMx75-0001Wv-Ee for emacs-orgmode@gnu.org; Wed, 14 Nov 2018 10:29:55 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1gMx4q-0008E2-Js for emacs-orgmode@gnu.org; Wed, 14 Nov 2018 16:27:36 +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: emacs-orgmode@gnu.org Hi! > Leo Gaspard writes: > >> Here is a translated example task from my .org file: >> >> *** TODO Check bank report >> SCHEDULED: <2000-02-10 Thu +1m> >> >> Dated [2000-01-01 Sat +1m] >> >> The point of this “Dated” field being to tell me to which report I >> should be looking, given I sometimes am a month late or so in checking >> my reports, and just put them in the (physical) drawer as I receive >> them. >> >> This “Dated” field is exactly what I would like to see updated when I >> mark the task as done (like the SCHEDULED date), but it looks like it >> doesn't move. > > Org didn't handle repeaters in inactive time stamps. This is now fixed > (in master). Thank you. AFAICT the performance of marking tasks done which contain *a lot* of inactive timestams has degraded considerably with this change. Example: #v+ * TODO task SCHEDULED: <2018-11-15 .+1d> :PROPERTIES: :STYLE: habit :LAST_REPEAT: [2018-11-14 16:26] :END: [2018-07-10 Tue 11:29]--[2018-07-10 Tue 12:10] [2018-07-09 Mon 15:20]--[2018-07-09 Mon 15:23] [2018-07-08 Sun 09:01]--[2018-07-08 Sun 09:20] ... ... [2013-07-08 Sun 09:01]--[2013-07-08 Sun 09:20] #v- Sorry for not having digged deeper into this issue yet. Ciao, Marco