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: how to enable minted instead of verbatim in generate latex format from markdown
Date: Mon, 22 Oct 2012 12:57:58 -0700 (PDT)	[thread overview]
Message-ID: <9ee3b098-d73c-460e-97c4-7cd1d4c430b3@googlegroups.com> (raw)

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

From pandoc release, it is mentioned that "minted" latex package is 
supported besides verbatim since 1.9.1.2

Currently if I set normal code segment like

    $ pandoc -v

It will use "\begin{verbatim}"

~~~ {.bash}
$ pandoc -v
~~~

It will generate 

\begin{Shaded}
\begin{Highlighting}[]
\NormalTok{$ pandoc -v }
\end{Highlighting}
\end{Shaded}

How can I generate minted based latex instead ?

BTW: minted seems is better for code syntax highlight

rgs/larry

-- 
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
To view this discussion on the web visit https://groups.google.com/d/msg/pandoc-discuss/-/YyPePFbZm3EJ.
For more options, visit https://groups.google.com/groups/opt_out.



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

             reply	other threads:[~2012-10-22 19:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 19:57 Larry Cai [this message]
     [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

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=9ee3b098-d73c-460e-97c4-7cd1d4c430b3@googlegroups.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).