Sébastien Miquel writes:
> The point of my proposal is to allow one to write unescaped latex in
> the latex src block. (Mostly to avoid doubling every backslash). It is
> quite the shame to have to write non latex code in a latex src block.
Ahhh, sorry --- I focused on the wrong part of your e
Hi Sebastien,
I have encountered issues with this before when trying to noweb code
into a string that was code to be sent via ssh. I ended up switching
to use typeset -f in bash in most cases now, but that is not possible
for other languages. Some languages also have enough different types
of s
Timothy writes:
Just quickly, this works:
#+begin_src emacs-lisp :noweb yes
(setq my-latex-code "\
<>
")
#+end_src
I don't understand the purpose of your backslash, is it a typo ? With
or without it, this doesn't tangle to working lisp with my example.
The point of my proposal is to allow on
Sébastien Miquel writes:
> #+BEGIN_SRC latex :noweb-ref latex-ref
> \some \multiline
> \unescaped \latex \code
> #+END_SRC
>
> #+BEGIN_SRC emacs-lisp :noweb yes
> (setq my-latex-code "<>\n")
> #+END_SRC
>
> I don't think there's any way to achieve such functionality currently.
Just quickly, th
Hi,
Would there be some interest in extending the noweb syntax to allow
for string escaped expansion ?
I've modified my setup so that if the noweb delimiter `<<` is preceded
by a quote `"` then the expansion is string escaped (and the prefix
isn't duplicated for each line). This allows the follo
