From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arkady Grudzinsky Subject: Re: Repeating tasks with scheduled time Date: Wed, 05 Oct 2016 13:06:29 -0700 Message-ID: References: <87d1jfpaes.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51487) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1brsTG-0006o2-Jf for emacs-orgmode@gnu.org; Wed, 05 Oct 2016 16:07:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1brsTD-0002Xg-CM for emacs-orgmode@gnu.org; Wed, 05 Oct 2016 16:07:18 -0400 Received: from [195.159.176.226] (port=49410 helo=blaine.gmane.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1brsTD-0002Wh-5A for emacs-orgmode@gnu.org; Wed, 05 Oct 2016 16:07:15 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1brsSe-0007vp-JW for emacs-orgmode@gnu.org; Wed, 05 Oct 2016 22:06:40 +0200 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 On Wed, Oct 05 2016, Nicolas Goaziou wrote: > Hello, > > Arkady Grudzinsky writes: > >> On Tue, Oct 04 2016, Arkady Grudzinsky wrote: >> >>> Say, I have this TODO item which needs to be repeated every >>> evening after 20:00 and if it is not marked as DONE for several >>> days, I want it to be moved to the NEAREST 20:00 in the future, >>> i.e. to 20:00 TODAY if I mark it at noon. I thought, this would >>> accomplish the goal: >>> >>> * TODO Load and run the dishwasher >>> SCHEDULED: <2016-10-03 Mon 20:00 .+1d> >> >> Sorry, the correct syntax would be >> >> * TODO Load and run the dishwasher >> SCHEDULED: <2016-10-03 Mon 20:00 ++1d> >> >> It still moves the scheduled time to the next day instead of >> 20:00 today. >> >> >>> >>> Instead, marking this task as completed today at noon moves the >>> schedule to 20:00 TOMORROW instead of 20:00 TODAY although the >>> nearest 20:00 in the future is, technically, 20:00 TODAY. >>> >>> Is there a way to change this behavior? > > IIRC this was fixed in development version, i.e., Org 9.0. Thanks. I have 8.2 installed. Do you know when 9.0 will be released? -- Arkady