From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Repeating tasks with scheduled time Date: Wed, 05 Oct 2016 08:39:07 +0200 Message-ID: <87d1jfpaes.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40080) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1brfrF-0007wp-DZ for emacs-orgmode@gnu.org; Wed, 05 Oct 2016 02:39:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1brfrB-0001zM-9c for emacs-orgmode@gnu.org; Wed, 05 Oct 2016 02:39:12 -0400 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:59926) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1brfrB-0001yy-3h for emacs-orgmode@gnu.org; Wed, 05 Oct 2016 02:39:09 -0400 In-Reply-To: (Arkady Grudzinsky's message of "Tue, 04 Oct 2016 15:58:41 -0700") 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: Arkady Grudzinsky Cc: emacs-orgmode@gnu.org 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. Regards, -- Nicolas Goaziou