Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Lamoureux <lamour@engin.umich.edu>
Subject: rebuilding .overview
Date: 10 Feb 1997 12:33:11 -0500	[thread overview]
Message-ID: <6iv3ev4r2g8.fsf@erpland.engin.umich.edu> (raw)


Hmmm, hard to call this a bug, but easy to say that it didn't work
like I expected.  I'm still using the XEmacs version of gnus, and
yesterday, the filesystem that my homedir is on flaked and a large
chunk of a .overview file got corrupted (overwritten with nulls).

I spent quite a bit of time looking at the FAQ, help, and Info docs
trying to figure out how to rebuild it.  The best I could come up with
was M-x nnml-generate-nov-databases (which is probably overkill for
what I needed...is there a better way), and it was hard to find the
documentation for it even though I knew (from reading this list) that
such a beast existed.  Is there an error recovery section of the docs
that I missed?  Is there a better way to just regenerate the .overview
file for one group?

Also, after running the above function all of the new messages (there
were 105 new messages, which is how I noticed there was a problem in
the first place), all of the messages that were added back into the
.overview file were given a mark of read instead of unread.  I had to
enter the group with C-u Ret to see them.  Is that the best default
mark to have for such an operation?

Has this process been changed in the newer versions?  Is it better
documented now?


BTW, just the other day I had another group that didn't show up in the
topic listing until the second message showed up.  I had reported this
bug a while ago, but then couldn't reproduce it.  I just did.  :-/


fyi,
Michael


             reply	other threads:[~1997-02-10 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-02-10 17:33 Michael Lamoureux [this message]
1997-02-10 19:45 ` Rich Pieri
1997-02-12  1:31   ` Michael Lamoureux
1997-02-11 12:43 ` Lars Magne Ingebrigtsen
1997-02-11 20:21   ` Michael Lamoureux
1997-02-12  8:50     ` 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=6iv3ev4r2g8.fsf@erpland.engin.umich.edu \
    --to=lamour@engin.umich.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).