emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matthew Lundin <mdl@imapmail.org>
To: Saurabh Agrawal <mailsaurabh@gmail.com>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Novice here: agenda related questions
Date: Fri, 23 Jan 2009 10:33:34 -0600	[thread overview]
Message-ID: <m2ljt2nfs1.fsf@fastmail.fm> (raw)
In-Reply-To: <4c4575360901230809m26544b85mdb6ca008da5d174a@mail.gmail.com> (Saurabh Agrawal's message of "Fri\, 23 Jan 2009 21\:39\:45 +0530")


Hi Saurabh,

Saurabh Agrawal <mailsaurabh@gmail.com> writes:

> Hi Matt
>
> 1. Your first suggestion is spot on. Thanks.
>
>>> 2. Since I have a number of TODO action items in several projects, I
>>> would like to display only top two of them for each project at a
>>> time in an agenda. Is it somehow possible using some particular
>>> custom agenda view?
>>>
>
> In my second question, what I wanted to ask was is there some setting,
> where I can set number of TODOs to display for a particular CATEGORY?
> or something like that?

Sorry, I missed your second question when I replied to the email. I
handle this scenario by hand -- i.e., I only mark one or two next
actions as active TODOS per project and then switch the following
actions to TODO by hand once the first next actions are completed. (But
you could also mark the first one or two TODOs of a project with the tag
:NEXT: and then use a secondary query to limit your agenda only to items
tagged :NEXT:)

org-stuck-projects really helps here to determine which projects don't
have a next action.

If you want to automate cascading next actions, there is org-depend.el
in the contrib directory of the org distribution that can do what you're
looking for -- i.e., change the state of the next item in a subtree once
the previous item is marked done. Here's a quote from the file:

,----
| ;;
| ;; Triggering
| ;; ----------
| ;;
| ;; 1) If an entry contains a TRIGGER property that contains the string
| ;;    "chain-siblings(KEYWORD)", then switching that entry to DONE does
| ;;    do the following:
| ;;    - The sibling following this entry switched to todo-state KEYWORD.
| ;;    - The sibling also gets a TRIGGER property "chain-sibling(KEYWORD)",
| ;;      property, to make sure that, when *it* is DONE, the chain will
| ;;      continue.
| ;;
| ;; 2) If the TRIGGER property contains any other words like
| ;;    XYZ(KEYWORD), these are treated as entry id's with keywords.  That
| ;;    means, Org-mode will search for an entry with the ID property XYZ
| ;;    and switch that entry to KEYWORD as well.
`----

There are also several discussions of org-depend on the mailing list.

Best,
Matt

  reply	other threads:[~2009-01-23 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23 12:07 Saurabh Agrawal
2009-01-23 13:22 ` Matthew Lundin
2009-01-23 16:09   ` Saurabh Agrawal
2009-01-23 16:33     ` Matthew Lundin [this message]
2009-01-23 16:53       ` Saurabh Agrawal

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=m2ljt2nfs1.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mailsaurabh@gmail.com \
    --subject='Re: Novice here: agenda related questions' \
    /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 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).