From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] Unwrap br0ken URLs.
Date: Thu, 28 Feb 2008 09:29:49 -0800 [thread overview]
Message-ID: <1204219598-sup-1190@south> (raw)
In-Reply-To: <12034162702820-git-send-email-nicolas.pouillard@gmail.com>
I would love to have a feature like this in Sup. This patch still has
some issues in terms of being over-aggressive. What I would really like
to see as a starting point is a corpus of broken URL examples that we
can build unit tests of. Then we can tweak these regexes until we get
something that has both high precision and high recall.
Also, have you looked at URI.regexp? I think that can do a lot of the
dirty work.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-02-28 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 10:17 Nicolas Pouillard
2008-02-28 17:29 ` William Morgan [this message]
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=1204219598-sup-1190@south \
--to=wmorgan-sup@masanjin.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox