Thanks Nicolas for your reply. I am using Org 8.3.4. The clocking works fine for me and so do recurring state changes. Basic functioning is OK for me.
Currently, I follow these steps: 1. I don't clock these recurring tasks 2. mark the recurring task as done 3. manually copy the clock data 4. and use M-S-<up> to change the clock data to the current date I was seeing if the above process can be automated or cleverly done thru elisp code. I am not adept at elisp, so I was wondering if anyone else had done this. Thanks and have a great day! Bala http://balaramadurai.net On Wed, Oct 5, 2016 at 12:13 PM, Nicolas Goaziou <[email protected]> wrote: > Hello, > > Bala Ramadurai <[email protected]> writes: > > > I use org-mode for scheduling and logging in tasks. I clock in > > non-recurring tasks, however I find it strenuous to clock in recurring > > tasks. Is there any way I can mark the recurring task done and the > > scheduled time for the task is converted into clocked data as soon as I > > mark it done? > > > > Example, > > > > * TODO Task 1 > > SCHEDULED: <2016-10-04 Tue 10:00-10:30 ++1d> > > > > After I mark it done, the task should read > > > > * TODO Task 1 > > SCHEDULED: <2016-10-05 Wed 10:00-10:30> > > :LOGBOOK: > > - State "DONE" from "TODO" [2016-10-04 Tue 11:42] > > CLOCK: [2016-10-04 Tue 10:00]--[2016-10-04 Tue 10:30] => 0:30 > > :END: > > Could you expunge a bit? What happens instead? What is your > configuration and the Org version you're using? In particular, did you > try the latest one? > > Regards, > > -- > Nicolas Goaziou >
