user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
To: Konstantin Ryabitsev <>
Cc: Alyssa Ross <>,,
	Amitai Schleier <>
Subject: [PATCH] TODO: add an item for Python pygments
Date: Tue, 8 Oct 2019 21:53:21 +0000	[thread overview]
Message-ID: <20191008215321.GA23962@dcvr> (raw)
In-Reply-To: <20190926131836.GB10467@chatter.i7.local>

Konstantin Ryabitsev <> wrote:
> On Thu, Sep 26, 2019 at 01:59:53AM +0000, Eric Wong wrote:
> > I had my reservations about relying on; and this
> > confirms them, unfortunately :<  Oh well...
> I was also unable to find anywhere outside of Debian packages.
> > I wonder if pygments or any other code highlighting packages are
> > more stable.  We'd need to use a pipe or socket to interact with
> > pygments or anything w/o Perl bindings.
> I'd be quite happy to be able to use pygments!

Can you write the Python glue? :>

Subject: [PATCH] TODO: add an item for Python pygments

Pygments seems to be a popular highlighter and widely available,
so we'll be providing support for that at some point...

 TODO | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/TODO b/TODO
index 93054bb3..566e0a40 100644
--- a/TODO
+++ b/TODO
@@ -115,3 +115,6 @@ all need to be considered for everything we introduce)
 * support searching based on `git-patch-id --stable` to improve
   bidirectional mapping of commits <=> emails
+* pygments support - via Python script similar to `git cat-file --batch'
+  to avoid startup penalty.  pygments.rb (Ruby) can be inspiration, too.

  parent reply	other threads:[~2019-10-08 21:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24 20:05 [PATCH] hlmod: update for highlight 3.51 API change Alyssa Ross
2019-09-26  1:59 ` Eric Wong
2019-09-26 13:18   ` Konstantin Ryabitsev
2019-09-26 15:07     ` Alyssa Ross
2019-10-08 21:53     ` Eric Wong [this message]
2019-10-08 22:00       ` [PATCH] TODO: add an item for Python pygments Konstantin Ryabitsev
2019-09-26 15:08   ` [PATCH] hlmod: update for highlight 3.51 API change Alyssa Ross

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191008215321.GA23962@dcvr \ \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).