Hello,
I'm forwarding this question asked on stackexchange:
http://tex.stackexchange.com/questions/186605/with-orgtbl-how-to-ensure-
that-braces-and-dollars-are-not-escaped
After some investigation, it seems that the behavior is hidden deep in the
export routines, and I was wisely suggested
Hello,
Thibaut Verron thibaut.ver...@gmail.com writes:
I'm forwarding this question asked on stackexchange:
http://tex.stackexchange.com/questions/186605/with-orgtbl-how-to-ensure-
that-braces-and-dollars-are-not-escaped
After some investigation, it seems that the behavior is hidden deep
Now, are these limitations of Org really preventing it from exporting a
string verbatim? That would seem like the most logical default in this
situation, wouldn't it? (Disclaimer: I don't understand the limitations of
Org, so these last questions may be ridiculous to someone who does)
2014-06-26 12:38 GMT+02:00 Nicolas Goaziou m...@nicolasgoaziou.fr:
Hello,
Thibaut Verron thibaut.ver...@gmail.com writes:
I'm forwarding this question asked on stackexchange:
http://tex.stackexchange.com/questions/186605/with-orgtbl-how-to-ensure-
that-braces-and-dollars-are-not-escaped
Thibaut Verron thibaut.ver...@gmail.com writes:
Now, are these limitations of Org really preventing it from exporting a
string verbatim? That would seem like the most logical default in this
situation, wouldn't it?
I disagree in the general case. The most logical default for Org is to
treat
2014-06-26 15:17 GMT+02:00 Nicolas Goaziou m...@nicolasgoaziou.fr:
Thibaut Verron thibaut.ver...@gmail.com writes:
Now, are these limitations of Org really preventing it from exporting
a
string verbatim? That would seem like the most logical default in this
situation, wouldn't it?
I
Thibaut Verron thibaut.ver...@gmail.com writes:
Would changing the last lines of `orgtbl-to-latex` to something like this
work as a long-term solution?
(require 'ox-latex)
(let* ((*orgtbl-verbatim* (plist-get params :verbatim))
(backend (if *orgtbl-verbatim* nil 'latex)))