From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Sam Reckoner <reckoner-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: RST to LaTeX with highlight directive?
Date: Fri, 08 Feb 2019 17:41:44 -0800 [thread overview]
Message-ID: <yh480k1s4hsppj.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <a4ea56dc-3217-44ef-9b9f-5e733b417458-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
If I understand correctly,
.. highlight:: python
causes python to be used as the default syntax for
code blocks, unless they're marked differently?
Looks like it's a special sphinx directive. In
general, we aim to support standard rst. But I
suppose it could be useful to support common
sphinx directives as well.
Feel free to submit an issue requesting this on our
github issue tracker (jgm/pandoc).
A possible workaround is to use a lua filter to
insert the 'python' class into every code block.
(Easy.)
Sam Reckoner <reckoner-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Hi,
>
> I have a large number of rst documents that I am trying to convert to
> latex. The rst documents contain the .. highlight:: python directive which
> causes the literal blocks to be code formatted correctly but when I do the
> pandoc conversion, the resulting latex does not produce the corresponding
> highlights. I am doing this on the command line with pandoc 2.2.3.2 on
> Ubuntu bionic.
>
> pandoc -s foo.rst -o foo.tex
>
> For other reasons I cannot use the .. code: python directive.
>
> Thanks in advance.
>
> --
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a4ea56dc-3217-44ef-9b9f-5e733b417458%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2019-02-09 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 22:32 Sam Reckoner
[not found] ` <a4ea56dc-3217-44ef-9b9f-5e733b417458-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-02-09 1:41 ` John MacFarlane [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=yh480k1s4hsppj.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=reckoner-Re5JQEeQqe8AvxtiuMwx3w@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).