From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Isn’t there a plain text reader? Why?
Date: Mon, 19 Aug 2019 11:17:58 -0400 [thread overview]
Message-ID: <fd7361b2-3428-f38f-38fc-e3fab8b63605@usa.net> (raw)
In-Reply-To: <CAE9z9A3zRg+9_v26kMR-9fb5HHykwQKDabiufWKSdHcNmMW0ag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 8/17/19 10:34 AM, Rudi C wrote:
> Thank you!
> I imagine there are aliases defined for `pandoc
> --list-highlight-languages`? Since specifying `py` seemed to work just
> as well as `python`, if I'm remembering correctly. If so, where should I
> edit in the sources ti add more aliases? (And send those edits as
> PRs)(Like, `el` could be an alias for `commonlisp` ...)
I haven't played with it to much at the moment - I assume that's part of
the Skylighting package.
Here's Pandoc's docs on highlighting, with links to how to create your
own, and to the highlighting package it uses:
<https://pandoc.org/MANUAL.html#syntax-highlighting>
Daniel T. Staal
--
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
next prev parent reply other threads:[~2019-08-19 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 17:08 Rudi C
[not found] ` <255f893b-1048-4de9-aaeb-e9778187e701-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-15 17:29 ` Daniel Staal
[not found] ` <4be8dffb-2e8c-3ba3-d584-a06928a48af7-Jdbf3xiKgS8@public.gmane.org>
2019-08-16 6:07 ` Rudi C
[not found] ` <CAE9z9A1PhS=xsySFLDMNUf8SPogT2Ka9SCoWE41XHYjmeKZFoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-16 14:32 ` Daniel Staal
[not found] ` <08494ac8-209d-dfa6-43b6-f19034f2bef7-Jdbf3xiKgS8@public.gmane.org>
2019-08-17 14:34 ` Rudi C
[not found] ` <CAE9z9A3zRg+9_v26kMR-9fb5HHykwQKDabiufWKSdHcNmMW0ag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-19 15:17 ` Daniel Staal [this message]
2019-08-20 6:24 ` John MacFarlane
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=fd7361b2-3428-f38f-38fc-e3fab8b63605@usa.net \
--to=dstaal-jdbf3xikgs8@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).