On 2016-02-05 14:33, Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:
>> I have two questions: >> - should we support this and generate this code? > > Sure. Could you provide and apply a patch for that? Yes. Here it is for review, please let me know if I can apply it.
From aa8c0fa91af7a9307491bad78d7f82ce1705a7bd Mon Sep 17 00:00:00 2001
From: Alan Schmitt <alan.schm...@polytechnique.org>
Date: Fri, 5 Feb 2016 15:55:54 +0100
Subject: [PATCH] ox-latex.el: Fix minted inline
* lisp/ox-latex.el (org-latex-inline-src-block): Output minted code that
correctly formats code inline.
---
lisp/ox-latex.el | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index ec06b17..5879e40 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -2012,10 +2012,10 @@ contextual information."
(downcase org-lang)))
(options (org-latex--make-option-string
(plist-get info :latex-minted-options))))
- (concat (format "\\mint%s{%s}"
+ (format "\\mintinline%s{%s}{%s}"
(if (string= options "") "" (format "[%s]" options))
- mint-lang)
- separator code separator)))
+ mint-lang
+ code)))
;; Use listings package.
(otherwise
;; Maybe translate language's name.
--
2.7.0
>> - in the meantime, I created a macro that does this for latex, but it
>> does not work for html (it exports the “src_coq” string verbatim):
>> #+macro: coq @@latex:\mintinline{coq}{$1}@@@@html:src_coq[:exports
>> code]{$1}@@
>> Why is this macro wrong?
>
> Contents of an export snippet, e.g. @@html:...@@ are not evaluated by
> the back-end. IOW this is back-end code.
I see. I think I’ll just use <code> then and skip the syntax coloring
for the moment.
Thanks,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Athmospheric CO₂ (Updated February 4, 2016, Mauna Loa Obs.): 403.08 ppm
signature.asc
Description: PGP signature
