emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Matt Lundin <mdl@imapmail.org>
To: Marcelo de Moraes Serpa <celoserpa@gmail.com>
Cc: Bernt Hansen <bernt@norang.ca>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [off-topic/GTD]Only Next Actions list to rule them all ?
Date: Wed, 21 Oct 2009 15:05:43 -0400	[thread overview]
Message-ID: <m263a8bm9k.fsf@fastmail.fm> (raw)
In-Reply-To: <1e5bcefd0910211130h63a3914u1e29b2c087486ed1@mail.gmail.com> (Marcelo de Moraes Serpa's message of "Wed, 21 Oct 2009 13:30:41 -0500")

Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:

> On the other hand, most of this could be achieved by using the agenda
> view and other org filtering features, and still keep a list of
> projects, sub-projects and next-actions, all in one, like:
>
> (Always ordered by priority)
>
> * Projects and Next Actions
> ** A project/outcome :PROJECT:
> *** TODO Do something :HOME:
> *** A subproject :PROJECT:
> **** TODO Do something! :HOME:
> *** TODO Do something else :OFFICE:
>
> Then, in the agenda, I can filter by HOME / OFFICE or TODO and would
> have a flat list of actions too.
>
> More configuration, but more you get, when you view the Projects and
> Next Actions list, the information of to which project this next action
> belongs, which might not be that important, as I'm interested on doing,
> not reviewing the landscape all the time, but could be useful sometimes
> (when the action is not specific enough you can't tell the related
> outcome).
>
> What do you guys think?

Are you looking for us to convince you to organize your files by
project? :)

IMO, how the user chooses to organize his/her files is a moot point,
since the magic of org-mode lies in the agenda. My agenda files consist
of several thematic files (currently 21), each containing a variety of
notes, projects, todos, etc. In the end, the organization of these files
doesn't matter, since org-mode's agenda commands do a fantastic job of
presenting me with clean lists of all my todos, while org-refile allows
me easily to move items to different files and or subheadings.

I prefer this method because it allows me to jump to rich contextual
information from the agenda. For me, keeping next actions and projects
separate within the org files would eliminate a major strength of
org-mode and reduplicate what the agenda already does. But to each
his/her own! :)

- Matt

next prev parent reply	other threads:[~2009-10-21 19:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21  5:15 [off-topic/GTD]Only Next Actions list to rule them all ? Marcelo de Moraes Serpa
2009-10-21  5:51 ` Manish
2009-10-21 12:13   ` Desmond Rivet
2009-10-21 12:22   ` Bernt Hansen
2009-10-21 18:06     ` Marcelo de Moraes Serpa
2009-10-21 18:30       ` Marcelo de Moraes Serpa
2009-10-21 19:05         ` Matt Lundin [this message]
2009-10-21 19:15           ` Bernt Hansen
2009-10-21 22:15             ` Marcelo de Moraes Serpa
2009-10-22  1:48               ` Bernt Hansen

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=m263a8bm9k.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=bernt@norang.ca \
    --cc=celoserpa@gmail.com \
    --cc=emacs-orgmode@gnu.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

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).