From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: inline code and minted
Date: Sat, 06 Feb 2016 09:53:08 +0100 [thread overview]
Message-ID: <m260y25iff.fsf@charm-ecran.irisa.fr> (raw)
In-Reply-To: <871t8rqd84.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Fri, 05 Feb 2016 18:27:39 +0100")
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On 2016-02-05 18:27, Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> Yes. Here it is for review, please let me know if I can apply it.
>
> Be my guest! Thank you.
Done.
>> I see. I think I’ll just use <code> then and skip the syntax coloring
>> for the moment.
>
> I'm not sure to understand your problem. src_emacs-lisp{(+ 1 1)} should
> get syntax coloring in both latex and html back-end.
I’m collaborating with some people who use org from elpa, so they do not
have access to the fix. For them I can set up a macro that does the
right thing in the latex case, but I don’t know to have backend-specific
code in the latex case and the default handling in the other cases.
In other words, right now I have this:
#+macro: coq @@latex:\mintinline{coq}{$1}@@@@html:<code>$1</code>@@
and I would like to replace the @@html: bit with the default inline
source code behavior except for latex export.
Best,
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 --]
prev parent reply other threads:[~2016-02-06 8:53 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
2016-02-05 17:15 ` Kaushal Modi
2016-02-05 17:27 ` Nicolas Goaziou
2016-02-06 8:53 ` Alan Schmitt [this message]
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m260y25iff.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).