From: Russell Adams <RLAdams@AdamsInfoServ.Com>
Subject: Re: Overall organization/setup for org mode: Projects and Tasks
Date: Wed, 14 Sep 2011 13:40:09 -0500 [thread overview]
Message-ID: <20110914184009.GH2773@x201> (raw)
On Wed, Sep 14, 2011 at 10:43:28AM -0700, Alan E. Davis wrote:
> I've been using org-mode for a few years. My agenda is cluttered with tasks
> that are weeks and even months past due. I am "this close" to declaring
> "orgmode bankruptcy" and starting from scratch, except my current setup
> works so well for other things. Might still do that, but I want to ask for
> I stumble consistently over the distinction between projects and tasks. I
> think there is not clear distinction, but I need to find a way to organize
> them so that, at least, agenda displays the day to day TODO tasks separated
> in a meaningful way from the long term projects that I need to remind myself
> of (and there are dozens of these).
> PROJECTS: I can define projects as
> - an overall series of tasks related to a single purpose
> - a recurring task (monthly calendars that I need to remind myself to
> make each month)
> - an actual project I am working on (writing a proposal, or a
> research project about a coral, or a recipe database, or reconstructing a
> LaTeX file tree for a publication ten years ago)
> TODOS: perhaps tasks could be anything,
> - bills (marked by tag "bill"
> - phone calls to make
> I am starting to understand how I TODOS can be scattered through all my
> other files. However, the greater the number of agenda files, the greater
> the clutter. And, as a recent thread called to mind, there are times when
> the list of agenda files prevents me from searching for tags or todos. SO
> where is the happy medium?
> Some thoughts:
> - I tried to write a custom agenda command that defined the agenda
> files to encompass all *org files in a directory. This actually set the
> agenda-files variable to all files for the rest of the session, so I gave
> that idea up----although I know it's possible to do it.
> - Again, the number of agenda files seems to be constraining.
> - There seem to be issues between defining the agenda files
> explicitly, or adding them one at a time.
> - It would be useful if agenda searches automatically picked up the
> recent files I had worked on during the session,
> however, in as streamlined a way as possible.
> I don't need to be reminded everyday that I have to organize bibliographic
> references for my next trip to the library, but I have to have a way to keep
> these organized to jog my memory in planning my time in some loose sense.
> I do need to have a list of bills that I can access without having to sort
> through the list of projects that are 3 months overdue.
> Almost every week I have new insights into how to use tags, so perhaps I
> need to junk alot of the tags I set up long ago.
> These thoughts are somewhat disconnected, and I apologize for this.
> And I would be grateful for any comments that would shed light on how to
> solve these issues.
> Alan Davis
I keep two main Org files (Biz, Personal) which are the only two files
in my agenda. I use Capture almost exclusively to add to these files.
Every project I do is a separate Org file, which I timestamp heavily
but I don't typically add them to my agenda. If they need an agenda
item, I may temporarily add them to the agenda, or put an entry in my
main pair of files.
This really keeps the clutter down. I can run agenda inside a project
by restricting agenda to the current file.
I hope that helps.
Russell Adams RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
next prev parent reply other threads:[~2011-09-14 18:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 17:43 Alan E. Davis
2011-09-14 18:26 ` Thomas S. Dye
2011-09-14 18:40 ` Russell Adams [this message]
2011-09-14 20:00 ` Martyn Jago
2011-09-14 22:50 ` Russell Adams
2011-09-14 18:59 ` Olaf Dietsche
2011-09-14 21:04 ` Christian Moe
2011-09-14 21:49 ` Darlan Cavalcante Moreira
2011-09-17 19:32 ` Max Mikhanosha
2011-09-18 19:22 ` Alan E. Davis
2011-09-18 2:40 ` David Rogers
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 \
* 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).