From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [Exporter] How to save 'info' plist for later use?
Date: Wed, 10 Jul 2013 18:57:31 +0200 [thread overview]
Message-ID: <87a9lufj44.fsf@gmail.com> (raw)
In-Reply-To: 87sizmifsy.fsf@ericabrahamsen.net
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> Nick Dokos <ndokos@gmail.com> writes:
>>
>>> Thorsten Jolitz <tjolitz@gmail.com> writes:
>>>
>>>> Thorsten Jolitz <tjolitz@gmail.com> 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.
Thanks for the tip, sometimes its obvious that some functionality is
already implemented, but not so obvious whats the name attached to it.
Looking in the source-code is of course the best way to find out, but I
thought I would have access to all function-names anyway with
,----------------------
| C-h f org-export- TAB
`----------------------
until I figured out that defining some autoloads and actually loading
the whole library are two different things, and that I will find all
functions that way only after doing an explicit 'M-x load-library' or
after actually using it ... ;)
--
cheers,
Thorsten
next prev parent reply other threads:[~2013-07-10 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 10:56 [Exporter] How to save 'info' plist for later use? Thorsten Jolitz
2013-07-10 11:34 ` Robert Klein
2013-07-10 12:21 ` Thorsten Jolitz
2013-07-10 15:41 ` Eric Abrahamsen
2013-07-10 11:46 ` Thorsten Jolitz
2013-07-10 12:17 ` Nick Dokos
2013-07-10 12:30 ` Thorsten Jolitz
2013-07-10 13:59 ` Jambunathan K
2013-07-10 15:33 ` Thorsten Jolitz
2013-07-10 15:40 ` Eric Abrahamsen
2013-07-10 16:57 ` Thorsten Jolitz [this message]
2013-07-10 17:16 ` Jambunathan K
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=87a9lufj44.fsf@gmail.com \
--to=tjolitz@gmail.com \
--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).