From: Grant Schissler <grant.schissler@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Customizing org-todo-repeat-to-state to return to the current TODO state
Date: Fri, 21 Nov 2014 13:39:34 -0700 [thread overview]
Message-ID: <CAMc14AZ8O=Sz6gA5OHwdpGvAoqvfzfUdydsExyqOnAgS4pgAbw@mail.gmail.com> (raw)
In-Reply-To: <87tx1ss460.fsf@alphaville.bos.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2041 bytes --]
That is a nice workaround, but does anyone have any ideas that I could
continue to use my main org file? Also, what is meant by "the previous
state in TYPO_TYP set"? Thank you very much for the suggestion.
On Fri, Nov 21, 2014 at 1:13 PM, Nick Dokos <ndokos@gmail.com> wrote:
> Sebastien Vauban <sva-news@mygooglest.com>
> writes:
>
> > Grant Schissler wrote:
> >> I am trying to change the behavior of marking a repeated task as DONE.
> I
> >> would like the task to return to the current TODO state rather than the
> >> first in the TODO sequence or a fixed state. For example,
> >>
> >> ** APPT Lunch with Mallorie
> >> <2014-12-04 Thu 12:00 +1w>
> >>
> >> Should return to APPT, not TODO or some other predefined state as in the
> >> current behavior:
> >>
> >> TODO Lunch with Mallorie
> >> - State "DONE" from "APPT" [2014-11-21 Fri 10:56]
> >> <2014-12-11 Thu 12:00 +1w>
> >>
> >> I am sure that customizing the org-todo-repeat-to-state will do the
> trick,
> >> but sadly, I have had the time to learn elisp well enough to perform
> this.
> >>
> >> Any help would be much appreciated. Please let me know if you have
> >> questions.
> >
> > ;; TODO state to which a repeater should return the repeating task.
> > (setq org-todo-repeat-to-state "APPT")
> >
>
> That may not be the best solution however: it would change it globally,
> so *every* repeater would go back to APPT.
>
> C-h v org-todo-repeat-to-state RET says:
>
> ,----
> | The TODO state to which a repeater should return the repeating task.
> | By default this is the first task in a TODO sequence, or the previous
> state
> | in a TODO_TYP set. But you can specify another task here.
> | alternatively, set the :REPEAT_TO_STATE: property of the entry.
> `----
>
> so setting the property of the entry might be better.
>
> Personally, I have my appointments in a separate file with its own
> TODO sequence:
>
> #+TODO: APPT | DONE
>
> Nick
>
>
>
--
A. Grant Schissler, M.S
GIDP Statistics, University of Arizona
Research Assistant, Lussier Lab
[-- Attachment #2: Type: text/html, Size: 2962 bytes --]
next prev parent reply other threads:[~2014-11-21 20:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 19:14 Customizing org-todo-repeat-to-state to return to the current TODO state Grant Schissler
2014-11-21 20:02 ` Sebastien Vauban
2014-11-21 20:13 ` Nick Dokos
2014-11-21 20:39 ` Grant Schissler [this message]
2014-11-21 21:14 ` Nick Dokos
2014-11-21 20:41 ` Grant Schissler
2014-11-21 20:36 ` Grant Schissler
2014-11-21 20:18 ` Sharon Kimble
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='CAMc14AZ8O=Sz6gA5OHwdpGvAoqvfzfUdydsExyqOnAgS4pgAbw@mail.gmail.com' \
--to=grant.schissler@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).