emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marco Wahl <marcowahlsoft@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: mark as done on a previous date?
Date: Wed, 04 Jan 2017 18:40:32 +0100	[thread overview]
Message-ID: <84r34iaflb.fsf@gmail.com> (raw)
In-Reply-To: m2pok9gynz.fsf@Margil.home

> Interesting. I couldn't get yours to work as I expected either, and
> decided to try =org-todo-yesterday=, and couldn't get _that_ to work as
> I expected either, which I thought was strange so I dug a bit deeper. I
> tested with =emacs -q foo.org= and added the following entry (I did this
> on the 30th of December):
>
> ,----
> | * TODO Testing 123
> |   SCHEDULED: <2016-12-27 Tue .+1m>
> |   :PROPERTIES:
> |   :STYLE:    habit
> |   :END:
> `----
>
> After using =org-todo-yesterday= I ended up with:
>
> ,----
> | * TODO Testing 123
> |   SCHEDULED: <2017-01-29 Sun .+1m>
> |   - State "DONE"       from "TODO"       [2016-12-30 Fri 16:29]
> |   :PROPERTIES:
> |   :STYLE:    habit
> |   :LAST_REPEAT: [2016-12-30 Fri 16:29]
> |   :END:
> `----
>
> I now see (finally!) that the *re-scheduling* works as I would expect,
> but the LAST_REPEAT and state change logging still uses the actual time.
> I would have expected both those to use the 29th rather than the 30th as
> well. Perhaps this is just my expectation that needs adjusting, but this
> breaks org-habit's graphing of my consistency. Perhaps I just have to
> get in the habit of ticking stuff off on the day I do them... :-)

Hi Stig,

I think your expectation is right.  There is another thread in this
mailing list about the same topic AFAICT.  Hopefully something reliable
will emerge.


Ciao

      reply	other threads:[~2017-01-04 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29 13:12 mark as done on a previous date? Stig Brautaset
2016-12-30 12:14 ` Marco Wahl
2016-12-30 16:38   ` Stig Brautaset
2017-01-04 17:40     ` Marco Wahl [this message]

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=84r34iaflb.fsf@gmail.com \
    --to=marcowahlsoft@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).