Gnus development mailing list
 help / color / mirror / Atom feed
From: Jonas Steverud <tvrud@bredband.net>
Subject: Re: gnus-list-identifiers not stripped in threads started with
Date: Tue, 18 May 2004 10:23:08 +0200	[thread overview]
Message-ID: <m2hdueuosz.fsf@c-a35372d5.036-4-67626721.cust.bredbandsbolaget.se> (raw)
In-Reply-To: <hhu0yetx1b.fsf@blah.pl> (Maciej Matysiak's message of "Tue, 18 May 2004 02:10:40 +0200")

Maciej Matysiak <phoner.ding@blah.pl> writes:

[...]
> i've just noticed that the bad effect is only in the summary, the subject
> is stripped in the message buffer.
>
> i'm using cvs few minutes old, but the bug has been in cvs gnus for a while
> alrady.

I've seen this as well and I agree, it is most annoying.

I have set nnmail-list-identifiers and gnus-list-identifiers. Since
the former is applied before any decoding of QP etc. it isn't very
useful so I started to do some research.

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¹. I've found
that if the regexps in the aforementioned functions does not match,
the removal is broken.

I suggestion is to check the offending emails literally (C-u g in
the summary) and see what the regexp acctually is applied to. I
wouldn't be surprised if the subject contains a Re: that isn't matched
by the (hardcoded) regexp.



Two IMHOs:

1. Why have both nnmail-list-identifiers *and* gnus-list-identifiers?
   Isn't this redundant? If the reason is that one shall have the
   option to remove it in mails but not elsewhere I don't agree: That
   can be controlled by group parameters. Besides, the
   nnmail-list-identifiers is not very useful considering it is
   applied *before* QP-decoding.

2. nnmail-list-identifiers should be applied after QP decoding.

I would prefer the removal of nnmail-list-identifiers of the two above.

-------
¹  IMHO the default for this should be set to include SV and AW and
any other known idiocy.

-- 
(        http://hem.bredband.net/steverud/        !     Wei Wu Wei     )
(        Meaning of U2 Lyrics, Roleplaying        !  To Do Without Do  )




       reply	other threads:[~2004-05-18  8:23 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 [this message]
     [not found]   ` <hhbrkmrv04.fsf@blah.pl>
2004-05-18  9:28     ` Jonas Steverud
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=m2hdueuosz.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).