Thorsten Jolitz tjol...@gmail.com writes:
I'm not sure about what you want to do with the parse tree. The usual
function to work with it is `org-element-map'. You may want to have
a look at its docstring, as it contains examples.
I want to write an 'unusual' backend that does not need
Nicolas Goaziou n.goaz...@gmail.com writes:
I want to write an 'unusual' backend that does not need anything else
from the exporting framework but the parse-tree as a list.
Then you don't want the exporting framework at all, only org-element.el.
yes, only the parser.
Anyway I'm confused.
Thorsten Jolitz tjol...@gmail.com writes:
[continuation, prior message sent unfinished by accident]
but with your other hints, I now understand the problem. I wanted to see
how the parse tree looks like, so I printed it out (I did not know about
the existance of 'print-circle' then, but it
Hi List,
here is an excerpt of a parse tree produced with
'org-element-parse-buffer':
,-
| (section (:begin 1 :end 624 :contents-begin
| 1 :contents-end 623 :post-blank 1 :parent #0) (keyword (:key
| TITLE :value Program Blues for
Hello,
Thorsten Jolitz tjol...@gmail.com writes:
here is an excerpt of a parse tree produced with
'org-element-parse-buffer':
,-
| (section (:begin 1 :end 624 :contents-begin
| 1 :contents-end 623 :post-blank 1 :parent #0)
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
I'm not sure about what you want to do with the parse tree. The usual
function to work with it is `org-element-map'. You may want to have
a look at its docstring, as it contains examples.
I want to write an 'unusual' backend that does not
