Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Duplicates/Loops in Summary Buffer
Date: Tue, 12 Feb 2002 22:27:44 -0500	[thread overview]
Message-ID: <2nofiuhxhr.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <m3ofixa9pt.fsf@barnowl.demon.co.uk>

Graham Murray <graham@barnowl.demon.co.uk> writes:

> Using the latest CVS, I am seeing a problem in the Summary Buffer (so
> far only with nntp backend.) Some articles appear twice, either
> immediately following one another, or the 2nd comes after replies to
> the first (the sub-thread is not repeated, only the one article.)
> This introduces a "loop" where trying to enter the 2nd occurrence
> takes you (in the summary buffer) back to the first. So you cannot use
> <space> or 'n' to leave the article, as these cause it to be
> displayed again. The first occurrence is marked 'R' but the 2nd one
> has no mark (unread). 
>
> Here is an example.
> O  +   148                           [  34: Fishfood            ] 
> O  +   142                              [  25: Simon               ] 
> O  +   142                                 [  11: Alexis Manning      ] 
> R. +   148                                    [  22: Fishfood            ] 
>  . +   148                                    [  22: Fishfood            ] 
> O  +   145                                 [  42: dormouse            ] 
>
> Are there any diagnostics I can take to help identify the cause?

Could you send the evaluation result of gnus-newsgroup-data to
bugs@gnus.org after entering such a Summary buffer?

ShengHuo



      parent reply	other threads:[~2002-02-13  3:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-10 10:54 Graham Murray
2002-02-10 19:52 ` Paul Jarc
2002-02-13  3:27 ` ShengHuo ZHU [this message]

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=2nofiuhxhr.fsf@zsh.cs.rochester.edu \
    --to=zsh@cs.rochester.edu \
    /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).