From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: More Flexibility for Stuck Projects? Date: Thu, 19 Mar 2009 17:40:34 +0100 Message-ID: <68B2EECE-D9F1-4C8E-B64F-F724217B58E3@uva.nl> References: <86ljr2ahps.fsf@pmade.com> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: multipart/mixed; boundary="===============1280962171==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LkLIm-0002B8-Vp for emacs-orgmode@gnu.org; Thu, 19 Mar 2009 12:41:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LkLIi-00028y-3c for emacs-orgmode@gnu.org; Thu, 19 Mar 2009 12:41:04 -0400 Received: from [199.232.76.173] (port=59478 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LkLIh-00028s-UJ for emacs-orgmode@gnu.org; Thu, 19 Mar 2009 12:40:59 -0400 Received: from fk-out-0910.google.com ([209.85.128.191]:41128) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LkLIg-0003mU-J2 for emacs-orgmode@gnu.org; Thu, 19 Mar 2009 12:40:59 -0400 Received: by fk-out-0910.google.com with SMTP id z23so240666fkz.10 for ; Thu, 19 Mar 2009 09:40:56 -0700 (PDT) In-Reply-To: <86ljr2ahps.fsf@pmade.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Peter Jones Cc: emacs-orgmode@gnu.org --===============1280962171== Content-Type: multipart/alternative; boundary=Apple-Mail-5--671886673 --Apple-Mail-5--671886673 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit 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 "project|subproject" 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 projects: (("#" "Stuck" stuck "" ((org-tags-exclude-from-inheritance '("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: "+project+LEVEL=2|+subproject+LEVEL=3" > > Or a better way to do what I'm doing. I am using TODO keywords #+TODO: PROJ | PRDONE PRCANCELLED 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 conditions. 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. or - use a TODO keyword PROJ - define the search as "TODO=\"PROJ\"" HTH - 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 --Apple-Mail-5--671886673 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable 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

"project|subproject"

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
projects:

(("#" = "Stuck" stuck = ""
  ((org-tags-exclude-from-inheritance
&nb= sp;   '("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 =             &n= bsp;  :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:

"+project+LEVEL=3D2= |+subproject+LEVEL=3D3"



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

I am using TODO = keywords

#+TODO: PROJ | PRDONE = PRCANCELLED 

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

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.

or

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


HTH
- 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
<= br>
= --Apple-Mail-5--671886673-- --===============1280962171== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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 --===============1280962171==--