From: Ivan Nedrehagen <ivannedr@broadpark.no>
To: Chris Gray <chrismgray@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Re: The recurring task pattern
Date: Thu, 04 Jun 2009 12:50:10 +0200 [thread overview]
Message-ID: <op.uuzxpwk2etmi9u@gorontha.conoptica.local> (raw)
In-Reply-To: <863aahy9ro.fsf@portan.ibr.cs.tu-bs.de>
På Wed, 03 Jun 2009 10:57:47 +0200, skrev Chris Gray
<chrismgray@gmail.com>:
> Ivan Nedrehagen wrote:
>
>> Hi everyone, I have a pattern that repeats itself in org-mode and I am
>> wondering if anyone have any solutions to it.
>
>> I have some tasks that must be done each week, it does not matter when
>> I complete them, but they must be done before end of the week. And
>> when the next week comes the task should be repeated.
>
>> Now I have an TODO item on it and I flip it back and forth from TODO
>> to DONE, but it requires me to remember that I have completed the
>> task, and requires me to put it back to TODO next week. This is not
>> working very well.
>
>> What I would like:
>> At the beginning of each week the task sets itself to TODO.
>> When I complete it, it logs the state change (only for this state, I
>> do not want state change logging on all).
>> A reminder that I did not complete it last week would be nice, but I
>> expect that to be too much to ask for.
>
> You can add a deadline that repeats every week for the task.
>
> ** TODO Do weekly task
> DEADLINE: <2009-06-03 Wed +1w>
>
> Cheers,
> Chris
>
>
Yes this does almost do the trick, but with one annoying feature.
It changes the state back to TODO immediatly after it is done so
it still shows up in my agenda as a TODO item. So it looks for me like
I never have done my repeating items, and I have to check the date to
be sure.
But it is perhaps difficult to make it change state later on?
It could be fixed with a more advanced custom agenda command i guess.
next prev parent reply other threads:[~2009-06-04 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 8:50 The recurring task pattern Ivan Nedrehagen
2009-06-03 8:57 ` Chris Gray
2009-06-03 9:24 ` Mikael Fornius
2009-06-04 10:50 ` Ivan Nedrehagen [this message]
2009-06-05 1:40 ` Matthew Lundin
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=op.uuzxpwk2etmi9u@gorontha.conoptica.local \
--to=ivannedr@broadpark.no \
--cc=chrismgray@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).