emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Dustin Lacewell <dlacewell@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Inheriting Properties
Date: Fri, 22 Apr 2011 08:14:45 -0400	[thread overview]
Message-ID: <87k4emjxe2.fsf@fastmail.fm> (raw)
In-Reply-To: <BANLkTi=kovSgxLU7RyaGTBW108NEB6xVzg@mail.gmail.com> (Dustin Lacewell's message of "Thu, 21 Apr 2011 15:43:28 -0500")

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

      reply	other threads:[~2011-04-22 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 20:43 Inheriting Properties Dustin Lacewell
2011-04-22 12:14 ` Matt Lundin [this message]

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=87k4emjxe2.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=dlacewell@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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