user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: Alyssa Ross <hi@alyssa.is>,
	meta@public-inbox.org,
	Amitai Schleier <schmonz-web-ikiwiki@schmonz.com>
Subject: Re: [PATCH] TODO: add an item for Python pygments
Date: Tue, 8 Oct 2019 18:00:54 -0400	[thread overview]
Message-ID: <20191008220054.GB3591@pure.paranoia.local> (raw)
In-Reply-To: <20191008215321.GA23962@dcvr>

On Tue, Oct 08, 2019 at 09:53:21PM +0000, Eric Wong wrote:
> Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> > On Thu, Sep 26, 2019 at 01:59:53AM +0000, Eric Wong wrote:
> > > I had my reservations about relying on highlight.pm; and this
> > > confirms them, unfortunately :<  Oh well...
> > 
> > I was also unable to find highlight.pm 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? :>

I think it's pretty clear to anyone who's looked at my projects that I'm
a "sysadmin who also writes python code when he needs to" and not really
what one would call a "proper developer." :)

I mean, heck, almost none of my projects have any tests.

So, you don't really want my help. ;)

-K

  reply	other threads:[~2019-10-08 22:00 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     ` [PATCH] TODO: add an item for Python pygments Eric Wong
2019-10-08 22:00       ` Konstantin Ryabitsev [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

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

  git send-email \
    --in-reply-to=20191008220054.GB3591@pure.paranoia.local \
    --to=konstantin@linuxfoundation.org \
    --cc=e@80x24.org \
    --cc=hi@alyssa.is \
    --cc=meta@public-inbox.org \
    --cc=schmonz-web-ikiwiki@schmonz.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).