From 39005a442b1fa72a3c4008d414823a9073e354bb Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Wed, 24 Apr 2019 19:52:14 +0000 Subject: wwwhighlight: do linkification, too 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(+) (limited to 'lib') diff --git a/lib/PublicInbox/WwwHighlight.pm b/lib/PublicInbox/WwwHighlight.pm index 01916401..d8101b75 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); -- cgit v1.2.3-24-ge0c7