public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Larry Cai <larry.caiyu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: how to enable minted instead of verbatim in generate latex format from markdown
Date: Tue, 23 Oct 2012 13:16:13 +0800	[thread overview]
Message-ID: <CAPzfJ9TWj_Q=Aju5t9Ujfrm4At_VdRtX2jVJ-wmPFnkYBaLfFw@mail.gmail.com> (raw)
In-Reply-To: <20121022215352.GA13799-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2178 bytes --]

Thank for quick reply, probably it is almost the same.

Currently I reuse the ProGit scripts to generate latex using pandoc, and
tune latex files in detail.

And In pdf, I want to have shade+syntax highlight, and expected latex code

\definecolor{bg}{rgb}{0.95,0.95,0.95}
\begin{minted}[bgcolor=bg]{bash}
$ sudo apt-get install ruby1.9.1
$ sudo apt-get install pandoc
$ sudo apt-get install texlive-xetex
$ sudo apt-get install texlive-latex-recommended
$ sudo apt-get install texlive-latex-extra
\end{minted}

// in my script, I will add [bgcolor=bg] into generated latex if minted is
used directly.

In current solution, highlighting-kate (or pygments ) will generate the
formatted latex instead.  While if minted package is used, it will handle
the syntax highlight in its package like virbatim, It is more clean for me
to handle.

There are some one2one mapping like line numbers as well.

rgs/larry

On Tue, Oct 23, 2012 at 5:53 AM, John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>wrote:

> minted is only supported by the LaTeX reader, not the LaTeX writer.
>
> +++ Larry Cai [Oct 22 12 12:57 ]:
>
> >    BTW: minted seems is better for code syntax highlight
>
> What features does minted have that you can't get with
> pandoc/highlighting-kate?
>
> --
> You received this message because you are subscribed to the Google Groups
> "pandoc-discuss" group.
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to
> pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>


-- 
True software development embraces consistent inconsistency.
blog: http://codeslife.com

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.



[-- Attachment #2: Type: text/html, Size: 4035 bytes --]

      parent reply	other threads:[~2012-10-23  5:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 19:57 Larry Cai
     [not found] ` <9ee3b098-d73c-460e-97c4-7cd1d4c430b3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2012-10-22 21:53   ` John MacFarlane
     [not found]     ` <20121022215352.GA13799-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2012-10-23  5:16       ` Larry Cai [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPzfJ9TWj_Q=Aju5t9Ujfrm4At_VdRtX2jVJ-wmPFnkYBaLfFw@mail.gmail.com' \
    --to=larry.caiyu-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).