From: Toby Speight <streapadair@gmx.net>
Subject: Re: URLs containing `?' are not fully comprehended
Date: 18 May 2000 11:22:44 +0100 [thread overview]
Message-ID: <uln189myz.fsf@lanber.cam.eu.citrix.com> (raw)
In-Reply-To: Steinar Bang's message of "17 May 2000 17:40:09 +0200"
Steinar> Steinar Bang <URL:mailto:sb@metis.no>
>>>>> Toby Speight <streapadair@gmx.net>:
>>
>> While we're on URL highlighting, some folks use <...> instead of
>> <URL:...> to delimit multi-line URLs. Is it possible for us to
>> accommodate this use? (IME, it's becoming more common)
0> In article <whbt25rxra.fsf@viffer.metis.no>, Steinar wrote:
Steinar> Well... Message-Ids also commonly reside inside <...>.
But they don't normally[1] begin with "http:", "ftp:", "mailto:", or
any of the other scheme names Gnus recognises. I'm not after matching
bare hostnames in this case (as I think they're evil anyway), just that
the existing[2] matches be multi-line if they're immediately preceded
by "<". I think we're reaching the limits of regexps with this stuff
now - but is there a sufficiently user-configurable alternative?
[1] I can handle _occasional_ false positives
[2] before the over-liberalisation that's caused so much talk here
next prev parent reply other threads:[~2000-05-18 10:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-16 18:24 Karl Kleinpaste
2000-05-16 19:29 ` Arne Jørgensen
2000-05-16 19:37 ` Bjørn Mork
2000-05-16 20:10 ` Simon Josefsson
2000-05-16 21:00 ` Kai Großjohann
2000-05-17 14:21 ` Toby Speight
2000-05-17 16:21 ` Andreas Fuchs
2000-05-17 11:46 ` Per Abrahamsen
2000-05-17 12:17 ` Karl Kleinpaste
2000-05-17 17:55 ` Per Abrahamsen
2000-05-17 14:23 ` Toby Speight
2000-05-17 15:40 ` Steinar Bang
2000-05-18 10:22 ` Toby Speight [this message]
2000-05-19 0:31 ` Russ Allbery
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=uln189myz.fsf@lanber.cam.eu.citrix.com \
--to=streapadair@gmx.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;
as well as URLs for NNTP newsgroup(s).