From: Tim <wiskey5alpha@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org, Tim <wiskey5alpha@gmail.com>
Subject: Re: Showing only subprojects in the agenda
Date: Wed, 27 Feb 2013 22:41:20 -0500 [thread overview]
Message-ID: <87mwup14wv.wl%wiskey5alpha@gmail.com> (raw)
In-Reply-To: <87ehgbciar.fsf@norang.ca>
At Wed, 20 Feb 2013 06:54:04 -0500,
Bernt Hansen wrote:
>
> If all of your projects are normally at level 2 will this work?
>
> C-c a m LEVEL=2/!TODO RET
>
Bernt,
I really appreciate your time. Unfortunately, this doesnt quite get me
what I am looking for. My current method of defining projects and actions
is :
- any thing that needs to be accomplished is a TODO
- a TODO can have TODOs as children, for as many levels as it takes to
organize the project and subprojects
- Next actions are defined with a NEXT key word and are tagged with the
appropriate context to have them show on my next actions list (i.e. errand,
office, home)
I would like to have 2 views of the projects :
The first is a hierarchial view of all TODOs , which i do using the indented
agenda list of TODOs.
The second is now using what you have published on your website using the skip
functions. Since I want to see all TODOs that have NEXT items as children, or,
said another way
A project is any TODO that has NEXT as children
I modified your =bh/is-project-p= to look for NEXT like so
#+BEGIN_SRC elisp
(while (and (not has-subtask)
(< (point) subtree-end)
- (re-search-forward "^\*+ TODO" subtree-end t))
+ (re-search-forward "^\*+ NEXT" subtree-end t))
(when (member (org-get-todo-state) org-todo-keywords-1)
#+END_SRC
Again, thank you for your help, and for putting your setup out on
the web for all of us to benefit from.
-Tim
prev parent reply other threads:[~2013-02-28 3:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 3:45 Showing only subprojects in the agenda Wiskey 5 Alpha
2013-02-19 23:56 ` Bernt Hansen
2013-02-20 4:06 ` Tim
2013-02-20 11:54 ` Bernt Hansen
2013-02-28 3:41 ` Tim [this message]
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=87mwup14wv.wl%wiskey5alpha@gmail.com \
--to=wiskey5alpha@gmail.com \
--cc=bernt@norang.ca \
--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 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).