From: Stig Brautaset <stig@brautaset.org>
To: Marco Wahl <marcowahlsoft@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: mark as done on a previous date?
Date: Fri, 30 Dec 2016 16:38:24 +0000 [thread overview]
Message-ID: <m2pok9gynz.fsf@Margil.home> (raw)
In-Reply-To: <84eg0p7gw3.fsf@gmail.com>
Marco Wahl <marcowahlsoft@gmail.com> writes:
> Hi!
>
>> I'm trying to use org-habit to track my habits and sometimes I don't
>> get around to mark stuff as done on the day I do them. I've found two
>> different functions for marking stuff as done in the past, but I can't
>> get either of them to work.
>> [...]
[...]
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... :-)
Stig
next prev parent reply other threads:[~2016-12-30 16:38 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 [this message]
2017-01-04 17:40 ` Marco Wahl
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2pok9gynz.fsf@Margil.home \
--to=stig@brautaset.org \
--cc=emacs-orgmode@gnu.org \
--cc=marcowahlsoft@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.