emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Jones <mlists@pmade.com>
To: emacs-orgmode@gnu.org
Subject: More Flexibility for Stuck Projects?
Date: Wed, 18 Mar 2009 11:01:03 -0600	[thread overview]
Message-ID: <86ljr2ahps.fsf@pmade.com> (raw)

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.


Peter Jones, http://pmade.com
pmade inc.  Louisville, CO US

             reply	other threads:[~2009-03-18 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 17:01 Peter Jones [this message]
2009-03-19 16:40 ` More Flexibility for Stuck Projects? Carsten Dominik
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=86ljr2ahps.fsf@pmade.com \
    --to=mlists@pmade.com \
    --cc=emacs-orgmode@gnu.org \


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