emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Justin Vallon <justinvallon@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Recurring TODO with hours not scheduled correctly
Date: Tue, 3 Dec 2019 01:03:03 -0500	[thread overview]
Message-ID: <dd7576f2-e3c6-478c-45e3-c5fc0a99412a@gmail.com> (raw)

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")

-- 
-Justin
JustinVallon@gmail.com

             reply	other threads:[~2019-12-03  6:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03  6:03 Justin Vallon [this message]
2019-12-07 16:00 ` PATCH: Re: Recurring TODO with hours not scheduled correctly Justin Vallon
2019-12-12 11:16   ` Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dd7576f2-e3c6-478c-45e3-c5fc0a99412a@gmail.com \
    --to=justinvallon@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).