From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Jolitz Subject: [Exporter] How to save 'info' plist for later use? Date: Wed, 10 Jul 2013 12:56:43 +0200 Message-ID: <87a9lur8d0.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50504) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uws4u-0006qC-Ti for emacs-orgmode@gnu.org; Wed, 10 Jul 2013 06:56:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uws4t-0004Gz-SU for emacs-orgmode@gnu.org; Wed, 10 Jul 2013 06:56:56 -0400 Received: from plane.gmane.org ([80.91.229.3]:56567) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uws4t-0004Gd-Lw for emacs-orgmode@gnu.org; Wed, 10 Jul 2013 06:56:55 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Uws4r-0006IV-6T for emacs-orgmode@gnu.org; Wed, 10 Jul 2013 12:56: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 12:56: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 12:56: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 Hi List, how do I get my hands on the 'info' plist (i.e. the communication-channel) when I try to export data that is (only an isolated) part of a parse-tree? Say that originally a whole buffer was parsed, thus the full tree and options info was available at that point. But then parts of the resulting parse-tree are extracted with org-element-map and are exported separately as data later on. In that case, I don't know how to pass the original 'info' plist to the export function, so export results are not complete due to the missing context information. Here is a minimal example: With file minimal.org #+begin_src org * A B #+end_src I call #+begin_src emacs-lisp (setq parse-tree (with-current-buffer (find-file-noselect "/path/to/minimal.org") (org-element-parse-buffer))) (let ((elem (org-element-map parse-tree 'headline 'identity nil t))) (insert (format "\n\n%s\n\n" elem)) ;; nil instead of info as 3rd parameter (insert (org-export-data-with-backend elem 'html nil))) #+end_src and get (note the incomplete IDs in the html) #+begin_quote (headline (:raw-value A :begin 1 :end 7 :pre-blank 0 :hiddenp nil :contents-begin 5 :contents-end 7 :level 1 :priority nil :tags nil :todo-keyword nil :todo-type nil :post-blank 0 :footnote-section-p nil :archivedp nil :commentedp nil :quotedp nil :CATEGORY nil :title (A) :parent (org-data nil #0)) (section (:begin 5 :end 7 :contents-begin 5 :contents-end 7 :post-blank 0 :parent #0) (paragraph (:begin 5 :end 7 :contents-begin 5 :contents-end 7 :post-blank 0 :post-affiliated 5 :parent #1) B )))

A

B

#+end_quote How could I get my hands on the 'info' plist during the buffer parsing and save it for later use in calls like #+begin_src emacs-lisp (org-export-data-with-backend elem 'html info) #+end_src ? -- cheers, Thorsten