From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Jolitz Subject: Re: accessing properties in org-element-parse-buffer tree Date: Sun, 31 Aug 2014 00:10:16 +0200 Message-ID: <871trx7ho7.fsf@gmail.com> References: <87ppfhzweg.fsf@ithaka.home> <87bnr17oks.fsf@gmail.com> <87k35pzp2x.fsf@ithaka.home> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60099) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XNqqy-00047u-I5 for emacs-orgmode@gnu.org; Sat, 30 Aug 2014 18:10:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XNqqs-0006Ap-5V for emacs-orgmode@gnu.org; Sat, 30 Aug 2014 18:10:36 -0400 Received: from plane.gmane.org ([80.91.229.3]:47515) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XNqqr-0006Ah-T5 for emacs-orgmode@gnu.org; Sat, 30 Aug 2014 18:10:30 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XNqqq-0004P6-Mb for emacs-orgmode@gnu.org; Sun, 31 Aug 2014 00:10:28 +0200 Received: from e178062046.adsl.alicedsl.de ([85.178.62.46]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 31 Aug 2014 00:10:28 +0200 Received: from tjolitz by e178062046.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 31 Aug 2014 00:10:28 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: emacs-orgmode@gnu.org Eike writes: > Thanks a lot for the examples, they are very helpful! I first thought to > parse the org buffer and then work with the resulting tree. Thats the obvious thing to do in this case, and you can do everything you want this way, but there are some alternatives too. > But your examples now makes me think to work directly on the > buffer. Well, I will play with a few different ways now… I wrote 'org-dp-filter-node-props' based on 'org-dp-contents', so only the property-drawer of the current entry is parsed and its content (the node-properties) filtered. This is meant mostly for local usage (in contrast to the global parse-tree), but can be used as function argument for org-map-entries too. The big advantage is that it becomes really easy to filter out all the system properties, or all properties that do not belong to a specific application. I use it quite often now because I like the database functionality of Org properties. -- cheers, Thorsten