From mboxrd@z Thu Jan  1 00:00:00 1970
From: Samuel Wales <samologist@gmail.com>
Subject: Re: Projects with priority items
Date: Mon, 14 Feb 2011 14:14:32 -0700
Message-ID: <AANLkTi=u2_H8fpNW5kzim-j0YHoM7KHJ5=kijPJAXqwB@mail.gmail.com>
References: <AANLkTi=Korv-ZF84ZkqS_6wtLR6jP7N0VVZ-xMPHm8R=@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from [140.186.70.92] (port=57105 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Pp5kg-0006pm-I2
	for emacs-orgmode@gnu.org; Mon, 14 Feb 2011 16:14:35 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <samologist@gmail.com>) id 1Pp5kf-00043t-8S
	for emacs-orgmode@gnu.org; Mon, 14 Feb 2011 16:14:34 -0500
Received: from mail-yx0-f169.google.com ([209.85.213.169]:57663)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <samologist@gmail.com>) id 1Pp5kf-00043i-1e
	for emacs-orgmode@gnu.org; Mon, 14 Feb 2011 16:14:33 -0500
Received: by yxl31 with SMTP id 31so2540946yxl.0
	for <emacs-orgmode@gnu.org>; Mon, 14 Feb 2011 13:14:32 -0800 (PST)
In-Reply-To: <AANLkTi=Korv-ZF84ZkqS_6wtLR6jP7N0VVZ-xMPHm8R=@mail.gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Nathan Neff <nathan.neff@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>

Excellent question.  Do you mean all ancestors?

===

More options you might consider (don't want to hijack thread):

Other options include dimming tasks that have at least one descendent
in the same agenda view.

Motivation is that sometimes I mark a task as important (or any other
tag), and mark its child as important.  When I look at the agenda view
for important items without inheritance, I am less interested in the
parent.  But when B is done, I am interested in A again.  I don't want
to manipulate tags.  I just want to have both there all the time in the
agenda, but one dimmed.

  * deal with company A :important:
    * call B at company A :important:
    * call C

However, this is also not implemented.

Samuel