From: Manish <mailtomanish.sharma@gmail.com>
To: Adam Spiers <orgmode@adamspiers.org>, emacs-orgmode@gnu.org
Subject: Re: SOMEDAY/MAYBE vs. low priorities
Date: Mon, 31 Dec 2007 22:55:30 +0530 [thread overview]
Message-ID: <e7cdbe30712310925l42d5450ap85896cb2016c304e@mail.gmail.com> (raw)
In-Reply-To: <20071231171524.GQ20947@atlantic.linksys.moosehall>
On Dec 31, 2007 10:45 PM, Adam Spiers <orgmode@adamspiers.org> wrote:
> Adam Spiers (orgmode@adamspiers.org) wrote:
> > OK. My setup is similar except that I allow for sub-projects -
> > projects within projects. As a result, projects are not uniquely
> > identified by their star level, so I explicitly mark them with PROJECT
> > which means I retain the ability to do keyword searches on them. This
> > also has the advantage that I can include items for reference within
> > the project as sub-headings, and they won't have a keyword so they
> > won't show up in searches.
>
> OK, last one of the year honest! `org-stuck-projects' appears to get
> confused by sub-projects. If I set it to
>
> ("/PROJECT" ("TODO" "NEXT" "NEXTACTION" "STARTED") nil "")
>
> then in the following, it considers both the main and sub- projects as
> unstuck, when in fact only the sub-project is:
>
> * PROJECT main project
> ** NEXT main project is not stuck
> ** PROJECT sub-project
> *** sub-project is stuck
>
I am a very new org user so it may not make much sense but I suspect
tags could be used to mark some projects/tasks as SOMEDAY and then
stuck projects configured to ignore those?
Happy New Year!
--
Manish
next prev parent reply other threads:[~2007-12-31 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 18:11 SOMEDAY/MAYBE vs. low priorities Adam Spiers
2007-12-30 21:10 ` Eddward DeVilla
2007-12-30 22:44 ` Pete Phillips
2007-12-31 14:44 ` Adam Spiers
2007-12-31 17:09 ` Adam Spiers
2007-12-31 17:15 ` Adam Spiers
2007-12-31 17:25 ` Manish [this message]
2007-12-31 19:01 ` Pete Phillips
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=e7cdbe30712310925l42d5450ap85896cb2016c304e@mail.gmail.com \
--to=mailtomanish.sharma@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@adamspiers.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.