From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Jolitz Subject: Re: [Exporter] How to save 'info' plist for later use? Date: Wed, 10 Jul 2013 14:30:43 +0200 Message-ID: <87wqoyppfw.fsf@gmail.com> References: <87a9lur8d0.fsf@gmail.com> <8761wir623.fsf@gmail.com> <87vc4i1uf4.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50725) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwtXw-0006e1-RT for emacs-orgmode@gnu.org; Wed, 10 Jul 2013 08:31:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UwtXs-000334-1S for emacs-orgmode@gnu.org; Wed, 10 Jul 2013 08:31:00 -0400 Received: from plane.gmane.org ([80.91.229.3]:42003) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwtXr-00032X-Lq for emacs-orgmode@gnu.org; Wed, 10 Jul 2013 08:30:55 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UwtXp-0002G9-Rr for emacs-orgmode@gnu.org; Wed, 10 Jul 2013 14:30:53 +0200 Received: from g231110193.adsl.alicedsl.de ([92.231.110.193]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Jul 2013 14:30:53 +0200 Received: from tjolitz by g231110193.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Jul 2013 14:30:53 +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 Nick Dokos writes: > Thorsten Jolitz writes: > >> Thorsten Jolitz writes: >> >> PS >> >>> How could I get my hands on the 'info' plist during the buffer parsing >>> and save it for later use in calls like >> >> As far as I understand it, the 'info' plist is actually dynamically >> created and modified in various stages of the export process. >> >> So what I really mean is probably: >> >> How could I get my hands on an 'info-like' plist that contains all the >> tree and options information available at the moment a buffer is parsed >> with `org-element-parse-buffer' - and save it for later use? > > edebug-defun org-element-parse-buffer, do whatever is necessary for it >to get called, and when it stops, evaluate it with ``e'' or switch to >*scratch* and save it in your own variable: > > (setq thorsten-info info) Thats a nice trick, but I'm afraid that the 'info' plist is not created during the parsing but rather during the export. When I want something similar after just parsing, I might have to create it myself. PS and how would you use this trick in a program? -- cheers, Thorsten