From: storm@cua.dk (Kim F. Storm)
Subject: Re: Bug? Extra whitespace in split subject lines in summary buffer
Date: Fri, 16 Jun 2006 11:41:07 +0200 [thread overview]
Message-ID: <m38xnxv3nw.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <b4mzmgdend9.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> 31-May [ 84: Daniel Brockman ] patch: bugfixes in rcirc.el (rcirc-default-user-full-name, rcirc-process-list)
>
> I often look at such ones in the nntp groups. It seems to be
> due to the INN server, that replaces LWSPs with a couple of
> spaces when generating NOV databases.
This is with groups read from gmane.org -- I don't think it uses INN
anymore.
>> Is this intentional?
>
> Maybe yes, in the sense that Gnus assumes that data in NOV have
> already been cooked [...]
I see. Thanks.
This also explains why I didn't notice this problem before...
... it must have started some moons ago, when I switched from
subscribing to the mailing lists to reading the lists on gmane.org.
> There are several ways to do that if you don't mind that it
> might slow Gnus. Here are two examples:
Thanks. I'll try those.
But I also hope that Lars will fix this on gmane.
>> I tried setting gnus-simplify-subject-functions, but it has no effect.
>
> It is used for other purposes: to test whether two subjects are
> alike, for instance.
IMO, the documentation for gnus-simplify-subject-functions
needs clarification. It just says "... that simpilifes subjects",
but not the circumstances where the simplified subject is used.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-06-16 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 22:43 Kim F. Storm
2006-06-16 4:27 ` Katsumi Yamaoka
2006-06-16 9:41 ` Kim F. Storm [this message]
2006-06-16 15:40 ` Adam Sjøgren
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=m38xnxv3nw.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
/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).