From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 462001F462 for ; Wed, 24 Apr 2019 23:02:14 +0000 (UTC) From: Eric Wong To: meta@public-inbox.org Subject: [PATCH 1/5] wwwhighlight: do linkification, too Date: Wed, 24 Apr 2019 23:02:10 +0000 Message-Id: <20190424230214.2378-2-e@80x24.org> In-Reply-To: <20190424230214.2378-1-e@80x24.org> References: <20190424230214.2378-1-e@80x24.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: Otherwise, there's no reason to use this API over highlight(1). Maybe this can be an option in the future; but I'm struggling to find a reason to not do it by default. --- lib/PublicInbox/WwwHighlight.pm | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/lib/PublicInbox/WwwHighlight.pm b/lib/PublicInbox/WwwHighlight.pm index 0191640..d8101b7 100644 --- a/lib/PublicInbox/WwwHighlight.pm +++ b/lib/PublicInbox/WwwHighlight.pm @@ -24,6 +24,7 @@ use warnings; use bytes (); # only for bytes::length use HTTP::Status qw(status_message); use parent qw(PublicInbox::HlMod); +use PublicInbox::Linkify qw(); # TODO: support highlight(1) for distros which don't package the # SWIG extension. Also, there may be admins who don't want to @@ -64,7 +65,10 @@ sub call { return r(405) if $req_method ne 'PUT'; my $bref = read_in_full($env) or return r(500); + my $l = PublicInbox::Linkify->new; + $l->linkify_1($$bref); $bref = $self->do_hl($bref, $env->{PATH_INFO}); + $l->linkify_2($$bref); my $h = [ 'Content-Type', 'text/html; charset=UTF-8' ]; push @$h, 'Content-Length', bytes::length($$bref); -- EW