As someone who writes about technical topics, I'd like to use org-babel in my blog.
Examples
Table Generation
For example the following snippet is only exported as source block:
#+begin_src emacs-lisp :exports both
'((a b c) (d e f))
#+end_src
Whereas org-export correctly renders the results (output of org-org-export-as-org):
#+begin_src emacs-lisp
'((a b c) (d e f))
#+end_src
#+results:
| a | b | c |
| d | e | f |
Using call
The following source block is rendered to This is a greeting: . (call is not executed):
#+NAME: greeting
#+begin_src emacs-lisp :exports results :results silent :var name=""
(format "Hello %s, nice to meet you" name)
#+end_src
This is a greeting: call_greeting(name="Emacs").
Whereas org-export correctly renders the results (output of org-org-export-as-org):
This is a greeting: =Hello Emacs, nice to meet you=.
Suggestion
Add a filter that can transform the source, e.g. via org-org-export-as-org.
Things to consider
Calling org-org-export-as-org on each source file during export could get very slow and/or have unexpected consequences (e.g. when the babel code touches the disk).
As someone who writes about technical topics, I'd like to use org-babel in my blog.
Examples
Table Generation
For example the following snippet is only exported as source block:
Whereas
org-exportcorrectly renders the results (output oforg-org-export-as-org):Using
callThe following source block is rendered to
This is a greeting: .(callis not executed):Whereas
org-exportcorrectly renders the results (output oforg-org-export-as-org):Suggestion
Add a filter that can transform the source, e.g. via
org-org-export-as-org.Things to consider
Calling
org-org-export-as-orgon each source file during export could get very slow and/or have unexpected consequences (e.g. when the babel code touches the disk).