From: Bernt Hansen <bernt@norang.ca>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Organizing by time or by subject and an idea
Date: Mon, 30 Jan 2012 19:26:34 -0500 [thread overview]
Message-ID: <87r4yglnt1.fsf@norang.ca> (raw)
In-Reply-To: <CA+M2ft-GY_q4+1FMcUjnf1pNCtjjP1zM=-e_bDMK23knuZh_GA@mail.gmail.com> (John Hendy's message of "Mon, 30 Jan 2012 17:11:04 -0600")
John Hendy <jw.hendy@gmail.com> writes:
> On Mon, Jan 23, 2012 at 3:00 AM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>>
>> The key, as John has already stated, is to record everything! With
>> emacs, I can usually pull out what I want *if* the information was
>> recorded in the first place.
>>
>> Finally, tags can be very useful for quick searching as well.
>
> I still need to figure out a better tag system as well. Currently, I
> just have a project acronym under each main header:
>
> -----
> * Tracking
> Odds and ends tasks
>
> * Project 1 :proj1:
> Stuff for project 1
>
> * Project 2 :proj2:
> Stuff for project 2
>
> * References :ref:
> Misc things I need to refer back to now and then (project reporting IDs, etc.)
> -----
>
> That's quasi helpful, but not really... Do you tag by type of data
> stored? Project/task type/name?
Hi John,
I have lots of projects that have similar structure and headlines. I
use tags sparingly -- mainly for filtering in the agenda and for
information about tasks. I almost always work from the agenda to find
what to do next and having the tags indicating which project the task is
for is very convenient. Tags are inherited so I'll normally tag the top
level project with some unique name and a few file tags are added for
grouping tasks.
I keep multiple projects in a single file but they are all related to
some larger projects. I'll archive done state tasks away when they are
2 months old.
Something like this:
,----[ fileX.org ]
| #+FILETAGS: XX
|
| * Tasks
| ** TODO Do this
| * TODO SomeProject :someproject:
| ** TODO Create design document
| ** TODO Coding
| *** TODO FileA
| **** TODO FunctionQ
| *** TODO FileB
| * TODO OtherProject :otherproject:
| ** TODO Create design document
| ** TODO Coding
| *** TODO FileF
| **** TODO FunctionR
| *** TODO FileG
`----
,----[ fileY.org ]
| #+FILETAGS: YY
|
| * Tasks
| ** TODO Do this
| * TODO ProjA :proja:
| ** TODO Create design document
| ** TODO Coding
| *** TODO FileA
| **** TODO FunctionQ
| *** TODO FileB
| * TODO ProjB :projb:
| ** TODO Create design document
| ** TODO Coding
| *** TODO FileF
| **** TODO FunctionR
| *** TODO FileG
`----
When looking for tasks to work on in the agenda it's obvious what a task
belongs to. Each task has an XX or YY tag from the FILETAGS line and
all projB tasks have a :projb: tag. I use this a lot to quickly
distinguish tasks from each other in the global todo list.
My current global todo list has tasks with 1 - 5 tags. Only HOLD tasks
have 5 tags (where :HOLD: is automatically added when I change the task
state) All tasks have at least 1 tag (coming from the FILETAGS entry).
Filtering the agenda with tags is immensely useful. You can limit to a
specific tag, or exclude tasks with some tag, etc which helps me focus
on the thing I'm working on now.
I also limit my block agenda view to subtree and project using my fairly
recent changes on http://doc.norang.ca/org-mode.html.
HTH,
Bernt
next prev parent reply other threads:[~2012-01-31 0:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 18:04 Organizing by time or by subject and an idea John Hendy
2012-01-21 12:59 ` Max Mikhanosha
2012-01-21 13:09 ` Max Mikhanosha
2012-01-21 15:57 ` Max Mikhanosha
2012-01-23 9:00 ` Eric S Fraga
2012-01-30 23:11 ` John Hendy
2012-01-31 0:26 ` Bernt Hansen [this message]
2012-01-31 13:10 ` Eric S Fraga
2012-02-10 19:47 ` John Hendy
2012-02-11 2:03 ` Bernt Hansen
2012-02-11 2:07 ` John Hendy
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87r4yglnt1.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).