emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Peter Jones <mlists@pmade.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: More Flexibility for Stuck Projects?
Date: Thu, 19 Mar 2009 17:40:34 +0100	[thread overview]
Message-ID: <68B2EECE-D9F1-4C8E-B64F-F724217B58E3@uva.nl> (raw)
In-Reply-To: <86ljr2ahps.fsf@pmade.com>

[-- Attachment #1.1: Type: text/plain, Size: 3385 bytes --]

Hi Peter,

I guess you might want to use

(setq org-tags-exclude-from-inheritance '("project" "subproject"))

Then you can select projects for the stuck-project listing with


If you have a reason to actually want the inheritance of these tags
in other circumstances, you could implement this setting
as an option to an agenda custom command that does look for stuck

(("#" "Stuck" stuck ""
     '("project" "subproject"))))

To answer to your original question:

On Mar 18, 2009, at 6:01 PM, Peter Jones wrote:

> I really love the idea of stuck projects, it helps me every day.   
> Right
> now, I consider projects to be level two headings with the :project:
> tag.  90% of my projects follow this convention.
> However, I sometimes find myself needing sub-projects, where level two
> is a project, level three is a sub-project, and level four are tasks:
> * Projects                :project:
> ** Some Complex Project
> *** Sub-Project 1         :subproject:
> **** NEXT Do something
> **** Do something else
> *** Sub-Project 2         :subproject:
> **** Do something again
> With the above headings, and my current configuration for stuck
> projects, Sub-Project 2 won't show up in the stuck projects list
> (because technically it's not a stuck project).
> Does anyone have a setting for org-stuck-projects that would allow  
> me to
> define a project as either:
> 1. A level 2 heading tagged :project:
> 2. A level 3 heading tagged :subproject:


> Or a better way to do what I'm doing.

I am using TODO keywords


to make projects, because they do not involve inheritance, and a project
is never a TODO item itself, only the subtasks are....

Now, maybe the real problem you are having is this:

When the stuck project search goes through your tree, it first finds a  
project tree and checks if it is stuck.  If not, the entire tree is  
skipped, including the subprojects.  This is not what you want.

The best solution probably is to say that a project that has sub  
projects is never stuck, by adding the subproject tag to the unstuck  

Hmm, I see now that part of this problem stems from the fact that
the skipper skips the entire subtree and never looks at subitems.
Maybe this is a mistake...  I actually think it is.  I am changing  
this... done.

With this change, I guess you can switch to

- use :project: to define both projects and subprojects
- exclude :project: from inheritance
- define your stuck project search "+project" to identify a project.


- use a TODO keyword PROJ
- define the search as "TODO=\"PROJ\""


- Carsten

> The biggest challenge to getting this working is that I use tag
> inheritance with the :project: tag.  In some files I have level 1
> headings tagged :project:, and in others, I use file level tags with
> :project:.  That means that all headings are basically tagged as
> :project:, so I need to specify a heading level for stuck projects.
> TIA.
> -- 
> Peter Jones, http://pmade.com
> pmade inc.  Louisville, CO US
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[-- Attachment #1.2: Type: text/html, Size: 4741 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

  reply	other threads:[~2009-03-19 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 17:01 More Flexibility for Stuck Projects? Peter Jones
2009-03-19 16:40 ` Carsten Dominik [this message]
2009-03-19 18:00   ` Peter Jones

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:

  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=68B2EECE-D9F1-4C8E-B64F-F724217B58E3@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=mlists@pmade.com \


* 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


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