From: Erik Iverson <eriki@ccbr.umn.edu>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Basic organization question
Date: Fri, 14 Jan 2011 22:50:16 -0600 [thread overview]
Message-ID: <4D312788.1090801@ccbr.umn.edu> (raw)
In-Reply-To: <m2zkr2u9df.fsf@verilab.com>
On 01/14/2011 09:35 PM, Tommy Kelly wrote:
> I can see that TODOs can be organized using tags, or categories, or
> files, or simply subtrees (or several of those). Is there an obvious
> choice?
My vote is "NO", org is really about finding what works best for you,
and the plethora of choices reflects that different people work in
different ways! Try out a few until something feels natural.
>
> All I'm really looking for is a basic organization, to let me "group"
> tasks of different broad functional areas -- accounting, recruitment,
> IT, and so on.
>
> And I like the idea discussed in http://orgmode.org/org.html, where
> tasks get captured into a single refile.org file and then later moved
> about into their classification homes.
>
> But of those various ways of classifying, is there one to be preferred?
>
> thanks,
> Tommy
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2011-01-15 4:41 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 [this message]
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
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=4D312788.1090801@ccbr.umn.edu \
--to=eriki@ccbr.umn.edu \
--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).