From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: on matching more naked URLs in articles
Date: 26 Apr 2000 14:22:01 -0400 [thread overview]
Message-ID: <vxkog6w4t9y.fsf@mesquite.charcoal.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "22 Apr 2000 14:13:26 +0200"
<sarcasm> Bloody marvelous. </sarcasm>
Now, Gnus is urlifying stuff such as bash-2.04.tar.gz and 21.2.31.
I'm not at all convinced this is a good thing. The heuristic is
nowhere near adequately restrictive. Maybe (only maybe) if you
restrict the trailing component to TLDs, it would be adequate.
next prev parent reply other threads:[~2000-04-26 18:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-22 14:32 Steinar Bang
2000-04-21 12:17 ` Lars Magne Ingebrigtsen
2000-04-21 13:51 ` Steinar Bang
2000-04-21 18:43 ` Lars Magne Ingebrigtsen
2000-04-21 20:31 ` Steinar Bang
2000-04-21 22:24 ` David Aspinwall
2000-04-22 12:13 ` Lars Magne Ingebrigtsen
2000-04-26 18:22 ` Karl Kleinpaste [this message]
2000-04-27 8:35 ` Steinar Bang
2000-04-27 10:17 ` Toby Speight
2000-04-29 14:27 ` Thomas Skogestad
2000-04-29 20:36 ` François Pinard
[not found] ` <vxkog6w4t9y.fsf@mesquite.charcoal <3166007242308746@oakhurst.penguinpowered.com>
2000-04-29 15:44 ` Karl EICHWALDER
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=vxkog6w4t9y.fsf@mesquite.charcoal.com \
--to=karl@charcoal.com \
/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;
as well as URLs for NNTP newsgroup(s).