From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lindsay Todd Subject: Cloning tasks subtrees when repeating? Date: Mon, 16 May 2011 14:35:47 -0400 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([140.186.70.92]:60096) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QM2dy-0007Pl-Mg for emacs-orgmode@gnu.org; Mon, 16 May 2011 14:35:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QM2dx-0005jx-DU for emacs-orgmode@gnu.org; Mon, 16 May 2011 14:35:50 -0400 Received: from mail-gx0-f169.google.com ([209.85.161.169]:63148) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QM2dx-0005jd-B5 for emacs-orgmode@gnu.org; Mon, 16 May 2011 14:35:49 -0400 Received: by gxk23 with SMTP id 23so1999217gxk.0 for ; Mon, 16 May 2011 11:35:48 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: org-mode Folks: I am looking for a nice org-mode-ish way to manage a task check list that repeats regularly. I would like to log, then archive, which items actually are completed when I close the task. (It isn't uncommon to have a few open.) Here is the situation: Every couple of weeks, I have an opportunity to work through a checklist of about 40-50 system maintenance tasks, organized under a repeating TODO-task item. At the end of the maintenance time period, I close the task (which reschedules nicely), then cut-n-paste the partly-marked list to the LOGBOOK drawer (as well as any additional notes I want to log). Then I manually clear out the check list... This is not too much work, but of course it would be nice if the checklist could automatically be saved, then cleared. But there is another problem: my LOGBOOK drawer is getting very large, and checklist processing has been slowing (I can no longer use it). What would be nice is if I could close the task, the repeated entry would be an entirely new task. Perhaps it is a clone of the task I just closed (with a new date), or perhaps it is populated from some sort of template. The important thing is I need a new task entry, so I can archive the old entry, and still have a new entry with a new date. Has anyone else had a similar use-case that could suggest an approach they've used? Thanks! /Lindsay