From: Bernt Hansen <bernt@norang.ca>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: DONE repeating events become TODO, not OTHER
Date: Wed, 23 Sep 2015 13:10:06 -0400 [thread overview]
Message-ID: <87k2rhdpu9.fsf@norang.ca> (raw)
In-Reply-To: <87pp1irqov.fsf@alphaville.usersys.redhat.com> (Nick Dokos's message of "Wed, 16 Sep 2015 17:37:36 -0400")
Nick Dokos <ndokos@gmail.com> writes:
> Ken Mankoff <mankoff@gmail.com> writes:
>
>> I have repeating events of type OTHER, as in:
>>
>> * OTHER Foo
>> <2015-09-16 +1w>
>>
>> When I have finished the task for today, I mark it done. Because it is
>> a repeating event, it doesn't actually change to DONE, instead it
>> changes to TODO and adds a :LAST_REPEAT: item in the :PROPERTIES:
>> drawer.
>>
>> How do I tell this specific item, or all OTHER items in general, that
>> after completion it should remain OTHER rather than changing to TODO?
>>
>
> Do you *have* to have a TODO state? If not,
>
> #+TODO: OTHER | DONE
>
> should do the trick. Or you could use multiple
> sets:
>
> #+TODO: TODO INPROGRESS | DONE
> #+TODO: OTHER | COMPLETED
>
> In the latter case, the keywords all have to be different.
> See
>
> (info "(org) TODO items")
Or after defining OTHER has a todo keyword add a property specifying
which next state you want
* OTHER Foo
:PROPERTIES:
:REPEAT_TO_STATE: OTHER
:END:
<2015-09-16 +1w>
Regards,
Bernt
prev parent reply other threads:[~2015-09-23 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 21:18 DONE repeating events become TODO, not OTHER Ken Mankoff
2015-09-16 21:37 ` Nick Dokos
2015-09-16 22:21 ` Ken Mankoff
2015-09-17 1:30 ` Nick Dokos
2015-09-23 17:10 ` Bernt Hansen [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=87k2rhdpu9.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@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 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).