From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matt Lundin <mdl@imapmail.org>
Subject: Re: Inheriting Properties
Date: Fri, 22 Apr 2011 08:14:45 -0400
Message-ID: <87k4emjxe2.fsf@fastmail.fm>
References: <BANLkTi=kovSgxLU7RyaGTBW108NEB6xVzg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:35929)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lundin@fastmail.fm>) id 1QDFG6-00012Y-4t
	for emacs-orgmode@gnu.org; Fri, 22 Apr 2011 08:14:50 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lundin@fastmail.fm>) id 1QDFG5-0001r1-4W
	for emacs-orgmode@gnu.org; Fri, 22 Apr 2011 08:14:50 -0400
Received: from out4.smtp.messagingengine.com ([66.111.4.28]:60362)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lundin@fastmail.fm>) id 1QDFG4-0001qu-V4
	for emacs-orgmode@gnu.org; Fri, 22 Apr 2011 08:14:49 -0400
In-Reply-To: <BANLkTi=kovSgxLU7RyaGTBW108NEB6xVzg@mail.gmail.com> (Dustin
	Lacewell's message of "Thu, 21 Apr 2011 15:43:28 -0500")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: </archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Dustin Lacewell <dlacewell@gmail.com>
Cc: emacs-orgmode@gnu.org

Dustin Lacewell <dlacewell@gmail.com> writes:

> Hi, I'm a new org-mode user and I'm just starting to use it in a real
> way. One feature that seems to be missing is the ability to specify
> properties on a parent-node that are inherited by the children, but is
> not applied to the parent itself. An example of where you might need
> this is:
>
> * Servers
>    :PROPERTIES:
>    :COLUMNS: %25ITEM %ip
>    :END
> ** foo.example.com
>    :PROPERTIES:
>    :ip:x.x.x.x
>    :END
> ** bar.example.com
>    :PROPERTIES:
>    :ip:x.x.x.x
>    :END
>
> If there was a way to apply the root properties to the children but
> not the parent itself, then column mode would work as expected but
> would not apply the columns specification to the "Servers" node where
> it is not relevant. As it is now, each child-entry needs it's own
> column specification.

Is there a practical reason you do not want the Servers heading included
in the columns view? One advantage of including the heading is that, as
your data grows, you can use that line to summarize the data in the
subheadings:

(info "(org) Column attributes")

Best,
Matt