From: Michael Cook <michael.cook@cisco.com>
Subject: Re: gnus-article-unsplit-urls
Date: Fri, 04 Jan 2002 12:08:38 -0500 [thread overview]
Message-ID: <g08pu4q2gdl.fsf@zzz.cisco.com> (raw)
In-Reply-To: <m3wuyy5aw4.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 04 Jan 2002 17:38:51 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> But won't that match stuff like
>
> http://google.com/thing
> and then there's something else on the next line?
that's why i thought a washing function would be better. the
detection of the problem is not perfect. so you'd probably not want
it to happen implicitly. i figure more likely you'd see a broken
url, you'd mumble something under your breath about microsoft, you'd
type `W u', and then go about your business.
m.
next prev parent reply other threads:[~2002-01-04 17:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 14:58 gnus-article-unsplit-urls Michael Cook
2002-01-04 15:31 ` gnus-article-unsplit-urls Simon Josefsson
2002-01-04 15:38 ` gnus-article-unsplit-urls Michael Cook
2002-01-04 15:48 ` gnus-article-unsplit-urls Simon Josefsson
2002-01-04 16:37 ` gnus-article-unsplit-urls Lars Magne Ingebrigtsen
2002-01-04 17:27 ` gnus-article-unsplit-urls Simon Josefsson
2002-01-04 17:42 ` gnus-article-unsplit-urls Lars Magne Ingebrigtsen
2002-01-04 18:06 ` gnus-article-unsplit-urls Simon Josefsson
2002-01-04 15:44 ` gnus-article-unsplit-urls Simon Josefsson
2002-01-04 16:38 ` gnus-article-unsplit-urls Lars Magne Ingebrigtsen
2002-01-04 17:08 ` Michael Cook [this message]
2002-01-04 17:12 ` gnus-article-unsplit-urls Lars Magne Ingebrigtsen
2002-01-04 17:33 ` gnus-article-unsplit-urls Simon Josefsson
2002-01-04 17:42 ` gnus-article-unsplit-urls Michael Cook
2002-02-08 14:19 ` gnus-article-unsplit-urls Michael Cook
2002-02-08 14:33 ` gnus-article-unsplit-urls ShengHuo ZHU
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=g08pu4q2gdl.fsf@zzz.cisco.com \
--to=michael.cook@cisco.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).