From: Jonas Steverud <tvrud@bredband.net>
Subject: Re: gnus-list-identifiers not stripped in threads started with
Date: Tue, 18 May 2004 11:28:41 +0200 [thread overview]
Message-ID: <m265auulrq.fsf@c-a35372d5.036-4-67626721.cust.bredbandsbolaget.se> (raw)
In-Reply-To: <hhbrkmrv04.fsf@blah.pl> (Maciej Matysiak's message of "Tue, 18 May 2004 10:37:31 +0200")
Maciej Matysiak <phoner.ding@blah.pl> writes:
> On the 18th of May 2004 at 10:23, Jonas Steverud <tvrud#bredband.net> wrote:
[...]
>> I could confirm that nnmail-list-identifiers is applied before any
>> decoding of QP etc. but that gnus-summary-remove-list-identifiers (and
>> so is nnmail-remove-list-identifiers) is hard-coded to use Re: instead
>> of using a variable similar to message-subject-re-regexp¹.
>
> ouch. my m-s-r-r is quite different than the default:
Just for the record: m-s-r-r is only used in message-mode.
nnmail-remove-list-identifiers use
"^Subject: +\\(Re: +\\)?\\(" regexp " *\\)"
gnus-summary-remove-list-identifiers use
(concat "\\(\\(\\(Re: +\\)?\\(" regexp " *\\)\\)+\\(Re: +\\)?\\)")
Ouch.
IMHO there should be a gnus-re-regexp that then is used as the default
for m-s-r-r and used by the xxx-remove-list-id functions.
(I know I should implement this myself, but I haven't done the
bureaucracy to be able to do that, but I guess the number of todos
pile up until I get it done, or something...)
>> I suggestion is to check the offending emails literally (C-u g in
>> the summary) and see what the regexp acctually is applied to.
>
> as i mentioned before, it happens only when the message which started thread
> is not visible in the summary. real example:
OK, I haven't done such testing - I just saw what happened in the
summary and then started to read the removal functions. It maybe is so
that it is the thread gathering functions or the display functions
that is the culprit and not the remove-function? I.e. the error might
be elsewhere.
--
( http://hem.bredband.net/steverud/ ! Wei Wu Wei )
( Meaning of U2 Lyrics, Roleplaying ! To Do Without Do )
next prev parent reply other threads:[~2004-05-18 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <hhu0yetx1b.fsf@blah.pl>
2004-05-18 8:23 ` Jonas Steverud
[not found] ` <hhbrkmrv04.fsf@blah.pl>
2004-05-18 9:28 ` Jonas Steverud [this message]
2004-05-18 13:56 ` Lars Magne Ingebrigtsen
2004-05-18 14:10 ` Jonas Steverud
2004-05-18 14:16 ` Lars Magne Ingebrigtsen
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=m265auulrq.fsf@c-a35372d5.036-4-67626721.cust.bredbandsbolaget.se \
--to=tvrud@bredband.net \
/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).