Re: [O] Customizing org-todo-repeat-to-state to return to the current TODO state
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) Best regards, Seb -- Sebastien Vauban
Re: [O] Customizing org-todo-repeat-to-state to return to the current TODO state
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
Re: [O] Customizing org-todo-repeat-to-state to return to the current TODO state
Grant Schissler grant.schiss...@gmail.com writes: Hi Org-mode Users, 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. Thanks for the support and to all those that make org-mode great! Grant Hi Grant. This is what I have for a repeating task every Friday morning. --8---cut here---start-8--- ** TODO Hancock's half hour, new programmes on Radio 4 SCHEDULED: 2014-11-28 Fri 11:30 +7d - State DONE from TODO [2014-11-21 Fri 18:11] - State DONE from TODO [2014-11-14 Fri 12:18] - State DONE from TODO [2014-11-02 Sun 08:34] :LOGBOOK: - State DONE from TODO [2014-11-07 Fri 13:57] - State DONE from TODO [2014-11-01 Sat 10:06] :END: :PROPERTIES: :LAST_REPEAT: [2014-11-21 Fri 18:11] :END: --8---cut here---end---8--- To progress it from TODO via DONE and back to TODO, I do C-c t d and its all set up for the next week. Hope this helps Sharon. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, fluxbox 1.3.5, emacs 24.4.1.0 signature.asc Description: PGP signature
Re: [O] Customizing org-todo-repeat-to-state to return to the current TODO state
Sorry, I wasn't clear what I meant by fixed state. I want to avoid globally changing the repeat-to-state and flexibly return to the current state. Thanks for the suggestion though On Fri, Nov 21, 2014 at 1:02 PM, Sebastien Vauban sva-n...@mygooglest.com wrote: 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) Best regards, Seb -- Sebastien Vauban -- A. Grant Schissler, M.S GIDP Statistics, University of Arizona Research Assistant, Lussier Lab
Re: [O] Customizing org-todo-repeat-to-state to return to the current TODO state
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 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
Re: [O] Customizing org-todo-repeat-to-state to return to the current TODO state
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
Re: [O] Customizing org-todo-repeat-to-state to return to the current TODO state
Grant Schissler grant.schiss...@gmail.com writes: 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. The property thingie is a very fine scalpel: if you have a few of these APPT headings, then it's probably the way to go. See (info (org) TODO extensions), in particular the Multiple keyword sets in one file subsection for a different way. But honestly, I have enough appointments and they are so different from anything else, that a separate file makes sense for me. -- Nick
