emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* Inheriting Properties
@ 2011-04-21 20:43 Dustin Lacewell
  2011-04-22 12:14 ` Matt Lundin
  0 siblings, 1 reply; 2+ messages in thread
From: Dustin Lacewell @ 2011-04-21 20:43 UTC (permalink / raw)
  To: emacs-orgmode

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Inheriting Properties
  2011-04-21 20:43 Inheriting Properties Dustin Lacewell
@ 2011-04-22 12:14 ` Matt Lundin
  0 siblings, 0 replies; 2+ messages in thread
From: Matt Lundin @ 2011-04-22 12:14 UTC (permalink / raw)
  To: Dustin Lacewell; +Cc: emacs-orgmode

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-04-22 12:14 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-04-21 20:43 Inheriting Properties Dustin Lacewell
2011-04-22 12:14 ` Matt Lundin

Code repositories for project(s) associated with this 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).