Re: [O] [Exporter] How to save 'info' plist for later use?

[Eric Abrahamsen]

Thorsten Jolitz <address@hidden> writes:

> Nick Dokos <address@hidden> writes:
>
>> Thorsten Jolitz <address@hidden> writes:
>>
>>> Thorsten Jolitz <address@hidden> 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?

If you look in the `org-export-as' function, you can see the part where
the info plist is built, looks like most of it is done by
org-export--get-buffer-attributes.