From: Colin Rafferty <craffert@ms.com>
Subject: bug in sparse threads
Date: 23 Oct 1998 16:27:48 -400 [thread overview]
Message-ID: <vgv7lxr9g6z.fsf@ms.com> (raw)
Hi-
I have the gnus-build-sparse-threads set to `t', and this has very
weird repercussions.
I have a pair of articles in an nnml group that are in the cache
(marked with a `?'). I don't see them when I enter the group (as I
shouldn't), but I do see phantom articles that are in the thread.
Here is what I see when I enter the group, and it has one new article
(note that gnus-summary-same-subject is "\\\\"):
Q [ 0: ] Re: mime-encoded email (and vm)
Q [ 0: ] \\
Q [ 0: ] \\
[ 11: +James Saveliff ] taken hostage by xemacs
If I then do a `/ D' (gnus-summary-limit-include-dormant), it shows
the dormant messages within their phantom thread:
Q [ 0: ] Re: mime-encoded email (and vm)
? + [ 20: +David Laks ] \\
Q [ 0: ] \\
Q [ 0: ] \\
Q [ 0: ] \\
? + [ 119: +Isaac Hollander ] \\
[ 11: +James Saveliff ] taken hostage by xemacs
Is there anything that I can do to fix all this? I like sparse
threads.
--
Colin
next reply other threads:[~1998-10-23 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-23 20:27 Colin Rafferty [this message]
1998-10-24 17:49 ` 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=vgv7lxr9g6z.fsf@ms.com \
--to=craffert@ms.com \
/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).