From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Better References: parsing
Date: 26 Feb 2001 12:26:43 -0500 [thread overview]
Message-ID: <5bofvpe4oc.fsf@milli.cs.rochester.edu> (raw)
In-Reply-To: <m3snl1e6pw.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "26 Feb 2001 11:42:13 -0500")
prj@po.cwru.edu (Paul Jarc) writes:
> Some user agents truncate References: when it gets long, and not very
> intelligently, so it ends up as, e.g., "... <a@b.c> <d". A followup
> to such an article will have "... <a@b.c> <d <x@y.z>", which breaks
> gnus-split-references. This patch against current CVS helps.
>
> --- gnus-util.el~ Mon Feb 26 11:27:44 2001
> +++ gnus-util.el Mon Feb 26 11:27:27 2001
> @@ -382,7 +382,7 @@
> "Return a list of Message-IDs in REFERENCES."
> (let ((beg 0)
> ids)
> - (while (string-match "<[^>]+>" references beg)
> + (while (string-match "<[^> \t]+>" references beg)
> (push (substring references (match-beginning 0) (setq beg (match-end 0)))
> ids))
> (nreverse ids)))
>
> (Are ChangeLog entries desired for such small changes? If so:
> 2001-02-26 11:27:27 Paul Jarc <prj@po.cwru.edu>
>
> * gnus-util.el (gnus-split-references): Handle malformed References:.
> )
Installed. Thanks.
ShengHuo
prev parent reply other threads:[~2001-02-26 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 16:42 Paul Jarc
2001-02-26 17:26 ` ShengHuo ZHU [this message]
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=5bofvpe4oc.fsf@milli.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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).