From: Bernt Hansen <bernt@norang.ca>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Basic organization question
Date: Wed, 19 Jan 2011 13:40:24 -0500 [thread overview]
Message-ID: <87aaiwag9z.fsf@norang.ca> (raw)
In-Reply-To: <m2zkqw4w5i.fsf@verilab.com> (Tommy Kelly's message of "Wed, 19 Jan 2011 11:54:01 -0600")
Hi Tommy,
Comments are inline below.
Tommy Kelly <tommy.kelly@verilab.com> writes:
> Bernt,
>
> Still digging into this. You said:
>
>> TAGS are much more flexible for controlling what you see on
>> the agenda and I use tags for filtering what is displayed on the agenda.
>
> Am I right though that from the point of view of clocking tasks, you
> rely not on TAGS but on having each task live inside the appropriate
> file/heading/sub-heading/sub-sub-heading and so on?
Yes each task lives in the appropriate file and subtree. It is only
possible to clock tasks. I clock in tasks both from the agenda and
directly from inside org files. Finding the thing to clock in is what I
use the agenda for -- I find a task with an agenda view (limited by
tags) and clock in the task directly with I in the agenda view.
> Or do you have some jiggery pokery to let clocking and clock tables be
> sensitive to TAGs?
I mostly use R and C-u R in the agenda for clock reports. The C-u R
version limits the displayed clock report based on your current agenda
tags filter.
Dynamic clock reports can also be limited by tags but I am not currently
using this feature.
I use persistent tags filters so when I set a tag filter to HOME it
stays that way until I change it. This lets me look at the agenda for
this week limited to HOME tasks, and also TODO and NEXT tasks for only
tasks with the HOME tag.
> Overall it looks like you use file-and-level-of-subheading to categorize things
> according to general area (clientX, clientY, or accounting, research,
> and so on), and then you use TAGs in addition to orthogonally categorize
> things according to some aspect of your workflow (it's a phone call, it
> has GTD context @wibble, it needs refiled, and so on). Is that remotely
> accurate?
Yes pretty much. I tend to group project related things into a file and
give it a #+FILETAGS: entry so everything in that file gets some tag.
Then I can limit my agenda view to just include or just exclude those
things depending on my current work context.
Inside a file I'll also have tagged entries for PHONE, NOTE, CANCELLED,
FLAGGED, @somewhere, etc so I can further refine the displayed tasks in
my agenda view.
Regards,
Bernt
next prev parent reply other threads:[~2011-01-19 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 3:35 Basic organization question Tommy Kelly
2011-01-15 4:50 ` Erik Iverson
2011-01-15 5:11 ` Thomas S. Dye
2011-01-15 12:07 ` Tommy Kelly
2011-01-17 2:58 ` Bernt Hansen
2011-01-19 17:54 ` Tommy Kelly
2011-01-19 18:40 ` Bernt Hansen [this message]
2011-01-15 5:53 ` Jambunathan K
-- strict thread matches above, loose matches on Subject: below --
2011-01-19 17:57 Tommy Kelly
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=87aaiwag9z.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=tommy.kelly@verilab.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).