From mboxrd@z Thu Jan 1 00:00:00 1970 From: Justin Vallon Subject: Recurring TODO with hours not scheduled correctly Date: Tue, 3 Dec 2019 01:03:03 -0500 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:41261) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ic1HL-0001aa-PD for emacs-orgmode@gnu.org; Tue, 03 Dec 2019 01:03:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ic1HK-0000dL-Hm for emacs-orgmode@gnu.org; Tue, 03 Dec 2019 01:03:19 -0500 Received: from mail-qt1-x832.google.com ([2607:f8b0:4864:20::832]:33722) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ic1HK-0000ba-2n for emacs-orgmode@gnu.org; Tue, 03 Dec 2019 01:03:18 -0500 Received: by mail-qt1-x832.google.com with SMTP id d5so2656041qto.0 for ; Mon, 02 Dec 2019 22:03:17 -0800 (PST) Received: from tzzpccd.dnsalias.net (pool-72-89-125-139.nycmny.fios.verizon.net. [72.89.125.139]) by smtp.gmail.com with ESMTPSA id p35sm1142301qtd.12.2019.12.02.22.03.08 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 Dec 2019 22:03:11 -0800 (PST) Content-Language: en-US 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 Newbie org-mode user. Wondering about some odd recurrence behavior. emacs --no-init-file # test.org * TODO shovel snow M-x org-schedule RET RET * TODO shovel show SCHEDULED: <2019-12-03 Tue> Add time: * TODO shovel show SCHEDULED: <2019-12-03 Tue 09:00 .+1h> Complete: C-c C-t * TODO shovel show SCHEDULED: <2019-12-03 Tue 10:00 .+1h> :PROPERTIES: :LAST_REPEAT: [2019-12-03 Tue 00:52] :END: - State "DONE" from "TODO" [2019-12-03 Tue 00:52] Again: complete: C-c C-t * TODO shovel show SCHEDULED: <2019-12-03 Tue 11:00 .+1h> :PROPERTIES: :LAST_REPEAT: [2019-12-03 Tue 00:57] :END: - State "DONE" from "TODO" [2019-12-03 Tue 00:57] - State "DONE" from "TODO" [2019-12-03 Tue 00:52] My understanding of .+TERM is that the new scheduled time should be now + term. However, from this instance and testing with other terms, it seems to be "current date + scheduled-time" + HOURS. Completing again advances the time by one hour, leaving the date as today. For ".+2d", the new scheduled date/time is 2d away (at the same time), and re-completing does not change the new schedule time. (equal org-version "9.1.9") --=20 -Justin JustinVallon@gmail.com