From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Gathering very loose threads
Date: Wed, 15 May 2002 14:54:43 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0205151452570.4915-100000@yxa.extundo.com> (raw)
In-Reply-To: <uk7q53f3s.fsf@axis.com>
On Wed, 15 May 2002, Niklas Morberg wrote:
> I've set the variables:
>
> gnus-simplify-subject-functions '(gnus-simplify-subject-fuzzy)
> gnus-summary-gather-subject-limit 'fuzzy
> gnus-simplify-ignored-prefixes ".*\\[.*@.*\\]"
>
> to help gather subjects that belong together under the same
> thread. This helps a lot (the last one is to get replies to
> messages forwarded by gnus to thread properly), but one
> problem remains.
>
> Some MUAs insert a space in the subject line if the subject
> is too long (65 characters in one case). How can I solve
> this? Here is an example of four subject lines that all
> should be gathered in the same thread:
>
> About your recent suggestion to improve life
> Re: About your recent suggestion to improve life
> Re: [A person <a.person@hisdomain.org>] About your recent suggestion to improve life
> Re: [A person <a.person@hisdomain.org>] About your recent suggest ion to improve life
>
> Any ideas?
All whitespace could be stripped before comparing Subject: content.
Does this work as a member of gnus-simplify-subject-functions?
(lambda (str)
(with-temp-buffer
(insert str)
(goto-char (point-min))
(while (re-search-forward " +" nil t)
(replace-match ""))
(buffer-string))))))
next prev parent reply other threads:[~2002-05-15 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 10:00 Niklas Morberg
2002-05-15 12:13 ` odd nnir error Bill White
2002-05-18 19:01 ` Kai Großjohann
2002-05-15 12:54 ` Simon Josefsson [this message]
2002-05-15 14:31 ` Gathering very loose threads Niklas Morberg
[not found] ` <wtnn0v0dwfr.fsf@licia.dtek.chalmers.se>
2002-05-16 14:58 ` Simon Josefsson
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.44.0205151452570.4915-100000@yxa.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).