Aloha all,
The noweb strip-export setting leaves empty lines in the export.
I have this ecm:
#+name: foo
#+begin_src elisp
(+ 1 1)
#+end_src
#+name: bar
#+header: :noweb strip-export
#+begin_src elisp
<>
(+ 2 2)
#+end_src
LaTeX export renders this:
Hi Joost,
2015ko azaroak 8an, Joost Helberg-ek idatzi zuen:
>
> Dear Aaron,
>
> I was running close to the development version, but not close
> enough. It's solved now in the current version of org-mode.
>
> At first I accepted this odd behaviour, but then I realized htmlize is
> supposed to
>>>>> "Aaron" == Aaron Ecay <aarone...@gmail.com> writes:
> From: Aaron Ecay <aarone...@gmail.com>
> To: Joost Helberg <jo...@snow.nl>, emacs-orgmode@gnu.org
> Subject: Re: [O] :noweb no-export and syntax highlighting upon export
> Date: 2015-
ls,
In the org-code below syntax highlighting in both code-blocks in the
emacs-buffer is fine, but the html-export only works nice in case of
using :noweb yes, the no-export option screws up syntax highlighting in
the html-output (two screenshots included).
I understood that htmlize is used for
Hi Joost,
Org’s html export relies on the syntax of the source block being valid
in the block’s language, for the corresponding emacs major mode to
highlight it properly. In general, I wouldn’t rely on it behaving
properly in the presence of unexpanded noweb references. That said...
2015ko
Hi Tom,
I just pushed up a fix and a test, please let me know if the problem
persists.
Cheers,
t...@tsdye.com (Thomas S. Dye) writes:
Hi Eric,
The :noweb no-export option depends on the value of :exports in an
unexpected way.
If :exports code, then the noweb references are not expanded
Hi Eric,
The :noweb no-export option depends on the value of :exports in an
unexpected way.
If :exports code, then the noweb references are not expanded on export
to LaTeX, as expected.
If :exports both, then the noweb references are expanded on export to
LaTeX.
All the best,
Tom
--
Thomas
