From: Steinar Bang <sb@metis.no>
Subject: on matching more naked URLs in articles
Date: 22 Jan 2000 15:32:13 +0100 [thread overview]
Message-ID: <whd7qup47m.fsf@viffer.metis.no> (raw)
Before I waste time on it: has anyone looked into changing
gnus-button-url-regexp into matching naked URLs without a protocol
field? Ie. URLs like dodrt.dod.no, vvv.no, imdb.com etc.
And is there a way to getting the changed gnus-button-url-regexp into
gnus-button-alist without restarting Gnus? (I suspect that ever
longer and more cryptic regexps require quick cycles of changing and
trying)
Todays gnus-button-url-regexp is
"\\b\\(s?https?\\|ftp\\|file\\|gopher\\|news\\|telnet\\|wais\\|mailto\\):\\(//[-a-zA-Z0-9_.]+:[0-9]*\\)?\\([-a-zA-Z0-9_=!?#$@~`%&*+|\\/:;.,]\\|\\w\\)+\\([-a-zA-Z0-9_=#$@~`%&*+|\\/]\\|\\w\\)"
I'm not sure where the best place to change it is. My first attempt
would be something like this:
"\\b\\(\\(s?https?\\|ftp\\|file\\|gopher\\|news\\|telnet\\|wais\\|mailto\\):\\(//[-a-zA-Z0-9_.]+:[0-9]*\\)?\\([-a-zA-Z0-9_=!?#$@~`%&*+|\\/:;.,]\\|\\w\\)+\\([-a-zA-Z0-9_=#$@~`%&*+|\\/]\\|\\w\\)\\|\\([A-Za-z]+\\.\\)+\\(com\\|org\\|no\\|se\\)\\(/[A-Za-z0-9/]+\\)?\\)"
I'm not sure if the top level domain should be from a fixed list, or
if we just should match [A-Za-z]? Are there efficiency reasons for
doing it either way?
Most URLs exchanged this way seems to be .com URLs or URLs in the
native national domain of a particular newsgroup.
next reply other threads:[~2000-01-22 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-22 14:32 Steinar Bang [this message]
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
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=whd7qup47m.fsf@viffer.metis.no \
--to=sb@metis.no \
/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).