Re: [O] new exporter

[Nicolas Goaziou]

Hello,

Achim Gratz <address@hidden> writes:

> Achim Gratz writes:
>> This causes the (current-buffer) to expand literally into the byte-code
>> (look at the byte-code!) instead of being compiled as a function, which
>> obviously isn't going to work.  This does not happen if I either remove
>> the cond form or if I wrap the BODY in save-restriction in progn, but I
>> haven't done any further investigation if the code still works with that
>> change and if maybe there are other places that are similarly struck.
>
> No, that's not right... as long as I compile org-export.el in isolation,
> it compiles correctly.  It croaks if I compile either one of
> org-e-html.el or org-e-odt.el in the same session.  These are the two
> backends that have a (require 'org-export) in them.

Speaking about that, as you suggested already, we should move,
temporarily, the dispatcher into another file (i.e. org-e-extra.el)
which would require everything (org-element, org-export, org-e-publish,
org-e-latex,...) and have _every_ back-end require org-export and
org-element only.

That may not solve the problem, but could at least simplify it.

Is that fine?


Regards,

-- 
Nicolas Goaziou