On 2016-02-05 18:27, Nicolas Goaziou writes:
> Alan Schmitt 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 then and skip the syntax
On 2016-02-05 14:33, Nicolas Goaziou 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
On Fri, Feb 5, 2016 at 10:01 AM Alan Schmitt
wrote:
>
> Yes. Here it is for review, please let me know if I can apply it.
>
TIL that we can have inline source code highlighting in org exports!
For anyone else that just got enlightened about this, check out "C-h
Alan Schmitt writes:
> Yes. Here it is for review, please let me know if I can apply it.
Be my guest! Thank you.
> I see. I think I’ll just use then and skip the syntax coloring
> for the moment.
I'm not sure to understand your problem. src_emacs-lisp{(+ 1 1)}
Hello,
I see that
src_coq[:exports code]{nat}
exports to (latex export with minted)
\mint{coq}~nat~
which does not work as inline code here. The following would work,
however, with a recent minted:
\mintinline{coq}{nat}
I have two questions:
- should we support this and generate this code?
Hello,
Alan Schmitt writes:
> Hello,
>
> I see that
>
> src_coq[:exports code]{nat}
>
> exports to (latex export with minted)
>
> \mint{coq}~nat~
>
> which does not work as inline code here. The following would work,
> however, with a recent minted:
>
>