user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] linkify: implement Markdown link compatibility
Date: Tue,  6 Dec 2016 23:01:39 +0000	[thread overview]
Message-ID: <20161206230139.25292-1-e@80x24.org> (raw)

Although unescaped parentheses in URLs are technically allowed,
they are uncommon.  However, Markdown-like syntaxes are
unfortunately common for URLs, so we might as well support them.
---
 lib/PublicInbox/Linkify.pm | 15 +++++++++++----
 t/linkify.t                |  9 +++++++++
 2 files changed, 20 insertions(+), 4 deletions(-)

diff --git a/lib/PublicInbox/Linkify.pm b/lib/PublicInbox/Linkify.pm
index ea7fd71..cc0f7e3 100644
--- a/lib/PublicInbox/Linkify.pm
+++ b/lib/PublicInbox/Linkify.pm
@@ -15,7 +15,7 @@ use warnings;
 use Digest::SHA qw/sha1_hex/;
 
 my $SALT = rand;
-my $LINK_RE = qr{\b((?:ftps?|https?|nntps?|gopher)://
+my $LINK_RE = qr{(\()?\b((?:ftps?|https?|nntps?|gopher)://
 		 [\@:\w\.-]+/
 		 (?:[a-z0-9\-\._~!\$\&\';\(\)\*\+,;=:@/%]*)
 		 (?:\?[a-z0-9\-\._~!\$\&\';\(\)\*\+,;=:@/%]+)?
@@ -27,15 +27,22 @@ sub new { bless {}, shift }
 sub linkify_1 {
 	my ($self, $s) = @_;
 	$s =~ s!$LINK_RE!
-		my $url = $1;
+		my $beg = $1 || '';
+		my $url = $2;
 		my $end = '';
 
+		# Markdown compatibility:
+		if ($beg eq '(') {
+			$url =~ s/\)\z//;
+			$end = ')';
+		}
+
 		# it's fairly common to end URLs in messages with
 		# '.', ',' or ';' to denote the end of a statement;
 		# assume the intent was to end the statement/sentence
 		# in English
 		if ($url =~ s/([\.,;])\z//) {
-			$end = $1;
+			$end = $1 . $end;
 		}
 
 		# salt this, as this could be exploited to show
@@ -45,7 +52,7 @@ sub linkify_1 {
 		# only escape ampersands, others do not match LINK_RE
 		$url =~ s/&/&#38;/g;
 		$self->{$key} = $url;
-		'PI-LINK-'. $key . $end;
+		$beg . 'PI-LINK-'. $key . $end;
 	!ge;
 	$s;
 }
diff --git a/t/linkify.t b/t/linkify.t
index 49cbbd6..a794c78 100644
--- a/t/linkify.t
+++ b/t/linkify.t
@@ -57,4 +57,13 @@ use PublicInbox::Linkify;
 	is($s, qq(hello <a\nhref="$u">$u</a> world), "root + fragment");
 }
 
+{
+	my $l = PublicInbox::Linkify->new;
+	my $u = 'http://example.com/';
+	my $s = "[markdown]($u)";
+	$s = $l->linkify_1($s);
+	$s = $l->linkify_2($s);
+	is($s, qq![markdown](<a\nhref="$u">$u</a>)!, 'markdown compatible');
+}
+
 done_testing();
-- 
EW


             reply	other threads:[~2016-12-06 23:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-06 23:01 Eric Wong [this message]
2016-12-06 23:17 ` [PATCH] linkify: implement Markdown link compatibility Eric Wong
2016-12-06 23:42   ` [PATCH] linkify: implement Markdown link compatibility (again) Eric Wong

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: http://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=20161206230139.25292-1-e@80x24.org \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    /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).