From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Archiving and not archiving... Date: Wed, 11 Mar 2009 16:42:29 +0100 Message-ID: <314E1BE7-D490-4A29-9C0D-3C9BA2F02BF9@uva.nl> References: <49B6D412.9060203@sift.info> <7D769F3A-D705-461C-85FC-2E21CE04C0D9@uva.nl> <49B7D98D.4040801@sift.info> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LhQZo-0001bY-GQ for emacs-orgmode@gnu.org; Wed, 11 Mar 2009 11:42:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LhQZl-0001XI-DY for emacs-orgmode@gnu.org; Wed, 11 Mar 2009 11:42:34 -0400 Received: from [199.232.76.173] (port=58149 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LhQZl-0001X0-6X for emacs-orgmode@gnu.org; Wed, 11 Mar 2009 11:42:33 -0400 Received: from ey-out-1920.google.com ([74.125.78.146]:65527) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LhQZk-0000OP-MO for emacs-orgmode@gnu.org; Wed, 11 Mar 2009 11:42:32 -0400 Received: by ey-out-1920.google.com with SMTP id 4so10379eyg.24 for ; Wed, 11 Mar 2009 08:42:31 -0700 (PDT) In-Reply-To: <49B7D98D.4040801@sift.info> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Robert Goldman Cc: emacs-orgmode@gnu.org On Mar 11, 2009, at 4:32 PM, Robert Goldman wrote: > Carsten Dominik wrote: >> >> On Mar 10, 2009, at 9:56 PM, Robert Goldman wrote: >> >>> [My apologies in advance if this is a FAQ.] >>> >>> I have a bunch of Org files in which I have tasks some of which >>> involve >>> doing something for work (trivial or non-trivial), and some of which >>> involve doing something for home (trivial like picking up laundry or >>> more important like doing a call to a company that needs to be >>> logged). >>> >>> My question has to do with archiving. I archive my tasks to >>> separate >>> archive files. What I'd really like to be able to do is to identify >>> some tasks as being worth archiving (calling a company to request >>> them >>> to fix a billing error, for example), and some of which are not >>> (picking >>> up the dry cleaning, returning library books). >>> >>> Does anyone have a technique for marking tasks so that they get >>> electively archived when one uses one of the archiving commands? >> >> Hmm, this really seems to make sense only if you are using a command >> that scans the buffer for DONE tasks and archives all of them. Is >> that >> what you do? > > I typically have all of my tasks in a top-level headline, * Tasks, and > then use the subtree archiving command. That is really equivalent to > what you say here --- it scans the buffer and (prompting me for > agreement) archives all of the tasks. > >> >> One possibility is to give tasks their own ARCHIVE property which >> could >> point to a garbage file for boring tasks. > > Right, or (I think) I could have one archive file, with two top-level > items, > > * Interesting Tasks > and > * Boring Tasks > > and selectively archive to one or the other. > > Probably this is too much trouble, since it would bloat up each of the > individual tasks. > > Alternatively, in the org file that contains all my chores, I could > have > a top-level "chores" headline, in addition to my top-level tasks > headline, I could put ARCHIVE properties on each one, and have two > different remember templates, one for routine chores and one for more > interesting tasks.... >> >> I myself archive everything. I don't care how big the archive gets >> because I only need to look at it if I need to find something >> back. Who >> cares how big this file is. > > Possibly that's the right answer. I was just concerned that I might > want something back and not be able to get it because it was > surrounded > with a bunch of "pick up laundry" tasks... In this case, tag important tasks with some tag like :important: and do a sparse tree search for this tag in the archive file. C-c \ important RET Also, Org stores a lot of context info with the task as properties. If you remember that the task you are looking for had the "important" tag and used to be a subtask of * Tasks ** Financial then you can do a tag search with C-c \ +important+OLPATH="Task/Finance" RET Archive files are org files, and all the searching facilities are available there. - Carsten