From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: inline code and minted
Date: Fri, 05 Feb 2016 16:01:20 +0100 [thread overview]
Message-ID: <m2egcr5hhb.fsf@charm-ecran.irisa.fr> (raw)
In-Reply-To: <87egcrqo22.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Fri, 05 Feb 2016 14:33:41 +0100")
[-- Attachment #1.1: Type: text/plain, Size: 272 bytes --]
On 2016-02-05 14:33, Nicolas Goaziou <mail@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.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-ox-latex.el-Fix-minted-inline.patch --]
[-- Type: text/x-patch, Size: 1038 bytes --]
From aa8c0fa91af7a9307491bad78d7f82ce1705a7bd Mon Sep 17 00:00:00 2001
From: Alan Schmitt <alan.schmitt@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
[-- Attachment #1.3: Type: text/plain, Size: 611 bytes --]
>> - 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2016-02-05 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 10:07 inline code and minted Alan Schmitt
2016-02-05 13:33 ` Nicolas Goaziou
2016-02-05 15:01 ` Alan Schmitt [this message]
2016-02-05 17:15 ` Kaushal Modi
2016-02-05 17:27 ` Nicolas Goaziou
2016-02-06 8:53 ` Alan Schmitt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2egcr5hhb.fsf@charm-ecran.irisa.fr \
--to=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.