Sorry, Nick. I understand your point better now. It may take a lot of reorganizing, but I will let you know if I find something that works for me. Thanks
On Fri, Nov 21, 2014 at 1:13 PM, Nick Dokos <ndo...@gmail.com> wrote: > Sebastien Vauban <sva-n...@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
