From: Bill Janssen <bill.janssen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pygments 'console' style
Date: Thu, 21 Sep 2017 15:41:43 -0700 (PDT) [thread overview]
Message-ID: <ad8bd961-c9ad-4380-838d-4b8068a930a2@googlegroups.com> (raw)
In-Reply-To: <20170921222732.GB73159-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 3122 bytes --]
Sorry, I should have been more prolix. My documents have lots of examples
of people interacting with a read-eval-print loop in a terminal session.
Things like
$ date
Thu Sep 21 15:29:07 PDT 2017
$
The ideal console mode (or "repl" or "typescript", two other names for this
kind of text) does a good job of identifying user inputs versus program
outputs -- I'm not sure how well the Pygments lexer does at this. The
inputs are usually boldfaced, the outputs normal. Handles '#' and '%'
prompts, stuff before the prompt, etc.
'bash', on the other hand, is just highlighting for the bash language, as
far as I know.
I haven't found documentation on how to add support for a new language
highlighter; is there a link?
Bill
On Thursday, September 21, 2017 at 3:27:40 PM UTC-7, John MacFarlane wrote:
>
> Pandoc doesn't actually use pygments at all.
> It has a style named 'pygments' because it imitates
> pygments' default style, but the highlighting is all
> done by a Haskell library, skylighting.
>
> It uses definitions from KDE
> https://cgit.kde.org/syntax-highlighting.git/tree/data/syntax
>
> I don't see 'console' -- there is 'bash', which might work
> for your purposes -- I'm not sure what 'console' does.
>
> +++ Bill Janssen [Sep 21 17 15:15 ]:
> > Pandoc doesn't seem to recognize the 'console' language tag supported
> > by Pygments. Am I just missing it? If not, is there some way to add
> > it?
> > Bill
> >
> > --
> > 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>.
> > To post to this group, send email to
> > [2]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>.
> > To view this discussion on the web visit
> > [3]
> https://groups.google.com/d/msgid/pandoc-discuss/05541691-dbb5-48b4-
> > ac2a-a0f986fcb25e%40googlegroups.com.
> > For more options, visit [4]https://groups.google.com/d/optout.
> >
> >References
> >
> > 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>
> > 2. mailto:pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>
> > 3.
> https://groups.google.com/d/msgid/pandoc-discuss/05541691-dbb5-48b4-ac2a-a0f986fcb25e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> > 4. https://groups.google.com/d/optout
>
>
--
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/ad8bd961-c9ad-4380-838d-4b8068a930a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 436053 bytes --]
next prev parent reply other threads:[~2017-09-21 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 22:15 Bill Janssen
[not found] ` <05541691-dbb5-48b4-ac2a-a0f986fcb25e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-21 22:27 ` John MACFARLANE
[not found] ` <20170921222732.GB73159-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2017-09-21 22:41 ` Bill Janssen [this message]
[not found] ` <ad8bd961-c9ad-4380-838d-4b8068a930a2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-22 17:37 ` 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=ad8bd961-c9ad-4380-838d-4b8068a930a2@googlegroups.com \
--to=bill.janssen-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).