From: Salim B <salim.brueggemann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Using soul with Pandoc to highlight inline code spans
Date: Sun, 15 Oct 2017 07:42:06 -0700 (PDT) [thread overview]
Message-ID: <1d3fb97e-c9e1-4f86-ba91-0552e7c8d592@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1471 bytes --]
I've already asked that question over at Tex/Latex Stackexchange
<https://tex.stackexchange.com/questions/393522/using-soul-with-pandoc-to-highlight-inline-code-spans-texttt>,
but nobody answered so far. I've even earned the "tumbleweed" badge for it
– you only get that if you "*ask a question with zero score, no answers, no
comments, and low views for a week*" :p Somehow I get the feeling that the
Stackexchange community doesn't show too much love for Pandoc...
Anyway, I'd like to raise awareness for my question by opening this
discussion topic. Maybe someone here knows a solution to my problem
(highlighting inline code spans that span over multiple lines)? :)
I refrain from copying the whole issue here, please have a look a the
provided link to Stackexchange and ideally answer it there directly (if you
happen to be able to).
Thanks a lot,
Salim
--
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/1d3fb97e-c9e1-4f86-ba91-0552e7c8d592%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 404489 bytes --]
reply other threads:[~2017-10-15 14:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1d3fb97e-c9e1-4f86-ba91-0552e7c8d592@googlegroups.com \
--to=salim.brueggemann-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).