From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Jones Subject: More Flexibility for Stuck Projects? Date: Wed, 18 Mar 2009 11:01:03 -0600 Message-ID: <86ljr2ahps.fsf@pmade.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ljz94-0008At-Fs for emacs-orgmode@gnu.org; Wed, 18 Mar 2009 13:01:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ljz8z-000890-UC for emacs-orgmode@gnu.org; Wed, 18 Mar 2009 13:01:34 -0400 Received: from [199.232.76.173] (port=39453 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ljz8z-00088v-Kr for emacs-orgmode@gnu.org; Wed, 18 Mar 2009 13:01:29 -0400 Received: from main.gmane.org ([80.91.229.2]:39729 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ljz8y-0006Uj-Uw for emacs-orgmode@gnu.org; Wed, 18 Mar 2009 13:01:29 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ljz8v-00065U-ET for emacs-orgmode@gnu.org; Wed, 18 Mar 2009 17:01:25 +0000 Received: from 75-166-97-107.hlrn.qwest.net ([75.166.97.107]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 18 Mar 2009 17:01:25 +0000 Received: from mlists by 75-166-97-107.hlrn.qwest.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 18 Mar 2009 17:01:25 +0000 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: emacs-orgmode@gnu.org 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. 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