From: Bernt Hansen <bernt@norang.ca>
To: Matt Lundin <mdl@imapmail.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Documentation wishlist items
Date: Wed, 16 Sep 2009 07:37:48 -0400 [thread overview]
Message-ID: <87y6ofjf1v.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <87pr9r36mt.fsf@fastmail.fm> (Matt Lundin's message of "Tue\, 15 Sep 2009 23\:34\:02 -0400")
Matt Lundin <mdl@imapmail.org> writes:
> Ethan <ethan.glasser.camp@gmail.com> writes:
>
>> Reading HOWTO's like Bernt Hansen's and Charles Cave's are really
>> interesting to see how people work, but even documents like these don't
>> explain *why* they set things up in this way. For example, Bernt
>> Hansen's document explains that his toplevel headings are "main
>> categories", and shows that they each have a CATEGORY property, but
>> doesn't explain what that buys him, or what problem that solves.
>
> My guess is that this allows him to see what group an item belongs to in
> the agenda view, since categories are listed in the left column.
That's correct. The category only shows up in my agenda in the left
column and gives me instant access to what this task is related to. I
usually specify a shorter category name than the filename just to keep
the agenda compact. My todo.org file has multiple categories since it's
a mishmash of personal stuff.
I use filtering to limit the displayed tasks but the category is a
useful piece of information on the agenda. I don't use category for
anything else.
I guess the problem it solves is if I have two identical tasks in
separate categories that both show up in the agenda then I can tell
which is which -- but that doesn't happen often. I clock in tasks from
the agenda so knowing which is which is important. "Invoicing and
Archive Tasks" is one example since I carry one of those for every
client (which are in separate files and separate categories).
-Bernt
next prev parent reply other threads:[~2009-09-16 11:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 21:21 Documentation wishlist items Ethan
2009-09-15 23:56 ` Sean Sieger
2009-09-16 3:20 ` Sebastian Rose
2009-09-16 9:46 ` Bastien
2009-09-16 9:54 ` Greg Newman
2009-09-16 10:04 ` timetrap
2009-09-16 12:17 ` Jean-Marie Gaillourdet
2009-09-16 12:56 ` Peter Frings
2009-09-16 9:49 ` Bastien
2009-09-16 14:10 ` Sebastian Rose
2009-09-16 16:03 ` Matt Lundin
2009-09-16 12:46 ` Matt Lundin
2009-09-16 3:34 ` Matt Lundin
2009-09-16 11:37 ` Bernt Hansen [this message]
2009-09-16 15:33 ` Ethan
2009-09-16 16:32 ` Matthew Lundin
2009-09-16 18:42 ` tycho garen
2009-09-18 15:02 ` org-invoice question Dave Täht
2009-09-21 17:15 ` Peter Jones
2009-09-21 17:30 ` Dave Täht
2009-09-18 15:19 ` org-examples.git? Dave Täht
2009-09-18 17:00 ` org-examples.git? Matt Lundin
2009-09-16 9:42 ` Documentation wishlist items Bastien
2009-09-17 3:46 ` Matt Lundin
2009-09-17 17:34 ` Ethan
2009-09-17 19:30 ` Matthew Lundin
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=87y6ofjf1v.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.org \
/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).