From: Matt Lundin <mdl@imapmail.org>
To: Marcelo de Moraes Serpa <celoserpa@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Projects+Next Actions view
Date: Thu, 30 Sep 2010 19:56:24 -0400 [thread overview]
Message-ID: <87eicaokev.fsf@fastmail.fm> (raw)
In-Reply-To: <AANLkTikrpp4TV-h0q1tYxR+CW07n+aADmYamPqtCPq0h@mail.gmail.com> (Marcelo de Moraes Serpa's message of "Thu, 30 Sep 2010 13:03:03 -0500")
Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
> Another thing that I like about Things
> (http://culturedcode.com/things/) is the "Next Actions" view. It
> basically lists all projects plus the very first next action for each
> of them. When you need some perspective, having quick access to a view
> like this is very useful. It also shows any "orphan" tasks (tasks that
> don't belong to a project), so you have a nice overview of what you
> can do based on your own input.
>
> With org, I have created a Projects view, a tags agenda filter
> filtering for non-todo items. I could use follow mode, which is quite
> useful, but doesn't give the same uncluttered view Things does with
> its next actions view. I was wondering if it would be possible, even
> if more elisp would be needed, to create a view like this?
>
> E.x:
>
> * Keep the cat alive :PROJECT:HOME:
> ** TODO Feed the cat
> ...
>
> * Feature 2 :PROJECT:FEATURE:
> ** TODO Run the script
> ...
>
You could use a sparse tree view:
(add-to-list 'org-agenda-custom-commands
'("x" "PROJECT+N/A" tags-tree "PROJECT|TODO=\"TODO\""
((org-show-siblings nil)
(org-show-entry-below nil))))
Best,
Matt
next prev parent reply other threads:[~2010-09-30 23:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 18:03 Projects+Next Actions view Marcelo de Moraes Serpa
2010-09-30 23:56 ` Matt Lundin [this message]
2010-10-01 5:58 ` Marcelo de Moraes Serpa
2010-10-01 10:15 ` Łukasz Stelmach
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eicaokev.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--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
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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.