Re: on matching more naked URLs in articles

[Toby Speight <streapadair@gmx.net>]

Steinar> Steinar Bang <URL:mailto:sb@metis.no>
Karl> Karl Kleinpaste <URL:mailto:karl@charcoal.com>

0> In article <vxkog6w4t9y.fsf@mesquite.charcoal.com>, Karl wrote:

Karl> <sarcasm> Bloody marvelous. </sarcasm>
Karl>
Karl> Now, Gnus is urlifying stuff such as bash-2.04.tar.gz and
Karl> 21.2.31.
Karl>
Karl> I'm not at all convinced this is a good thing.  The heuristic is
Karl> nowhere near adequately restrictive.  Maybe (only maybe) if you
Karl> restrict the trailing component to TLDs, it would be adequate.


0> In article <whk8hk0wn6.fsf@viffer.metis.no>, Steinar wrote:

Steinar> I don't see any problem in some non-URLs are highlighted, as
Steinar> long as the real ones are, and that saves me cutting and
Steinar> pasting.


This is obviously an area where personal preferences differ.  I think
we need to put some canned "loose" and "tight" regexps as :fixed
choices in the defcustom.

IOW, instead of

  :type 'regexp

we should have

  :type '(choice (const "<tight>" :tag "Match conservatively")
                 (const "<loose>" :tag "Match liberally")
                 (regexp :tag "User-defined"))

where the consts are suitable defaults for the two POVs.

I think we can assume that users either (a) use Customize, or (b) are
clueful enough to find the definition and copy the regexps from there.