From: Xinglu Chen <public@yoctocell.xyz>
To: Kyle Meyer <kyle@kyleam.com>
Cc: 48033@debbugs.gnu.org
Subject: [bug#48033] [PATCH] gnu: public-inbox: Update to 1.6.1.
Date: Thu, 29 Apr 2021 14:18:05 +0200 [thread overview]
Message-ID: <87sg39uvwi.fsf@yoctocell.xyz> (raw)
In-Reply-To: <87r1iut6rz.fsf@kyleam.com>
On Wed, Apr 28 2021, Kyle Meyer wrote:
>> Also,
>> lib/PublicInbox/WwwHighlight.pm has this comment:
>>
>> # TODO: support highlight(1) for distros which don't package the
>> # SWIG extension. Also, there may be admins who don't want to
>> # have ugly SWIG-generated code in a long-lived Perl process.
>>
>> Maybe this will become true in the future. :)
>
> Yeah :) Or even pygments support:
> https://public-inbox.org/meta/20191008215321.GA23962@dcvr/
That would be even better :)
I will send an updated series for this.
next prev parent reply other threads:[~2021-04-29 12:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 12:35 [bug#48033] [PATCH] gnu: public-inbox: Update to 1.6.1 Xinglu Chen
2021-04-27 0:59 ` Kyle Meyer
2021-04-27 1:09 ` Kyle Meyer
2021-04-27 20:21 ` Xinglu Chen
2021-04-27 21:03 ` Xinglu Chen
2021-04-28 4:22 ` Kyle Meyer
2021-04-28 13:16 ` Xinglu Chen
2021-04-28 21:53 ` Kyle Meyer
2021-04-29 12:18 ` Xinglu Chen [this message]
2021-04-29 12:37 ` [bug#48033] [PATCH v2 0/2] Update public-inbox " Xinglu Chen
2021-04-29 12:37 ` [bug#48033] [PATCH v2 1/2] gnu: Add perl-linux-inotify2 Xinglu Chen
2021-04-29 12:37 ` [bug#48033] [PATCH v2 2/2] gnu: public-inbox: Update to 1.6.1 Xinglu Chen
2021-04-30 23:49 ` Kyle Meyer
2021-05-01 12:01 ` Xinglu Chen
2021-05-01 12:04 ` [bug#48033] [PATCH v3 0/2] Update public-inbox " Xinglu Chen
2021-05-01 12:05 ` [bug#48033] [PATCH v3 1/2] gnu: Add perl-linux-inotify2 Xinglu Chen
2021-05-01 12:05 ` [bug#48033] [PATCH v3 2/2] gnu: public-inbox: Update to 1.6.1 Xinglu Chen
2021-05-03 16:27 ` bug#48033: [PATCH] " Ludovic Courtès
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=87sg39uvwi.fsf@yoctocell.xyz \
--to=public@yoctocell.xyz \
--cc=48033@debbugs.gnu.org \
--cc=kyle@kyleam.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.