From: Matthew Lundin <mdl@imapmail.org>
To: Ethan <ethan.glasser.camp@gmail.com>
Cc: Matt Lundin <mdl@imapmail.org>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Documentation wishlist items
Date: Wed, 16 Sep 2009 12:32:02 -0400 [thread overview]
Message-ID: <m24or24zr1.fsf@fastmail.fm> (raw)
In-Reply-To: <9cd2f5ff0909160833n32fb0323i444611365c4c3673@mail.gmail.com> (Ethan's message of "Wed, 16 Sep 2009 11:33:37 -0400")
Ethan <ethan.glasser.camp@gmail.com> writes:
> On Tue, Sep 15, 2009 at 11:34 PM, Matt Lundin <mdl@imapmail.org> wrote:
>
> 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.
>
> But this is like asking why someone puts their pots in the cupboard
> next
> to the oven rather than above the sink, or why someone uses legal
> pads
> rather than a spiral notebook.
>
> And if you were setting up a kitchen for the first time, wouldn't you
> ask that kind of question? :)
Agreed. What I meant by the analogy is that often these times decisions
come down to personal convention/habit. You just start doing things one
way and they stick.
The analogy was in part a reminder to myself to avoid worrying about the
"one right way." :)
As a point of comparison, I divide my files according to area of
responsibility (household.org, health.org, family.org, writing.org,
etc.) so that I can quickly review what I need to do in each area. When
I'm done with an item, I archive it and it is nicely deposited in the
appropriate archive file. If a project within one of these files becomes
quite big, I create a new file for it. I almost never set CATEGORY,
because all my appointments are already organized by category (i.e.,
file name).
>
> My recommendation: Just start creating trees, use only a few TODO
> states, and allow the organization to evolve in the way that feels
> the
> most comfortable to you.
>
> At the time of this writing, I've stumbled because I have had one file
> called TODO which is becoming too cluttered for me to process usefully.
> I used C-c C-v to show only TODO items, but some TODO items have
> ellipses indicating content while some have ellipses indicating DONE
> items afterwards, so I end up expanding a bunch of DONE items.
Is this necessarily a bad thing? If you expand a TODO item with a bunch
of DONE items, it might indicate that you should either 1) create a new
TODO item or 2) mark the parent item as DONE.
> I have a TODO state called BLOCKING which clutters the view too.
Perhaps you could make the BLOCKING state it an inactive todo state in
order to exclude it from the sparse tree view.
#+SEQ_TODO: TODO(t) | DONE(d) BLOCKING(b)
> I have a vague sense that learning how to use the agenda would help,
> but I haven't gotten to it yet, since I've been trying to put together
> a coherent org-mode setup by cargo-culting things from the advanced
> users' setups. This probably isn't the best way to go about it, of
> course..
The agenda is calling you! :)
I wouldn't worry about custom commands until you need them. Just type
type C-c a t or C-c a T "TODO" and you'll get a "clean" list of all your
todos.
Hope this helps.
Matt
next prev parent reply other threads:[~2009-09-16 16:32 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
2009-09-16 15:33 ` Ethan
2009-09-16 16:32 ` Matthew Lundin [this message]
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=m24or24zr1.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=emacs-orgmode@gnu.org \
--cc=ethan.glasser.camp@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).