emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Robert Goldman <rpgoldman@sift.info>
Cc: emacs-orgmode@gnu.org
Subject: Re: Archiving and not archiving...
Date: Wed, 11 Mar 2009 16:42:29 +0100	[thread overview]
Message-ID: <314E1BE7-D490-4A29-9C0D-3C9BA2F02BF9@uva.nl> (raw)
In-Reply-To: <49B7D98D.4040801@sift.info>

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

      reply	other threads:[~2009-03-11 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 20:56 Archiving and not archiving Robert Goldman
2009-03-11 15:07 ` Carsten Dominik
2009-03-11 15:32   ` Robert Goldman
2009-03-11 15:42     ` Carsten Dominik [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=314E1BE7-D490-4A29-9C0D-3C9BA2F02BF9@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=rpgoldman@sift.info \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).