emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: egallego@babel.ls.fi.upm.es (Emilio Jesús Gallego Arias)
To: emacs-orgmode@gnu.org
Subject: Re: (org-entry-properties nil 'all) does not return inherited properties
Date: Mon, 22 Mar 2010 21:07:43 +0100	[thread overview]
Message-ID: <87vdcodss0.fsf@babel.ls.fi.upm.es> (raw)
In-Reply-To: 20100322180630.GB26505@homac

Holger Macht <holger@homac.de> writes:

> On Mo 22. Mär - 18:44:38, Emilio Jesús Gallego Arias wrote:
>> Holger Macht <holger@homac.de> writes:
>> 
>> > (org-entry-properties nil 'all) does not return inherited properties
>> > added with a file directive like that:
>> >
>> > #+PROPERTY: propkey propval
>> >
>> > Is this by intention? If so, is there a method to get all the properties
>> > of an item, also inherited ones?
>> >
>> > Currently I was just able to find (org-entry-get), but this only returns
>> > one specific property of which I need to know the name.
>> 
>> See:
>> 
>> ,----[ C-h v org-use-property-inheritance RET ]
>
> Have you tried? At least this doesn't have an effect on
> (org-entry-properties in current git head.

Sorry Holger I misunderstood your question. I guess you should modify
org-entry-properties in order to include global properties like is done
in the inheritance case.

It could be something like:

(when org-use-property-inheritance
      (setq props (append org-file-properties props)
	    props (append org-global-properties props)
            props (append org-global-properties-fixed props)))

I don't know what may this change break.

Regards,
Emilio

  reply	other threads:[~2010-03-22 20:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22 15:01 (org-entry-properties nil 'all) does not return inherited properties Holger Macht
2010-03-22 17:44 ` Emilio Jesús Gallego Arias
2010-03-22 18:06   ` Holger Macht
2010-03-22 20:07     ` Emilio Jesús Gallego Arias [this message]
2010-03-22 21:56       ` Holger Macht
2010-03-22 22:34         ` Emilio Jesús Gallego Arias
2010-03-24 12:37         ` Carsten Dominik

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=87vdcodss0.fsf@babel.ls.fi.upm.es \
    --to=egallego@babel.ls.fi.upm.es \
    --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).