Thorsten Jolitz writes:
> 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 a
Eric Abrahamsen writes:
> Thorsten Jolitz writes:
>
>> 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 f
Thorsten Jolitz writes:
> Robert Klein writes:
>
> Hi Robert,
>
>> I'm currently playing around with retrieving options, e.g. functions like:
>
>> #+begin_src elisp
>> (defun org-find-export-option (file option-name &optional backend) ...
>
> thanks, that brought me on the right track, I was sea
Thorsten Jolitz writes:
> 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 i
Jambunathan K writes:
> Add a filter or a translator. One of the arguments to that filter is
> the plist you are looking for. Work back from there and you will get
> the right APIs to use.
>
> The snippet below from ox-odt.el should be a good starting point for
> further exploration. The trans
Add a filter or a translator. One of the arguments to that filter is
the plist you are looking for. Work back from there and you will get
the right APIs to use.
The snippet below from ox-odt.el should be a good starting point for
further exploration. The translators do fairly *non-trivial*
tra
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 m
Robert Klein writes:
Hi Robert,
> I'm currently playing around with retrieving options, e.g. functions like:
> #+begin_src elisp
> (defun org-find-export-option (file option-name &optional backend) ...
thanks, that brought me on the right track, I was searching for
functions containing '-info-
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
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
Hi Thorsten,
I'm currently playing around with retrieving options, e.g. functions like:
#+begin_src elisp
(defun org-find-export-option (file option-name &optional backend)
"Find the OPTION of FILE."
(let* ((org-inhibit-startup t)
(visiting (find-buffer-visiting file))
(bu
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
r
12 matches
Mail list logo