Hi,
This has had me thinking about the exportation of blocks in general. I
think it makes sense to pull block exportation out into it's own
component both for simplicity and for ease of code-reading, hacking, and
customization.
with a set of blocks of forms like...
#+begin_html
#+begin_src
#+
Thanks for the pointer,
I'll be sure to follow that path for any future work on this front.
-- Eric
Carsten Dominik <[EMAIL PROTECTED]> writes:
> Hi Eric,
>
> I think this interesting functionality could at least initially
> be implemented as a add-on, hooking into `org-export-preprocess-hook'.
Hi Eric,
I think this interesting functionality could at least initially
be implemented as a add-on, hooking into `org-export-preprocess-hook'.
This hook is called before Org looks at any of the blocks, so the hook
could remove blocks or format them and replace them with finished
HTML (in the cas
Carsten Dominik <[EMAIL PROTECTED]> writes:
> Hi Eric,
>
> I think this interesting functionality could at least initially
> be implemented as a add-on, hooking into `org-export-preprocess-hook'.
> This hook is called before Org looks at any of the blocks, so the hook
> could remove blocks or form
On Nov 12, 2008, at 3:03 AM, Eric Schulte wrote:
Carsten Dominik <[EMAIL PROTECTED]> writes:
Hi Eric,
I think this interesting functionality could at least initially
be implemented as a add-on, hooking into `org-export-preprocess-
hook'.
This hook is called before Org looks at any of the bl