Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc@chow.mat.jhu.edu>
Subject: Re: Regenerating nnml group?
Date: Tue, 21 Apr 1998 13:03:30 -0400	[thread overview]
Message-ID: <x7ra2rgl99.fsf@chow.mat.jhu.edu> (raw)
In-Reply-To: 's message of "21 Apr 1998 19:07:45 +0300"

<jari.aalto@poboxes.com (Jari Aalto+list.ding)> writes:
> 
> Thank you. Nov the .overview file appeared fine in the disk,
> but the Summary buffer still doesn't show the missing articles.
> I don't have any more ideas why the articles won't show up
> in there...

My guess is that the following will help:

Turn off threading in that group (e.g. with group parameters) or
just turn it off globally.  Then enter the group.  The missing
articles should appear.  Now inspect the references headers.  I
think you'll find something wrong, e.g. a loop of references.
Edit the articles and delete the offending references.  Then
things should be fine when threading is turned back on.

Bad references headers can happen, for example, if you get confused
when using `T ^' and process mark the wrong article.

Question:  could Gnus handle bad references more gracefully?  Silently
omitting articles from the summary buffer is bad.  

Dan

-- 
Dan Christensen
jdc@math.jhu.edu


  reply	other threads:[~1998-04-21 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-21 14:08 Jari Aalto+list.ding
1998-04-21 14:34 ` Kai Grossjohann
1998-04-21 16:07   ` Jari Aalto+list.ding
1998-04-21 17:03     ` Dan Christensen [this message]
1998-04-21 17:31       ` Jari Aalto+list.ding
1998-04-25 10:01       ` Kim-Minh Kaplan
1998-04-21 17:04     ` Kai Grossjohann

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=x7ra2rgl99.fsf@chow.mat.jhu.edu \
    --to=jdc@chow.mat.jhu.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).