From: Simon Josefsson <jas@extundo.com>
Cc: <ding@gnus.org>
Subject: Re: gnus-article-unsplit-urls
Date: Fri, 4 Jan 2002 16:48:36 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.33.0201041645470.16087-100000@slipsten.extundo.com> (raw)
In-Reply-To: <g08ell63z45.fsf@zzz.cisco.com>
On Fri, 4 Jan 2002, Michael Cook wrote:
> Simon Josefsson <jas@extundo.com> writes:
>
> > Just insert a \n at the proper place in the URL regexp.
>
> the newlines would need to be discard, not just matched, right?
Ah, you are right. Hmm. Is it possible to write a regexp to match the
complete URL but not include the \n in the \\(...\\) part? I don't think
so. Maybe the code should simply strip \n's from the matched data?
next prev parent reply other threads:[~2002-01-04 15:48 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 ` Simon Josefsson [this message]
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 ` gnus-article-unsplit-urls Michael Cook
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=Pine.LNX.4.33.0201041645470.16087-100000@slipsten.extundo.com \
--to=jas@extundo.com \
--cc=ding@gnus.org \
/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).